[Date Prev][Date Next]
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: firstname.lastname@example.org
- Date: Sun, 18 Sep 2005 14:22:34 +0200
- Cc: "Dieter Kluenter" <email@example.com>
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:x-mailer:reply-to:x-priority:message-id:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding; b=YshdRgIFfZuWOWtK0I1aqG8VZUoRBIjHIFMMKLKyOphaXH8YGrRfgRqv/hS9QsusB06zOh3DQVWXI99hKixDfnYYzKGroNxe9EsDXtJGsZmDleSNzDwF32LW/c9Lff6Wfa8wqOtIJJHFwfbSV9s4OYeV8AX0r6elZYUqwAU7Rz4=
- In-reply-to: <firstname.lastname@example.org>
- References: <200509171719.j8HHJ5gI078619@boole.openldap.org> <email@example.com> <firstname.lastname@example.org>
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
-Do the ACL (for LDAP users) on the real main server won't be bypassed ?
-Do I need to design the directory (schema, acl) with the fact that I may use a
- Does populating large group with members (>1000 < 10000) work well
(through proxy) ?
In other words , is the proxy real transparent to Ldap client
operations (read, writes) or Acl, schema definitions
(I don't want to do any attributes or object mapping)
- Do the back-end ldap and proxy cache are stable and reliable enough to be used
in a heavy production env. ?
(The directory must be deployed in 8 month so I hope until then Old
2.3.x will be stable)
Thanks again for your answser.