Authentication caching and password changes
3 May
2025
3 May
'25
2:31 p.m.
In Dovecot docs (https://doc.dovecot.org/2.3/configuration_manual/ authentication/caching/) we see:
- User logs in with password Y. The cached password X doesn’t match Y and the previous authentication was unsuccessful, so Dovecot doesn’t bother doing another backend passdb lookup (until cache TTL expires). The login fails.
Anyone knows why they chose this design ? Why not simply do a passdb lookup instead of waiting for cache TTL to expire ?
In Dovecot docs (https://doc.dovecot.org/2.3/configuration_manual/ authentication/caching/) we see:
- User logs in with password Y. The cached password X doesn’t match Y and the previous authentication was unsuccessful, so Dovecot doesn’t bother doing another backend passdb lookup (until cache TTL expires). The login fails. Anyone knows why they chose this design ? Why not simply do a passdb lookup instead of waiting for cache TTL to expire ?
1
Age (days ago)
1
Last active (days ago)
0 comments
1 participants
participants (1)
-
Diego Alvarez