Jens L.

Results 517 comments of Jens L.

2024.8.3 should fix this error (and return a placeholder), however the root cause is that the x-forwarded-for header from your reverse proxy is empty

I haven't been able to reproduce this issue on 2024.8. I'm assuming this issue only happens on a non-clean install of authentik?

I suspect you're running a beta version as the code for this behaviour is not included in 2024.6.x. This is part of an upcoming change, see https://docs.goauthentik.io/docs/releases/2024.8#manual-action-may-be-required

you can use ghcr.io/goauthentik/dev-server:gh-version-2024.8 where this fix is already published, otherwise 2024.8.1 will be released later this week

This happens due to the `Not you?` button cancelling the flow execution by removing the currently planned flow, which also contains the final URL that the user should be sent...

I'm not saying that I dont agree with your point, this was just for context of why the current behaviour happens as it does. I think this might be also...

see #2023, when logging out from authentik all the users session tokens (like access tokens) are revoked and a signal is sent to the proxy provider to invalidate sessions there...

@flece could it be that in your .env file, the password entry has an invisible unicode character in it? could both of you run dump_config to ensure authentik reads the...