Okay here is what we are wanting to do and I need to know if it is possible with openLDAP. We have a main production ldap server v. 2.4.28 running on Ubuntu 10.04 We are adding two servers that will handle authenication and refer writes to the main provider server. What I would like to to setup another provider in our DR site and have it pull replication from the main LDAP server once a day, maybe twice. Then in turn that server would be the provider for two consumers at the DR site that would handle auth requests and refer write to the provider at the DR site. But the no changes at the DR site would be written back to the main production provider. I don't want someone testing something in the DR to be written back to production.
In a nut shell I want to have two systems that look the same and the information for the second system would come from a sync with the first system, but the second system would not be able to write back to the main system.
Thanks, Eric Speake Web Systems Administrator O'Reilly Auto Parts
This communication and any attachments are confidential, protected by Communications Privacy Act 18 USCS � 2510, solely for the use of the intended recipient, and may contain legally privileged material. If you are not the intended recipient, please return or destroy it immediately. Thank you.
On 07/31/13 10:29 AM, espeake@oreillyauto.com wrote:
Okay here is what we are wanting to do and I need to know if it is possible with openLDAP. We have a main production ldap server v. 2.4.28 running on Ubuntu 10.04 We are adding two servers that will handle authenication and
Someone will inevitably tell you to step up to the latest release, so it might as well be me. :)
Now that that's out of the way...
In a nut shell I want to have two systems that look the same and the information for the second system would come from a sync with the first system, but the second system would not be able to write back to the main system.
This kind of conflicts with your previous paragraph, which seems to say that you want two systems that look the same and the second replicating from the first, but you want BOTH to be writable.
I don't see how this would be sustainable. It's pretty much guaranteed that at some point someone will make a change on your "DR" node that will foul up the synchronization, such as deleting a container or an object. You're setting yourself up for a split brain situation.
If you're willing to let the second node be read-only, then what you want to do is more reasonable.
openldap-technical@openldap.org