open-consul/ui-v2/tests/acceptance/token-header.feature
John Cowen 31f36ce096 ui: Namespace Support (#6639)
Adds namespace support to the UI:

1. Namespace CRUD/management
2. Show Namespace in relevant areas (intentions, upstreams)
3. Main navigation bar improvements
4. Logic/integration to interact with a new `internal/acl/authorize` endpoint
2019-12-18 12:26:47 +00:00

41 lines
1.2 KiB
Gherkin

@setupApplicationTest
Feature: token headers
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 is made to "/v1/namespaces" 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
Then I fill in with yaml
---
secret: [Token]
---
And I submit
When I visit the index page
Then the url should be /datacenter/services
And a GET request was made to "/v1/namespaces" from yaml
---
headers:
X-Consul-Token: [Token]
---
Where:
---------
| Token |
| token |
| '' |
---------