[Date Prev][Date Next]
Re: "authtimestamp" attribute replication
2012/11/13 Quanah Gibson-Mount <firstname.lastname@example.org>
Read the slapo-ppolicy(5) man page.
--On Tuesday, November 13, 2012 7:29 PM +0000 jeevan kc <email@example.com
So I have initiated the lastbind overlay and have retrived the
'authtimestamp' attribute on openldap 2.4.30. What I found is that the
timestamps on the attribute have different values on the master server
and slave servers. Is there any way to fix this issue? An application
developer wants to retreive this value to create a report on 90 days of
inactivity for users and since the attribute has different vlaues on
different servers the testing on the accuracy of the report is failing.
I'm sorry but I think RTFM is not the good answer this time ;) authtimestamp is not managed by ppolicy but by the lastbind overlay.
To answer the question, I think the only thing to do is check all directories to create the report. It should be not be difficult for your application developer.
Sr. Member of Technical Staff
A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration