mirror of
https://github.com/0rangebananaspy/authelia.git
synced 2024-09-14 22:47:21 +07:00
97bfafb6eb
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.
17 lines
989 B
Gherkin
17 lines
989 B
Gherkin
Feature: User can access certain subdomains with single factor
|
|
|
|
Scenario: User is redirected to service after first factor if allowed
|
|
When I visit "https://login.example.com:8080/?rd=https://single_factor.example.com:8080/secret.html"
|
|
And I login with user "john" and password "password"
|
|
Then I'm redirected to "https://single_factor.example.com:8080/secret.html"
|
|
|
|
Scenario: Redirection after first factor fails if single_factor not allowed. It redirects user to first factor.
|
|
When I visit "https://login.example.com:8080/?rd=https://admin.example.com:8080/secret.html"
|
|
And I login with user "john" and password "password"
|
|
Then I'm redirected to "https://login.example.com:8080/?rd=https://admin.example.com:8080/secret.html"
|
|
|
|
Scenario: User can login using basic authentication
|
|
When I request "https://single_factor.example.com:8080/secret.html" with username "john" and password "password" using basic authentication
|
|
Then I receive the secret page
|
|
|