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

Re: Replication/ Clients update slave

To: Thorsten Mauch <mauch@imkenberg.de>
Subject: Re: Replication/ Clients update slave
From: Andreas <andreas@conectiva.com.br>
Date: Thu, 9 Oct 2003 13:15:13 -0300
Cc: "'openldap-software@OpenLDAP.org'" <openldap-software@OpenLDAP.org>
Content-disposition: inline
In-reply-to: <E5A63F34D141D111A6F4080009D70ACA346E88@imkedv_pdc>
References: <E5A63F34D141D111A6F4080009D70ACA346E88@imkedv_pdc>
User-agent: Mutt/1.5.4i

On Wed, Oct 08, 2003 at 11:59:15PM +0200, Thorsten Mauch wrote:
> the replication from the master to the slave work perfect. 
> My problem is that the clients can update the slave server directly, instead
> of beeing
> forwarded to the master server. 

Only the updatedn can write to the slave. If your clients use this dn,
then they will be able to write to the slave. Solution: do not use the
dn in updatedn for anything else than for the replication process.

References:
- Replication/ Clients update slave
  - From: Thorsten Mauch <mauch@imkenberg.de>

Prev by Date: Re: Postfix 2.0.16 CRAM/DIGEST-MD5 SMTP AUTH
Next by Date: Greater-equal/Less-than-equal comparisons
Index(es):
- Chronological
- Thread