Description of problem: When a user password change is made in RHDS and PassSync "Successfully" makes that changes to Active Directory. The user pwdLastSet attribute is not update. This creating a major problem. User are forced to change password every 90 days. User logs into ldap, changes their password. That password changes is reflected in Active Directory. But when the long into a AD there force again to change their password. Customer is using Windows 2016 Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Set same password policy in RHDS and Windows. Users are forced to change there password every 90 days. 2. When password for AD user expires in RHDS he is prompted for password change 3. After password change in RHDS when AD user login next day in Windows he is prompted to change his password. Actual results: User is prompted to change password in windows even after the user changed his password (as self) in RHDS. Expected results: When user is changing the password as self in RHDS then after successful password change user should not be prompted to change the password again in RHDS. The user should be forced to change his password in RHDS/Windows if the password has been reset by Administrator. Additional info:
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1597202
Metadata Update from @mreynolds: - Issue assigned to mreynolds
https://pagure.io/389-ds-base/pull-request/49952
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to review - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 1.3.8 (was: 0.0 NEEDS_TRIAGE)
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
1a93d63..ac500d3 389-ds-base-1.3.9 -> 389-ds-base-1.3.9
818807d..f13039b 389-ds-base-1.3.8 -> 389-ds-base-1.3.8
1448415..7e83f2a 389-ds-base-1.3.7 -> 389-ds-base-1.3.7
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3009
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.