-
-
Notifications
You must be signed in to change notification settings - Fork 924
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 2024.10.2 breaks Captcha stage #12042
Comments
These are the backend logs fired when accessing the login page:
|
Which captcha provider are you using? |
Same here after upgrading from 2024.10.1, I tried both reCaptcha and Cloudflare Turnstile |
When either captcha is configured as previously it should continue to work just fine, for reCaptcha v2 / Turnstile managed the new "Interactive" flag needs to be enabled We'll test this with an upgraded instance with a captcha configured known working on 2024.10.1 as that should continue to work as is |
I attempted a complete reinstallation of Authentik using the latest Docker image. I reconfigured my Turnstile Captcha, which is currently set to invisible mode (so interactive mode isn't required). However, I’m still encountering the same issue: an infinite loading circle, along with the same error appearing in the browser console. |
The PR above will fix this issue. However as we've announced the security release 2024.10.3 for next week we can't create a bugfix release for this, however this will be available on the container image |
"Glad" to see that I'm not the only one :-) |
Decided to update my reverse proxy today. After i was finished, i noticed my authelia was not working. |
Describe the bug
When updating to 2024.10.2, if you have a captcha stage, the login flow loads indefinitely and throws an error to console:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Captcha stage is loaded correctly and the login form is shown
Screenshots
Logs
Here are the frontend console outputs:
Backend logs are provided below in the comment
Version and Deployment (please complete the following information):
The text was updated successfully, but these errors were encountered: