open-consul/ui/packages/consul-ui/tests/acceptance/token-header.feature
Michael Klein 8b9a126386
ui: remove with-peers query param (#13756)
* Don't request nodes/services `with-peers` anymore

This will be automatic - no need for the query-param anymore.

* Return peering data based on feature flag mock-api services/nodes

* Update tests to reflect removed with-peers query-param

* setup cookie for turning peer feature flag on in mock-api in testing

* Add missing `S` for renamed PEERING feature-flag cookie
2022-07-14 19:32:53 +01:00

49 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 service page having not set a token previously
Given 1 datacenter model with the value "dc1"
When I visit the services page for yaml
---
dc: dc1
---
Then the url should be /dc1/services
And a GET request was made to "/v1/internal/ui/services?dc=dc1&ns=@namespace" from yaml
---
headers:
X-Consul-Token: ''
---
Scenario: Set the token to [Token] and then navigate to the service page
Given 1 datacenter model with the value "dc1"
And the url "/v1/acl/tokens" responds with a 403 status
When I visit the tokens page for yaml
---
dc: dc1
---
Then the url should be /dc1/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 services page for yaml
---
dc: dc1
---
Then the url should be /dc1/services
And a GET request was made to "/v1/internal/ui/services?dc=dc1&ns=@namespace" from yaml
---
headers:
X-Consul-Token: [Token]
---
Where:
---------
| Token |
| token |
| '' |
---------