e34c16a90c
* ui: Logout button This commit adds an easier way to logout of the UI using a logout button Notes: - Added a Logout button to the main navigation when you are logged in, meaning you have easy access to a way to log out of the UI. - Changed all wording to use 'Log in/out' vocabulary instad of 'stop using'. - The logout button opens a panel to show you your current ACL token and a logout button in order to logout. - When using legacy ACLs we don't show the current ACL token as legacy ACLs tokens only have secret values, whereas the new ACLs use a non-secret ID plus a secret ID (that we don't show). - We also added a new `<EmptyState />` component to use for all our empty states. We currently only use this for the ACLs disabled screen to provide more outgoing links to more readind material/documentation to help you to understand and enable ACLs. - The `<DataSink />` component is the sibling to our `<DataSource />` component and whilst is much simpler (as it doesn't require polling support), its tries to use the same code patterns for consistencies sake. - We had a fun problem with ember-data's `store.unloadAll` here, and in the end went with `store.init` to empty the ember-data store instead due to timing issues. - We've tried to use already existing patterns in the Consul UI here such as our preexisting `feedback` service, although these are likely to change in the future. The thinking here is to add this feature with as little change as possible. Overall this is a precursor to a much larger piece of work centered on auth in the UI. We figured this was a feature complete piece of work as it is and thought it was worthwhile to PR as a feature on its own, which also means the larger piece of work will be a smaller scoped PR also.
45 lines
1.4 KiB
Gherkin
45 lines
1.4 KiB
Gherkin
@setupApplicationTest
|
|
Feature: dc / acls / tokens / use: Using an ACL token
|
|
Background:
|
|
Given 1 datacenter model with the value "datacenter"
|
|
And 1 token model from yaml
|
|
---
|
|
AccessorID: token
|
|
SecretID: ee52203d-989f-4f7a-ab5a-2bef004164ca
|
|
---
|
|
And settings from yaml
|
|
---
|
|
consul:token:
|
|
SecretID: secret
|
|
AccessorID: accessor
|
|
Namespace: default
|
|
---
|
|
Scenario: Using an ACL token from the listing page
|
|
When I visit the tokens page for yaml
|
|
---
|
|
dc: datacenter
|
|
---
|
|
And I click actions on the tokens
|
|
And I click use on the tokens
|
|
And I click confirmUse on the tokens
|
|
Then "[data-notification]" has the "notification-use" class
|
|
And "[data-notification]" has the "success" class
|
|
Then I have settings like yaml
|
|
---
|
|
consul:token: "{\"AccessorID\":\"token\",\"SecretID\":\"ee52203d-989f-4f7a-ab5a-2bef004164ca\",\"Namespace\":\"@namespace\"}"
|
|
---
|
|
Scenario: Using an ACL token from the detail page
|
|
When I visit the token page for yaml
|
|
---
|
|
dc: datacenter
|
|
token: token
|
|
---
|
|
And I click use
|
|
And I click confirmUse
|
|
Then "[data-notification]" has the "notification-use" class
|
|
And "[data-notification]" has the "success" class
|
|
Then I have settings like yaml
|
|
---
|
|
consul:token: "{\"AccessorID\":\"token\",\"SecretID\":\"ee52203d-989f-4f7a-ab5a-2bef004164ca\",\"Namespace\":\"@namespace\"}"
|
|
---
|