goauthentik / goauthentik/authentik
kerberos login very long
- Dominant language
- Python
- Stars
- 25.6k
- Forks
- 2k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 659
Description
### Describe the bug
So, I deploy Authentik few years ago now and everythng is ok, but I wonder why autoconnection through any web-browser, the automatic login took like 7-10 secondes.
First time I think it was the database took too long to respond but not, if you have any suggestion it will help me a lot :)
authentik 2026.5.6
Active directory
Working but very long than a keycloak kerberos connection
I've already tweak postgres to autovacumming disable jit etc etc
Best regards
### How to reproduce
connect kerberos source (active directory)
configure browser + spnego etc
### Expected behavior
autoconnect took around 7-10 secondes
### Screenshots
_No response_
### Additional context
_No response_
### Deployment Method
Docker
### Version
2026.5.2
### Relevant log output
```shell
```
Contributor guide
Research direction
Start by reproducing the Active Directory Kerberos login through the Docker deployment with browser SPNEGO enabled, then inspect authentik logs and compare the 7–10 second delay with the reported database behavior. The issue provides no source file or test; done means identifying and resolving the login delay, with evidence from a repeatable reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgresql
- Domain
- authentication, backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100