Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1366699

Summary: Passwords are not Synchronized!!!
Product: Red Hat Directory Server Reporter: Alex <ricardoalx.perez>
Component: Directory ConsoleAssignee: mreynolds
Status: CLOSED INSUFFICIENT_DATA QA Contact: Viktor Ashirov <vashirov>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 11.0CC: mreynolds, nhosoi, nkinder, ricardoalx.perez
Target Milestone: ---Flags: nhosoi: needinfo? (ricardoalx.perez)
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-06 15:54:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Alex 2016-08-12 15:29:25 UTC
Description of problem:
I have a sync settings between 389 Directory Server and Microsoft Active Directory, it works correctly , I can replicate changes to users in both directions , ( 389 DS to MS AD , and MS AD to 389 DS ) , the only detail is not synchronize user passwords .

Version-Release number of selected component (if applicable):

rpm -qa | grep 389


How reproducible:

Steps to Reproduce:
1. On Microsoft Active Directory create a new user
2. On 389 Directory Server start the synchronization process
3. Replica acquired successfully: Incremental update succeeded
4. No errors during the synchronization process
5. Users and Groups are sincronized

Actual results: Synchronized users no have a valid password

The password is not synchronized

Expected results:  Synchronized users have a valid password, The password is not synchronized

Additional info:

Comment 2 Nathan Kinder 2017-04-06 15:54:46 UTC
We need more info (which was asked for back in August) to troubleshoot this issue.  Closing as INSUFFICIENT_DATA.