To exemplify the issues I'll use the model: AD <-> RHDS1 <-> RHDS2.Only one master is setup to sync to AD, which is the standard setup. Since password sync uses clear text to replicate to AD, password changes on RHDS2 will not propagate correctly to AD. RHDS2 sends the hash to RHDS1 which in turn sends it to AD. AD assumes the hash to be the actual clear text pw and attempts to use it to login to RHDS1. This creates a loop where one server keeps sending what it believes to be the new password to the other. I _think_ that if I add a replication agreement between RHDS2 and AD it will not fix my problem as even if RHDS2 sends the password ok to AD, RHDS1 will still try to send the update it received from RHDS2. Is this assumption correct? What is the best course of action? How can I tell if a password update is done on the server or pushed thru replication?
--- Begin Message ---I am using RHDS instead of FD, so if this issue has been addressed in FD please forgive me.
- To: fedora-directory-users@xxxxxxxxxx
- Subject: Password replication problems between a multi-master system and AD
- From: Alexandre Augusto da Rocha <augusto.rocha@xxxxxxxxxxxxxxxx>
- Date: Mon, 19 Mar 2007 19:23:17 -0500
- Organization: August Schell
- User-agent: Thunderbird 1.5.0.9 (Windows/20061207)
To exemplify the issues I'll use the model: AD <-> RHDS1 <-> RHDS2.Only one master is setup to sync to AD, which is the standard setup. Since password sync uses clear text to replicate to AD, password changes on RHDS2 will not propagate correctly to AD. RHDS2 sends the hash to RHDS1 which in turn sends it to AD. AD assumes the hash to be the actual clear text pw and attempts to use it to login to RHDS1. This creates a loop where one server keeps sending what it believes to be the new password to the other. I _think_ that if I add a replication agreement between RHDS2 and AD it will not fix my problem as even if RHDS2 sends the password ok to AD, RHDS1 will still try to send the update it received from RHDS2. Is this assumption correct? What is the best course of action? How can I tell if a password update is done on the server or pushed thru replication?Attachment: smime.p7s
Description: S/MIME Cryptographic Signature
--- End Message ---
-- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
