luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity
open-consul/ui/packages/consul-ui/tests/acceptance/dc/acls/tokens/index.feature

126 lines
3.2 KiB
Gherkin
Raw Normal View History

UI: New ACLs (#4789) UI to accompany the new ACLs APIs
2018-10-19 15:17:02 +00:00
@setupApplicationTest
Feature: dc / acls / tokens / index: ACL Token List
UI: Catch 500 error on token endpoint and revert to legacy tokens (#4874) In some circumstances a consul 1.4 client could be running in an un-upgraded 1.3 or lower cluster. Currently this gives a 500 error on the new ACL token endpoint. Here we catch this specific 500 error/message and set the users AccessorID to null. Elsewhere in the frontend we use this fact (AccessorID being null) to decide whether to present the legacy or the new ACL UI to the user. Also: - Re-adds in most of the old style ACL acceptance tests, now that we are keeping the old style UI - Restricts code editors to HCL only mode for all `Rules` editing (legacy/'half legacy'/new style) - Adds a [Stop using] button to the old style ACL rows so its possible to logout. - Updates copy and documentation links for the upgrade notices
2018-11-02 14:44:36 +00:00
Scenario: I see the tokens
UI: New ACLs (#4789) UI to accompany the new ACLs APIs
2018-10-19 15:17:02 +00:00
Given 1 datacenter model with the value "dc-1"
And 3 token models
When I visit the tokens page for yaml
---
dc: dc-1
---
Then the url should be /dc-1/acls/tokens
ui: Implements the ember-page-title addon to the UI (#7118) * Installs ember-page-title 5.x * Adds a page title to all template files that need one * Adds an assertion step to test the page titles
2020-01-28 14:25:52 +00:00
And the title should be "Tokens - Consul"
UI: New ACLs (#4789) UI to accompany the new ACLs APIs
2018-10-19 15:17:02 +00:00
Then I see 3 token models
ui: Always show main navigation Key/Value link (#10916) * ui: Ignore response from API for KV permissions Currently there is no way for us to use our HTTP authorization API endpoint to tell us whether a user has access to any KVs (including the case where a user may not have access to the root KV store, but do have access to a sub item) This is a little weird still as in the above case the user would click on this link and still get a 403 for the root, and then have to manually type in the URL for the KV they do have access to. Despite this we think this change makes sense as at least something about KV is visible in the main navigation. Once we have the ability to know if any KVs are accessible, we can add this guard back in. We'd initially just removed the logic around the button, but then noticed there may be further related KV issues due to the nested nature of KVs so we finally decided on simply ignoring the responses from the HTTP API, essentially reverting the KV area back to being a thin client. This means when things are revisited in the backend we can undo this easily change in one place. * Move acceptance tests to use ACLs perms instead of KV ones
2021-09-22 17:23:59 +00:00
Scenario: Viewing tokens with no write access
Given 1 datacenter model with the value "dc-1"
And 3 token models
And permissions from yaml
---
acl:
write: false
---
When I visit the tokens page for yaml
---
dc: dc-1
---
Then the url should be /dc-1/acls/tokens
And I don't see create
ui: Adds ability to search by policy, role or service ident names (#5811)
2019-06-05 08:25:32 +00:00
Scenario: Searching the tokens
Given 1 datacenter model with the value "dc-1"
And 4 token models from yaml
---
- Description: Description Search
Legacy: false
ServiceIdentities:
- ServiceName: not-in-sisearch
Policies:
- Name: not-in-Polsearch
Roles:
- Name: not-in-rolesearch
- Description: Not in descsearch
Legacy: false
ServiceIdentities:
- ServiceName: not-in-sisearch
Policies:
- Name: Policy-Search
Roles:
- Name: not-in-rolesearch-either
- Description: Not in descsearch either
Legacy: false
ServiceIdentities:
- ServiceName: not-in-sisearch
Policies:
- Name: not-int-Polsearch-either
Roles:
- Name: Role-Search
- Description: Not in descsearch either
Legacy: false
ServiceIdentities:
- ServiceName: Si-Search
Policies:
- Name: not-int-Polsearch-either
Roles:
- Name: not-in-rolesearch-either
---
When I visit the tokens page for yaml
---
dc: dc-1
---
Then the url should be /dc-1/acls/tokens
Then I see 4 token models
Then I fill in with yaml
---
s: Description
---
And I see 1 token model
And I see 1 token model with the description "Description Search"
Then I fill in with yaml
---
s: Policy-Search
---
And I see 1 token model
And I see 1 token model with the policy "Policy-Search"
Then I fill in with yaml
---
s: Role-Search
---
And I see 1 token model
And I see 1 token model with the role "Role-Search"
Then I fill in with yaml
---
s: Si-Search
---
And I see 1 token model
ui: Redesigns for the token/policy/roles listings pages (#8144)
2020-06-23 09:12:04 +00:00
And I see 1 token model with the serviceIdentity "Si-Search"
UI: Catch 500 error on token endpoint and revert to legacy tokens (#4874) In some circumstances a consul 1.4 client could be running in an un-upgraded 1.3 or lower cluster. Currently this gives a 500 error on the new ACL token endpoint. Here we catch this specific 500 error/message and set the users AccessorID to null. Elsewhere in the frontend we use this fact (AccessorID being null) to decide whether to present the legacy or the new ACL UI to the user. Also: - Re-adds in most of the old style ACL acceptance tests, now that we are keeping the old style UI - Restricts code editors to HCL only mode for all `Rules` editing (legacy/'half legacy'/new style) - Adds a [Stop using] button to the old style ACL rows so its possible to logout. - Updates copy and documentation links for the upgrade notices
2018-11-02 14:44:36 +00:00
Scenario: I see the legacy message if I have one legacy token
Given 1 datacenter model with the value "dc-1"
And 3 token models from yaml
---
- Legacy: true
- Legacy: false
- Legacy: false
---
When I visit the tokens page for yaml
---
dc: dc-1
---
Then the url should be /dc-1/acls/tokens
And I see update
And I see 3 token models
Scenario: I don't see the legacy message if I have no legacy tokens
Given 1 datacenter model with the value "dc-1"
And 3 token models from yaml
---
- Legacy: false
- Legacy: false
- Legacy: false
---
When I visit the tokens page for yaml
---
dc: dc-1
---
Then the url should be /dc-1/acls/tokens
And I don't see update
And I see 3 token models