dovecot - Aug 2006 - Feature req: auth_cache_relookup

With auth_cache_size set to a value greater than zero, when our users change
passwords their accounts stop working for a few minutes, because they are trying
to log in with their new password, but Dovecot is comparing that against the
cached old password.  It would be nice if an option could be added so that if
the login password does not match the cached password, the cache value is
dropped and dovecot-auth queries the userDB, but only if the previous login was
successful (to avoid frequent queries for bad logins).

Maybe this option could be called "auth_cache_relookup"

Bill

On Thu, 2006-08-31 at 12:16 -0400, Bill Boebel wrote:
> With auth_cache_size set to a value greater than zero, when our users
change passwords their accounts stop working for a few minutes, because they are
trying to log in with their new password, but Dovecot is comparing that against
the cached old password.  It would be nice if an option could be added so that
if the login password does not match the cached password, the cache value is
dropped and dovecot-auth queries the userDB, but only if the previous login was
successful (to avoid frequent queries for bad logins).
> 
> Maybe this option could be called "auth_cache_relookup"
I think I'll implement this without making it an option.

This brings to my mind your problems with memory leaks. Could it be that
auth cache is causing the leaks and not LDAP?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20061013/279943b9/attachment.bin>