On 7 Feb 2011 22:31, "Marco Pizzoli" marco.pizzoli@gmail.com wrote:
Hi Jonathan, I understand the "locality" of the attribute, but my question is motivated by the ppolicy_forward_updates directive that addresses this identical problem. Do you think it would be possible to have a similar feature with this overlay?
Thanks Marco On 7 Feb 2011 20:49, "Jonathan CLARKE" jonathan.clarke@normation.com wrote:
Marco Pizzoli wrote:
On 7 Feb 2011 22:31, "Marco Pizzoli" <marco.pizzoli@gmail.com mailto:marco.pizzoli@gmail.com> wrote:
Hi Jonathan, I understand the "locality" of the attribute, but my question is motivated by the ppolicy_forward_updates directive that addresses this identical problem. Do you think it would be possible to have a similar feature with this overlay?
Thanks Marco On 7 Feb 2011 20:49, "Jonathan CLARKE" <jonathan.clarke@normation.com
mailto:jonathan.clarke@normation.com>
wrote:
Note that authTimestamp is a DSA-specific attribute. (Look at its schema definition, it is dsaOperation.) Such attributes are, by design, not replicated, since their content is only meant for and valid on the particular DSA.
Le 07/02/2011 22:36, Marco Pizzoli a écrit :
On 7 Feb 2011 22:31, "Marco Pizzoli" marco.pizzoli@gmail.com wrote:
Hi Jonathan, I understand the "locality" of the attribute, but my question is motivated by the ppolicy_forward_updates directive that addresses this identical problem. Do you think it would be possible to have a similar feature with this overlay?
Well, it's certainly possible, since the lastbind overlay reuses the almost exact portion of code from the ppolicy overlay, the patch could be made pretty simply I guess...
Jonathan
openldap-technical@openldap.org
-
Howard Chu -
Jonathan CLARKE -
Marco Pizzoli