mirror of
https://github.com/0rangebananaspy/authelia.git
synced 2024-09-14 22:47:21 +07:00
56fdc40290
Now, /verify can return 401 or 403 depending on the user authentication. Every public API endpoints and pages return 200 with error message in JSON body or 401 if the user is not authorized. This policy makes it complicated for an attacker to know what is the source of the failure and hide server-side bugs (not returning 500), bugs being potential threats.
16 lines
984 B
Gherkin
16 lines
984 B
Gherkin
Feature: Non authenticated users have no access to certain pages
|
|
|
|
Scenario Outline: Anonymous user has no access to protected pages
|
|
When I visit "<url>"
|
|
Then I get an error <error code>
|
|
|
|
Examples:
|
|
| url | error code |
|
|
| https://auth.test.local:8080/secondfactor | 401 |
|
|
| https://auth.test.local:8080/verify | 401 |
|
|
| https://auth.test.local:8080/secondfactor/u2f/identity/start | 401 |
|
|
| https://auth.test.local:8080/secondfactor/u2f/identity/finish | 401 |
|
|
| https://auth.test.local:8080/secondfactor/totp/identity/start | 401 |
|
|
| https://auth.test.local:8080/secondfactor/totp/identity/finish | 401 |
|
|
| https://auth.test.local:8080/password-reset/identity/start | 401 |
|
|
| https://auth.test.local:8080/password-reset/identity/finish | 401 | |