[Date Prev][Date Next] [Chronological] [Thread] [Top]

Problem between ldappasswd and replication

I 'm using openldap 2.0.11 and all is ok except when I use ldappasswd to
change any password,
nothing appear in replica log, so my slave server are not synchronize. ( we
can notice that's other
modification , if i update  an other value by other way (ldapclient) all
synchrinisation is ok.

Is it normal ?

Thanks a lot

> -----Message d'origine-----
> De : owner-openldap-devel@OpenLDAP.org
> [mailto:owner-openldap-devel@OpenLDAP.org]De la part de Kurt D. Zeilenga
> Envoye : dimanche 15 juillet 2001 17:00
> A : Stig Venaas
> Cc : openldap-devel@OpenLDAP.org
> Objet : Re: how to treat filters with assertion values with bad UTF8?
> At 07:33 AM 7/15/2001, Stig Venaas wrote:
> >I noticed that the CVS devel version segfaulted on case insensitive
> >exact searches with bad UTF8 coding. This is very bad of course. I
> >just fixed it in CVS. The current fix tries to treat this as if there
> >were no matches and returns success. This seems correct according to
> >RFC 2251 which states:
> The filter component should be treated as Undefined
> if the assertion value doesn't conform to the assertion
> syntax.
> >Servers MUST NOT return errors if attribute descriptions or matching
> >rule ids are not recognized, or assertion values cannot be parsed.
> >More details of filter processing are given in section 7.8 of X.511
> This is correct.  The operational successfully matches no entries.
> >I was wondering if I should perhaps use LDAP_FILTER_ERROR though.
> No.  Note that LDAP_FILTER_ERROR is an API error code,
> not a protocol result code.