[Date Prev][Date Next]
Re: ldapmodify when using syncrepl fails due to referral (ITS#2715)
[redirected to openldap-devel]
I note that Jong and I chatted about adding a "turn" capability
to the SyncRepl engine. It is desirable to support both
consumer->provider connections (as SyncRepl currently supports)
and provider->consumer connections (as slurpd(8) does).
To provide this, I was thinking that slapd(8) (on the consumer):
updatedn="cn=Replica,o=University of Michigan,c=US"
binddn="cn=Manager,o=University of Michigan,c=US"
searchbase="o=University of Michigan,c=US"
and on the producer
where string is used to coordinate the turn (and possibly be used
in turn authorization). The producer (client) would connect to
the consumer (server), after authenticating, issue a TURN extended
op (providing the string). The connection would then turn. That
is, the producer would become the server and the consumer would
become the client. Then the consumer would initiate syncrepl.
Thoughts on this (and contributions) welcomed.
At 03:09 PM 9/11/2003, email@example.com wrote:
>--On Thursday, September 11, 2003 6:00 PM -0400 Jonghyuk Choi
>>> You are saying the slave needs to have access to bind to the master? So
>>> each slave needs permission to bind to the master to read the data it
>> yes. just like ordinary search requests...
>Okay, that is a major departure from how things were done previously via
>slurpd (slurpd had to have permission to bind to the slave). Well, that
>makes things interesting. I'll have to figure out how we want to set that
>up on our end, as it means we now have to run a process to get kerberos
>tickets on all the replica's, and grant them access into the master, which
>they previously didn't have.
>Principal Software Developer
>GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html