diff options
| author | azul <azul@leap.se> | 2014-07-17 12:16:07 +0200 |
|---|---|---|
| committer | azul <azul@leap.se> | 2014-07-17 12:16:07 +0200 |
| commit | ade74d8a9091ae607586d7b287a0579a2ee7af8e (patch) | |
| tree | 74273b8ba7e35d0fb3c96aa79e63c93086d15146 /features/authentication.feature | |
| parent | 952bc18e8333ca5c3e6e16f8059f84a1414d5f6f (diff) | |
| parent | e86cccb4b89540f3bd403110d051b2723be781b9 (diff) | |
Merge pull request #176 from azul/feature/api-authenticated-configs
API: Authenticated access to config settings
Diffstat (limited to 'features/authentication.feature')
| -rw-r--r-- | features/authentication.feature | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/features/authentication.feature b/features/authentication.feature new file mode 100644 index 0000000..52b562f --- /dev/null +++ b/features/authentication.feature @@ -0,0 +1,24 @@ +Feature: Authentication + + Authentication is handled with SRP. Once the SRP handshake has been successful a token will be transmitted. This token is used to authenticate further requests. + + In the scenarios MY_AUTH_TOKEN will serve as a placeholder for the actual token received. + + Background: + Given I set headers: + | Accept | application/json | + | Content-Type | application/json | + + Scenario: Submitting a valid token + Given I authenticated + And I set headers: + | Authorization | Token token="MY_AUTH_TOKEN" | + When I send a GET request to "/1/configs.json" + Then the response status should be "200" + + Scenario: Submitting an invalid token + Given I authenticated + And I set headers: + | Authorization | Token token="InvalidToken" | + When I send a GET request to "/1/configs.json" + Then the response status should be "401" |