[389-users] Replication and Password Changes

Tom Tucker tktucker at gmail.com
Wed Nov 9 01:11:07 UTC 2011


Please pardon any blunders in my LDAP vernacular.  My LDAP exposure has
been limited thus far.

I am testing Fedora 389 Directory Server as a replacement from my antique
Sun One (5.X) directory server. Things have gone well so far btw.

Q1) My first hurdle was confirming my ability to perform succesful export
and imports between the two platforms.  As I continue to test, what is the
recommended approach for importing any changes since my last import? Do I
need to delete everything on the Fedora DS and do a fresh import or what?
Any recommendations here? If yes, please provide steps.

Q2) My company has three data centers.  My initial thought was to configure
the new ldap environment in a multi-master configuration. Assuming ServerA
(in DC3 is unavailable (shown below) and clients are now communicating with
ServerB, how do we handle any password changes on the client side? Is this
just not possible or do I need to reconsider my architecture?

DC1 ServerA (supplier)
    ServerB (consumer RO)

DC2 ServerA (supplier)
    ServerB (consumer RO)

DC3 ServerA (supplier)
    ServerB (consumer RO)

Thank you for your time and assistance.


System Data
-------------------
389-dsgw-1.1.7-2.fc15.i686
389-console-1.1.7-1.fc15.noarch
389-admin-1.1.23-1.fc15.i686
389-adminutil-1.1.14-1.fc15.i686
389-ds-base-1.2.10-0.4.a4.fc15.i686
389-ds-console-doc-1.2.6-1.fc15.noarch
389-ds-console-1.2.6-1.fc15.noarch
389-ds-1.2.1-2.fc15.noarch
389-ds-base-libs-1.2.10-0.4.a4.fc15.i686
389-admin-console-1.1.8-1.fc15.noarch
389-admin-console-doc-1.1.8-1.fc15.noarch


# cat /etc/redhat-release
Fedora release 15 (Lovelock)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/389-users/attachments/20111108/20b90b80/attachment.html>


More information about the 389-users mailing list