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

40 lines
2.1 KiB
Gherkin
Raw Permalink Normal View History

Parameterize authentication regulation via configuration file. Both for flexibility and for testing purposes.
2017-09-02 23:25:43 +00:00
Feature: Authelia regulates authentication to avoid brute force
@needs-test-config
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-blackhat
Parameterize authentication regulation via configuration file. Both for flexibility and for testing purposes.
2017-09-02 23:25:43 +00:00
Scenario: Attacker tries too many authentication in a short period of time and get banned
Given I visit "https://auth.test.local:8080/"
And I set field "username" to "blackhat"
And I set field "password" to "bad-password"
And I click on "Sign in"
Every public endpoints return 200 with harmonized error messages or 401 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.
2017-10-10 21:03:30 +00:00
And I get a notification of type "error" with message "Authentication failed. Please check your credentials."
Parameterize authentication regulation via configuration file. Both for flexibility and for testing purposes.
2017-09-02 23:25:43 +00:00
And I set field "password" to "bad-password"
And I click on "Sign in"
Every public endpoints return 200 with harmonized error messages or 401 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.
2017-10-10 21:03:30 +00:00
And I get a notification of type "error" with message "Authentication failed. Please check your credentials."
Parameterize authentication regulation via configuration file. Both for flexibility and for testing purposes.
2017-09-02 23:25:43 +00:00
And I set field "password" to "bad-password"
And I click on "Sign in"
Every public endpoints return 200 with harmonized error messages or 401 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.
2017-10-10 21:03:30 +00:00
And I get a notification of type "error" with message "Authentication failed. Please check your credentials."
Parameterize authentication regulation via configuration file. Both for flexibility and for testing purposes.
2017-09-02 23:25:43 +00:00
When I set field "password" to "password"
And I click on "Sign in"
Every public endpoints return 200 with harmonized error messages or 401 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.
2017-10-10 21:03:30 +00:00
Then I get a notification of type "error" with message "Authentication failed. Please check your credentials."
Parameterize authentication regulation via configuration file. Both for flexibility and for testing purposes.
2017-09-02 23:25:43 +00:00
@needs-test-config
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-blackhat
Parameterize authentication regulation via configuration file. Both for flexibility and for testing purposes.
2017-09-02 23:25:43 +00:00
Scenario: User is unbanned after a configured amount of time
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
Given I visit "https://auth.test.local:8080/?redirect=https%3A%2F%2Fpublic.test.local%3A8080%2Fsecret.html"
Parameterize authentication regulation via configuration file. Both for flexibility and for testing purposes.
2017-09-02 23:25:43 +00:00
And I set field "username" to "blackhat"
And I set field "password" to "bad-password"
And I click on "Sign in"
Every public endpoints return 200 with harmonized error messages or 401 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.
2017-10-10 21:03:30 +00:00
And I get a notification of type "error" with message "Authentication failed. Please check your credentials."
Parameterize authentication regulation via configuration file. Both for flexibility and for testing purposes.
2017-09-02 23:25:43 +00:00
And I set field "password" to "bad-password"
And I click on "Sign in"
Every public endpoints return 200 with harmonized error messages or 401 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.
2017-10-10 21:03:30 +00:00
And I get a notification of type "error" with message "Authentication failed. Please check your credentials."
Parameterize authentication regulation via configuration file. Both for flexibility and for testing purposes.
2017-09-02 23:25:43 +00:00
And I set field "password" to "bad-password"
And I click on "Sign in"
Every public endpoints return 200 with harmonized error messages or 401 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.
2017-10-10 21:03:30 +00:00
And I get a notification of type "error" with message "Authentication failed. Please check your credentials."
Parameterize authentication regulation via configuration file. Both for flexibility and for testing purposes.
2017-09-02 23:25:43 +00:00
When I wait 6 seconds
And I set field "password" to "password"
And I click on "Sign in"
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 use "REGISTERED" as TOTP token handle
Parameterize authentication regulation via configuration file. Both for flexibility and for testing purposes.
2017-09-02 23:25:43 +00:00
And I click on "TOTP"
Fix randomness in integration tests
2017-10-08 15:13:29 +00:00
Then I'm redirected to "https://public.test.local:8080/secret.html"