goauthentik / goauthentik/authentik
Keep user logged in not working when logging in on another device (2024.10.0)
- Dominant language
- Python
- Stars
- 25.6k
- Forks
- 2k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 651
Description
**Describe the bug**
The keep logged in function is not working properly since I've upgraded to 2024.10.0. I've set the time to 720 hours, but when I login with another device, the session of the old device is getting dropped. This was not the case with 2024.8.x.
**To Reproduce**
Steps to reproduce the behavior:
1. Login on device A and press yes on the keep signed in prompt.
2. Login on device B and press yes on the keep signed in prompt.
3. Go back to device A and see yourself logged out
**Expected behavior**
The session of device A should not be dropped. This has worked before with version 2024.8.x
**Version and Deployment (please complete the following information):**
- authentik version: 2024.10.0
- Deployment: docker-compose
Contributor guide
Research direction
Reproduce the two-device login sequence on authentik 2024.10.0 with keep signed in enabled and compare it with 2024.8.x. Trace the keep-signed-in session handling and determine why device A is logged out after device B logs in; done when both sessions remain active for the configured 720 hours.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, python
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100