-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Reloading loop after update to 2023.10.1 #7342
Comments
should be fixed by #7324, you can test with the images linked in that PR |
I can still reproduce after updating to 2023.10.2 |
So can I - I don't think that fix is in 2023.10.2 |
I had this issue under |
@Kaaybi @yaakovfeldman @aceat64 Have you deleted the cookies for the URL? I had to delete the 2 cookies for the domain I tried to reach (after the update to 2023.10.2), then I could reach the site without a loop, again. |
I did, which will let me through, but the issue returns once the cookie named |
I have the exact same issue with redis and postgress when i updated to version 2023.10.1. After the "Token validity" setting expires i get the login screen and enter my credentials. After that i can see login successful top right of the screen and then it keeps looping the same screen with the loading logo spinning. This happens with the forward auth middleware build in to traefik and update to 2023.10.2) Authentik is proxied withouth the forward auth middleware and i can access it as normal. Also have one service (docker) running local using the OAuth2/OpenID Provider and this also has no issues when repeatedly logging in and out. Seeing the redis errors in noted by #7374 in my logs. Set a new database on redis and postgres and let authentik build it completely new and restored the old database for the case any tables where missing > issues still happening. The only thing working is removing the cookies from the browser (chrome) and then login with forward auth works until the "Token validity" setting expires. Also getting the error when authentik starts up: If any information is needed for debugging let me know as i'm happy to help improving this great product. |
I am bitten by exactly the same bug. Running Authentik 2023.10.1 behind Nginx. Deletion of cookies works until the new cookie expires. |
@raldnor @nismanoku @aceat64 @lexxxel please test the images from here #7385 (comment) |
I cleared all cookies for my domains and updated to those images for testing. Same results. I was able to access the proxied service but once the access token expired the issue came back. (I deleted the cookie to simulate expiration) |
I haven't yet updated to the images from #7385. Because yesterday i removed some of the providers and applications that where created before the update and recreated them. Afterwards i added them back to the embedded outpost and when logging in i got a clientid error notification. After refreshing the page i got the login page again and entered my credentials again after which i was authorized and redirect (traefik) to the service i was trying to access. Today i tried to login to those services again and i was successfully authorized and redirected to the services i was trying to reach. Well beyond the token validity setting duration of multiple services (single proxy authentication applications). Also haven't seen any of the errors with redis and/or authentik in the logs as prior to recreating the providers and applications. So i don't want to upgrade right away and give it some time for the token validity to expire again to test further if the loop comes back again or not without changing any other variables. Will follow if the loop comes back again or not. Has anyone of the others already tried recreating the providers and applications and re-adding them to the outpost for their services? Add-on: Entered details as below in the repository field and started up. Entered the outpost setting as a environment variable but the outpost in authentik still gives 2023.10.2 (build 596c16b) as version while authentik gives the correct version [596c16b] Based on 2023.10.2. i'm running as a docker on unraid with the provided community setup through ibracorp. |
@nismanoku I'm seeing the exact same issue with a Kubernetes deployment on 2023.10.2. |
Hello,
after the update to 2023.10.1 I notice a reloading loop after the authentication to my Prometheus site.
I use Proxy Provider with
default-source-authentication (Welcome to authentik!)
anddefault-provider-authorization-implicit-consent (Authorize Application)
flow but I also try thedefault-authentication-flow (Welcome to authentik!)
flow.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Just login
Screenshots
![image](https://private-user-images.githubusercontent.com/37346547/278625731-724caa63-3c16-4b4a-a86e-798db2c4fe7f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk2MTIwMzYsIm5iZiI6MTczOTYxMTczNiwicGF0aCI6Ii8zNzM0NjU0Ny8yNzg2MjU3MzEtNzI0Y2FhNjMtM2MxNi00YjRhLWE4NmUtNzk4ZGIyYzRmZTdmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE1VDA5Mjg1NlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWJjZTU3MTkyNTJjNWVjNzNiMGM1ZGUwOTUxMjMyNjY5YWU5ZDQ1MDU2NTU2NzI5M2YyMDIxYmIwZDYzZTA2YjUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.kcf_oI1FwODW3gjeC8W0ddjLUla7Mg6JVXMNTQBsNXA)
Logs
docker-compose server log
Version and Deployment (please complete the following information):
The text was updated successfully, but these errors were encountered: