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

Re: SuSE eMail Server 3.1 + LDAP slave replication problem

 Thanks Ralf,

So I have another question: according some docs into the Internet, the Samba (both client and server) can use this functionality, but I continue receiving the insuficcient access message. I comment the SMS ACL's and create another more generic:

access to *
       by dn="uid=replication,dc=getnet,dc=com,dc=br" write
       by dn="uid=cyrus,dc=getnet,dc=com,dc=br" write
       by * read
       by self write

I believe that with this ACL I must not have problems. In case this is correct, I request that they indicate me an application (that it has the functionality) for tests.

Thanks for your help...

Best regards,


Ralf Haferkamp wrote:

On Wed, Oct 16, 2002 at 11:42:16AM -0200, Fabiano Felix wrote:

Hi all,

I have a SMS 3.1, which is based on OpenLDAP-2.0.11. I create a cn=replica in the directory, and put the necessary ACLs to us. The Master to Slave replication is OK, but when I try to modify a data in the slave server, and it try to send the information to the master,

The slave server doesn't try to modify the master directly. It sends a
referral (the one configured with updateref) back to the client. The
client then is responsible for updating the records on the master. By
default most clients bind anonymously to the master for this. You would
need to change the clients to bind as a user which has sufficient access
rights to modify the directory. (BTW, the default clients of SLEMS 3.1
don't support this)

receive the following message:
"Insuficcient Access"