RPJosh
/
authelia
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
authelia/test/features/access-control.feature

56 lines
3.3 KiB
Gherkin
Raw Normal View History

Replace mocha integration tests by cucumber tests
2017-07-26 21:45:26 +00:00
Feature: User has access restricted access to domains
Add logs to detect redis connection issues earlier Before this fix, the application was simply crashing during execution when connection to redis was failing. Now, it is correctly handled with failing promises and logs have been enabled to clearly see the problem
2017-09-21 20:07:34 +00:00
@need-registered-user-john
Replace mocha integration tests by cucumber tests
2017-07-26 21:45:26 +00:00
Scenario: User john has admin access
Fix basic authentication and tests
2018-04-25 07:30:21 +00:00
When I visit "https://login.example.com:8080?rd=https://home.example.com:8080/"
Add logs to detect redis connection issues earlier Before this fix, the application was simply crashing during execution when connection to redis was failing. Now, it is correctly handled with failing promises and logs have been enabled to clearly see the problem
2017-09-21 20:07:34 +00:00
And I login with user "john" and password "password"
And I use "REGISTERED" as TOTP token handle
Improve UX of the second factor page Start the U2F signing request when entering in the second factor page so that the user only has to touch the token without any other clicks.
2017-10-21 23:23:26 +00:00
And I click on "Sign in"
Change domain from test.local to example.com Warning: you will need to update your /etc/hosts to take this change into account for the example environment to work.
2017-11-02 20:34:07 +00:00
And I'm redirected to "https://home.example.com:8080/"
Fix unit and integration tests
2018-03-28 22:04:59 +00:00
Then I have access to "https://public.example.com:8080/secret.html"
And I have access to "https://dev.example.com:8080/groups/admin/secret.html"
And I have access to "https://dev.example.com:8080/groups/dev/secret.html"
And I have access to "https://dev.example.com:8080/users/john/secret.html"
And I have access to "https://dev.example.com:8080/users/harry/secret.html"
And I have access to "https://dev.example.com:8080/users/bob/secret.html"
And I have access to "https://admin.example.com:8080/secret.html"
And I have access to "https://mx1.mail.example.com:8080/secret.html"
And I have access to "https://single_factor.example.com:8080/secret.html"
And I have no access to "https://mx2.mail.example.com:8080/secret.html"
Replace mocha integration tests by cucumber tests
2017-07-26 21:45:26 +00:00
Add logs to detect redis connection issues earlier Before this fix, the application was simply crashing during execution when connection to redis was failing. Now, it is correctly handled with failing promises and logs have been enabled to clearly see the problem
2017-09-21 20:07:34 +00:00
@need-registered-user-bob
Replace mocha integration tests by cucumber tests
2017-07-26 21:45:26 +00:00
Scenario: User bob has restricted access
Fix basic authentication and tests
2018-04-25 07:30:21 +00:00
When I visit "https://login.example.com:8080?rd=https://home.example.com:8080/"
Add logs to detect redis connection issues earlier Before this fix, the application was simply crashing during execution when connection to redis was failing. Now, it is correctly handled with failing promises and logs have been enabled to clearly see the problem
2017-09-21 20:07:34 +00:00
And I login with user "bob" and password "password"
And I use "REGISTERED" as TOTP token handle
Improve UX of the second factor page Start the U2F signing request when entering in the second factor page so that the user only has to touch the token without any other clicks.
2017-10-21 23:23:26 +00:00
And I click on "Sign in"
Change domain from test.local to example.com Warning: you will need to update your /etc/hosts to take this change into account for the example environment to work.
2017-11-02 20:34:07 +00:00
And I'm redirected to "https://home.example.com:8080/"
Fix unit and integration tests
2018-03-28 22:04:59 +00:00
Then I have access to "https://public.example.com:8080/secret.html"
And I have no access to "https://dev.example.com:8080/groups/admin/secret.html"
And I have access to "https://dev.example.com:8080/groups/dev/secret.html"
And I have no access to "https://dev.example.com:8080/users/john/secret.html"
And I have no access to "https://dev.example.com:8080/users/harry/secret.html"
And I have access to "https://dev.example.com:8080/users/bob/secret.html"
And I have no access to "https://admin.example.com:8080/secret.html"
And I have access to "https://mx1.mail.example.com:8080/secret.html"
[BREAKING] Flatten the ACL rules to enable some use cases. With previous configuration format rules were not ordered between groups and thus not predictable. Also in some cases `any` must have been a higher precedence than `groups`. Flattening the rules let the user apply whatever policy he can think of. When several rules match the (subject, domain, resource), the first one is applied. NOTE: This commit changed the format for declaring ACLs. Be sure to update your configuration file before upgrading.
2018-10-23 22:29:09 +00:00
And I have access to "https://single_factor.example.com:8080/secret.html"
Fix unit and integration tests
2018-03-28 22:04:59 +00:00
And I have access to "https://mx2.mail.example.com:8080/secret.html"
Replace mocha integration tests by cucumber tests
2017-07-26 21:45:26 +00:00
Add logs to detect redis connection issues earlier Before this fix, the application was simply crashing during execution when connection to redis was failing. Now, it is correctly handled with failing promises and logs have been enabled to clearly see the problem
2017-09-21 20:07:34 +00:00
@need-registered-user-harry
Replace mocha integration tests by cucumber tests
2017-07-26 21:45:26 +00:00
Scenario: User harry has restricted access
Fix basic authentication and tests
2018-04-25 07:30:21 +00:00
When I visit "https://login.example.com:8080?rd=https://home.example.com:8080/"
Add logs to detect redis connection issues earlier Before this fix, the application was simply crashing during execution when connection to redis was failing. Now, it is correctly handled with failing promises and logs have been enabled to clearly see the problem
2017-09-21 20:07:34 +00:00
And I login with user "harry" and password "password"
And I use "REGISTERED" as TOTP token handle
Improve UX of the second factor page Start the U2F signing request when entering in the second factor page so that the user only has to touch the token without any other clicks.
2017-10-21 23:23:26 +00:00
And I click on "Sign in"
Change domain from test.local to example.com Warning: you will need to update your /etc/hosts to take this change into account for the example environment to work.
2017-11-02 20:34:07 +00:00
And I'm redirected to "https://home.example.com:8080/"
Fix unit and integration tests
2018-03-28 22:04:59 +00:00
Then I have access to "https://public.example.com:8080/secret.html"
And I have no access to "https://dev.example.com:8080/groups/admin/secret.html"
And I have no access to "https://dev.example.com:8080/groups/dev/secret.html"
And I have no access to "https://dev.example.com:8080/users/john/secret.html"
And I have access to "https://dev.example.com:8080/users/harry/secret.html"
And I have no access to "https://dev.example.com:8080/users/bob/secret.html"
And I have no access to "https://admin.example.com:8080/secret.html"
And I have no access to "https://mx1.mail.example.com:8080/secret.html"
[BREAKING] Flatten the ACL rules to enable some use cases. With previous configuration format rules were not ordered between groups and thus not predictable. Also in some cases `any` must have been a higher precedence than `groups`. Flattening the rules let the user apply whatever policy he can think of. When several rules match the (subject, domain, resource), the first one is applied. NOTE: This commit changed the format for declaring ACLs. Be sure to update your configuration file before upgrading.
2018-10-23 22:29:09 +00:00
And I have access to "https://single_factor.example.com:8080/secret.html"
Fix unit and integration tests
2018-03-28 22:04:59 +00:00
And I have no access to "https://mx2.mail.example.com:8080/secret.html"