When the internal ticket renewal process runs, it has the Kerberos credential cache saved into the 'authtok' member attribute of the PAM data. So after it successfully renews the ticket, we're saving this value to the cache.
We need to skip updating the cached password if it's happening during automatic ticket renewal.
On 04/28/2011 07:55 PM, Stephen Gallagher wrote:
When the internal ticket renewal process runs, it has the Kerberos credential cache saved into the 'authtok' member attribute of the PAM data. So after it successfully renews the ticket, we're saving this value to the cache.
We need to skip updating the cached password if it's happening during automatic ticket renewal.
Ack
On Fri, 2011-04-29 at 10:22 +0200, Jakub Hrozek wrote:
On 04/28/2011 07:55 PM, Stephen Gallagher wrote:
When the internal ticket renewal process runs, it has the Kerberos credential cache saved into the 'authtok' member attribute of the PAM data. So after it successfully renews the ticket, we're saving this value to the cache.
We need to skip updating the cached password if it's happening during automatic ticket renewal.
Ack
Pushed to master and sssd-1-5.
sssd-devel@lists.fedorahosted.org
-
Jakub Hrozek -
Stephen Gallagher