Hi Christian, I'm not one of the gurus you were talking about, but I would appreciate that very much anyway!!
I recently filed an ITS asking also for excluding specific entries from having the "authTimestamp" attribute populated (ITS#77076). If you think it should be not so difficult to implement... I would appreciate.
Thanks in advance Marco
On Tue, Oct 8, 2013 at 3:25 PM, Christian Kratzer ck-lists@cksoft.dewrote:
Hi,
it seems this has been asked before but I am not sure of the conclusion:
http://www.openldap.org/lists/**openldap-technical/201211/** msg00078.htmlhttp://www.openldap.org/lists/openldap-technical/201211/msg00078.html
I have setup setup with slapo-lastbind configured on some slaves that have a working chaining configuration to the masters.
It seems that the authTimestmap attribute from slapo-lastbind is not getting replicated.
From looking at the source code for lastbind it seems we would need to implement something similar to olcPPolicyForwardUpdates from ppolicy.c
If none of the gurus here don't object the code looks clean enough that I would attempt to port forwarding of updates from slapo-ppolicy to slapo-lastbind. ( olcLastbindForwardUpdates )
Greetings Christian
-- Christian Kratzer CK Software GmbH Email: ck@cksoft.de Wildberger Weg 24/2 Phone: +49 7032 893 997 - 0 D-71126 Gaeufelden Fax: +49 7032 893 997 - 9 HRB 245288, Amtsgericht Stuttgart Web: http://www.cksoft.de/ Geschaeftsfuehrer: Christian Kratzer