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

Re: Being a consumer and a provider for the same database (toward different servers) ?

To: openldap-software@OpenLDAP.org
Subject: Re: Being a consumer and a provider for the same database (toward different servers) ?
From: Andreas Hasenack <ahasenack@terra.com.br>
Date: Mon, 19 Sep 2005 14:39:36 -0300
Content-disposition: inline
In-reply-to: <1125726346.20050918142234@gmail.com>
References: <200509171719.j8HHJ5gI078619@boole.openldap.org> <182571980.20050917210908@gmail.com> <878xxuwtw1.fsf@rubin.l4b.de> <1125726346.20050918142234@gmail.com>
User-agent: Mutt/1.5.9i

On Sun, Sep 18, 2005 at 02:22:34PM +0200, jmbajet@gmail.com wrote:
> Hello,
> 
> I'am quite new to Ldap and OpenLdap,
> 
> I must propose a solution that is stable and very reliable.
> so I don't know which solution is Best.
> 
> * A hub server which polls changes from subsidiaries and then
> subsidiaries polls changes from other subsidiaries from the hub server
> 
> * Or a back-ldap with proxycaching in the subsidiaries
> 
> 
> -Do LDAP users in the subsidiaries will be seen by the main server as normal direct ldap
> connections ?

Ask yourself this also: what happens when the wan link between the main
server and the subsidiaries breaks down for a few hours?

References:
- Being a consumer and a provider for the same database (toward different servers) ?
  - From: jmbajet@gmail.com
- Re: Being a consumer and a provider for the same database (toward different servers) ?
  - From: "Dieter Kluenter" <dieter@dkluenter.de>
- Re[2]: Being a consumer and a provider for the same database (toward different servers) ?
  - From: jmbajet@gmail.com

Prev by Date: LDAP indirect backend for ACLs
Next by Date: Re: ldap_sasl_interactive_bind_s
Index(es):
- Chronological
- Thread