Authenik session cookie expires value changes from timestamp to "Session" and requires reauthentication after few hours

[raulk89]

We have noticed an issue in authentik 2024.10.x version where we need to reauthenticate again for every ~2-3 hours. Initially we had session cookie set to expire after 1 day. But now we changed it to 5 days. Nothing changes. Our session cookie still expires after few hours.

I noticed that on web browser (Edge), the session cookie expires value changes from timestamp to "Session". It probably has something to do with it perhaps. After I reauthenticate again, then the session cookie value changes back to timestamp value.

The issue started after we ugprade to 2024.10.0
We came from 2024.8.3 and everything was working fine until we did the ugprade. We tried 2024.10.1 version as well, and we encountered the same issue.

I will upload the screenshot as well.

Deployment type: helm

Regards
Raul

[tograss]

Hi, please see #11436 . I think it might be the same bug. I noticed exact the same behavior

[raulk89]

Hmm, thanks.
Seems like the same issue.

I refreshed the authentik page, my session was still working.
Then we executed the ldap_sync, I did the refresh on that authentik page, and it asks for reauthenticating.
So seems like ldap_sync ise the issue yes.

According to this, by disabling the ldap_sync is also a workaround, yes ?

But what is strange, for us it worked like a charm in 2024.8.3
One thing to note. On 27-th of October, we had time change as well due to DST (Daylight Savings Time).
Before we were UTC +3
After 27-th of October we are on UTC+2

We may have been upgrading the authentik at the same time (not 100% about that). So that is why we thought it was due to the upgrade.

But when it is due to the time difference, can it be DST related or not possible at all ?

Raul

[authentik-automation]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Richar-Dada]

I have the same problem

[Richar-Dada]

We have noticed an issue in authentik 2024.10.x version where we need to reauthenticate again for every ~2-3 hours. Initially we had session cookie set to expire after 1 day. But now we changed it to 5 days. Nothing changes. Our session cookie still expires after few hours.

I noticed that on web browser (Edge), the session cookie expires value changes from timestamp to "Session". It probably has something to do with it perhaps. After I reauthenticate again, then the session cookie value changes back to timestamp value.

The issue started after we ugprade to 2024.10.0 We came from 2024.8.3 and everything was working fine until we did the ugprade. We tried 2024.10.1 version as well, and we encountered the same issue.

I will upload the screenshot as well.

Deployment type: helm

Regards Raul

hello，is the problem solved ？

[raulk89]

HeiWe did disable ldap sync. This was the cause why it happens.I have not tried it recently to enable the ldap sync again and see what happens.What version you are on currently ?RegardsRaulSent from my iPhoneOn 17. Jan 2025, at 11:50, 大大糖 ***@***.***> wrote: We have noticed an issue in authentik 2024.10.x version where we need to reauthenticate again for every ~2-3 hours. Initially we had session cookie set to expire after 1 day. But now we changed it to 5 days. Nothing changes. Our session cookie still expires after few hours. I noticed that on web browser (Edge), the session cookie expires value changes from timestamp to "Session". It probably has something to do with it perhaps. After I reauthenticate again, then the session cookie value changes back to timestamp value. The issue started after we ugprade to 2024.10.0 We came from 2024.8.3 and everything was working fine until we did the ugprade. We tried 2024.10.1 version as well, and we encountered the same issue. I will upload the screenshot as well. authentik_issue.png (view on web) Deployment type: helm Regards Raul hello，is the problem solved ？ —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[authentik-automation]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.