412eec7f5d
* 6 new components for new login/logout flow, plus SSO support UI Components: 1. AuthDialog: Wraps/orchestrates AuthForm and AuthProfile 2. AuthForm: Authorization form shown when logged out. 3. AuthProfile: Simple presentational component to show the users 'Profile' 4. OidcSelect: A 'select' component for selecting an OIDC provider, dynamically uses either a single select menu or multiple buttons depending on the amount of providers Data Components: 1. JwtSource: Given an OIDC provider URL this component will request a token from the provider and fire an donchange event when it has been retrieved. Used by TokenSource. 2. TokenSource: Given a oidc provider name or a Consul SecretID, TokenSource will use whichever method/API requests required to retrieve Consul ACL Token, which is emitted to the onchange event handler. Very basic README documentation included here, which is likely to be refined somewhat. * CSS required for new auth/SSO UI components * Remaining app code required to tie the new auth/SSO work together * CSS code required to help tie the auth/SSO work together * Test code in order to get current tests passing with new auth/SSO flow ..plus extremely basics/skipped rendering tests for the new components * Treat the secret received from the server as the truth Previously we've always treated what the user typed as the truth, this breaks down when using SSO as the user doesn't type anything to retrieve a token. Therefore we change this so that we use the secret in the API response as the truth. * Make sure removing an dom tree from a buffer only removes its own tree
43 lines
1.4 KiB
Gherkin
43 lines
1.4 KiB
Gherkin
@setupApplicationTest
|
|
@notNamespaceable
|
|
Feature: token-header
|
|
In order to authenticate with tokens
|
|
As a user
|
|
I need to be able to specify a ACL token AND/OR leave it blank to authenticate with the API
|
|
Scenario: Arriving at the index page having not set a token previously
|
|
Given 1 datacenter model with the value "datacenter"
|
|
When I visit the index page
|
|
Then the url should be /datacenter/services
|
|
And a GET request was made to "/v1/internal/ui/services?dc=datacenter&ns=@namespace" from yaml
|
|
---
|
|
headers:
|
|
X-Consul-Token: ''
|
|
---
|
|
Scenario: Set the token to [Token] and then navigate to the index page
|
|
Given 1 datacenter model with the value "datacenter"
|
|
And the url "/v1/acl/tokens" responds with a 403 status
|
|
When I visit the tokens page for yaml
|
|
---
|
|
dc: datacenter
|
|
---
|
|
Then the url should be /datacenter/acls/tokens
|
|
And I click login on the navigation
|
|
And I fill in the auth form with yaml
|
|
---
|
|
SecretID: [Token]
|
|
---
|
|
And I click submit on the authdialog.form
|
|
When I visit the index page
|
|
Then the url should be /datacenter/services
|
|
And a GET request was made to "/v1/internal/ui/services?dc=datacenter&ns=@namespace" from yaml
|
|
---
|
|
headers:
|
|
X-Consul-Token: [Token]
|
|
---
|
|
Where:
|
|
---------
|
|
| Token |
|
|
| token |
|
|
| '' |
|
|
---------
|