[Date Prev][Date Next]
Re: updateref not working
In a word...no.
So, with that, I can go back to my client software and check to see
how they're handling it.
What you may be saying, though, is that the configs seem to be good,
but if the client software doesn't support it, it doesn't matter.
More or less correct? The client software that brought this up was
I'll check on things on my side. Thanks for the guidance.
On 3/1/06, Quanah Gibson-Mount <email@example.com> wrote:
> Sean Hussey wrote:
> > Hi everyone,
> > We're on OpenLDAP 2.2.29, but we've had this problem since 2.2.17 (or
> > so). Our master is configured to replicate to the slaves via slurpd.
> > That works.
> > What doesn't work is having the slaves update the master when a change
> > comes through. As far as I know, these are the configurations we
> > need:
> > Slave servers:
> > updatedn "uid=replica,dc=host,dc=com"
> > updateref ldap://ldapmaster.host.com
> > Master server:
> > replica uri=ldap://ldapchild1.host.com:389
> > suffix="dc=host,dc=com"
> > binddn="uid=replica,dc=host,dc=com"
> > credentials=secret
> > bindmethod=simple
> > tls=yes
> > uid=replica is the rootdn of the slaves. On the slaves, rootpw is an
> > MD5 hash. On the master, the credentials are plaintext. Could that
> > be the issue?
> Not likely. Do you understand how things operate when a write attempt
> is made to a slave? I.e., do you understand what referrals are, and,
> more importantly, does the client software trying to make the write to
> the slave understand referrals?