Duplicate of bug #2838.

I tested an old non composite config - same problem when pref are 
stored in ldap  I dont see the last_login beeing updated...

well it does not seem linked to the cache system used. I was tricked 
by a last_login already initialised.

So i still don't exactly know how to trigger this last_login pref not 
beeing updated. Very annoying...

I am using horde groupware webmail edition rc1 (no queue is defined 
for this appl in bug manager).

I am using a composite driver with ldap and cyrus as auth backends.

I have noticed that last_login, and possibly other kind of prefs, is 
not updated in the hordePerson ldap attribute when I have the caching 
system enabled.

I checked in the Auth code that getAuth() is called upon login into 
horde and so I guess last_login pref is updated in the session, but it 
is not saved on the ldap backend.

All other prefs accessible from the applications and horde options are 
saved and restored OK. It seems to me that all session preferences 
that are set internally by horde are not saved. I did not find why 
while looking at the code but I saw that pref can be cached and depend 
on a dirty bit to be effectively saved in the backend. So I disabled 
the horde cache and now my last login is saved and restored.

So i might be a bug related to cache behaviour. I used the filesystem 
cache driver:
$conf['cache']['default_lifetime'] = 1800;
$conf['cache']['params']['dir'] = Horde::getTempDir();
$conf['cache']['params']['gc'] = 86400;
$conf['cache']['driver'] = 'file';