michael,
i know for a fact that the referral is not handled internally, the=20
entry on the master never gets changed. at this point i am not entirely=20=
sure if my slave is indeed configured correctly.
i did read in some unrelated documentation that how the referral is=20
handled differs based on the type of authentication you use. at this=20
moment i am using a simple bind.
jens
P.S.: frohe weihnachten ;)
On Tuesday, Dec 24, 2002, at 10:11 US/Eastern, Michael Str=F6der wrote:
> Jens Vagelpohl wrote:
>> i have done some testing by setting up a master and slave and using=20=
>> the "updateref" directive in the slave's slapd.conf. according to the=20=
>> OpenLDAP documentation that should cause the slave to hand back the=20=
>> URI designated in the updateref directive if someone attempts a >> =
write.
>> [..]
>> conn.set_option(ldap.OPT_DEREF, ldap.DEREF_ALWAYS)
>
> This option is for setting alias dereferencing which is something=20
> different.
>
>> but this does not seem to make a change.
>
> Maybe the OpenLDAP lib handles the referral internally and already=20
> changes the entry on your master?
>
> If you don't want to let the OpenLDAP lib handle the referral you have=20=
> to use:
>
> conn.set_option(ldap.OPT_REFERRALS,0)
>
> Ciao, Michael.
>
|