Hi, I would like to know if, in 389DS, is there the possibility to know when a user last authenticated to the system.
In OpenLDAP there is an overlay called slapo-lastbind which populate an operational attribute in the user entry called authTimestamp. I'm curious to know is something similar exists for 389DS.
If yes, is this attribute also propagated in a multi-master deployment.
Thanks in advance Marco
Hi, Marco
yes, there is 'Account Policy Plugin' updating the attribute 'lastLoginTime' ( http://directory.fedoraproject.org/wiki/Account_Policy_Design). I haven't tested how it works with replication, i'd be interested to know the results...
Up to the version 1.2.10rc1 there was a bug in the case when the PAM pass-through plugin was used ( https://bugzilla.redhat.com/show_bug.cgi?id=712294).
@+
2012/2/15 Marco Pizzoli marco.pizzoli@gmail.com
Hi, I would like to know if, in 389DS, is there the possibility to know when a user last authenticated to the system.
In OpenLDAP there is an overlay called slapo-lastbind which populate an operational attribute in the user entry called authTimestamp. I'm curious to know is something similar exists for 389DS.
If yes, is this attribute also propagated in a multi-master deployment.
Thanks in advance Marco
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
2012/2/15 Andrey Ivanov andrey.ivanov@polytechnique.fr
Hi, Marco
yes, there is 'Account Policy Plugin' updating the attribute 'lastLoginTime' ( http://directory.fedoraproject.org/wiki/Account_Policy_Design). I haven't tested how it works with replication, i'd be interested to know the results...
Up to the version 1.2.10rc1 there was a bug in the case when the PAM pass-through plugin was used ( https://bugzilla.redhat.com/show_bug.cgi?id=712294).
Thanks a lot! I will give it a look. Marco
389-users@lists.fedoraproject.org
-
Ivanov Andrey (M.) -
Marco Pizzoli