Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1513277
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
* Description of problem: SSSD is unable to handle "User must Change the password at next login" setting in AD if auth_provider = ldap is used * Version-Release number of selected component (if applicable): sssd-1.15.2-50.el7_4.6 * How reproducible: Always * Steps to Reproduce: 1. Integrate RHEL macine with AD domain using sssd with id_provider = ldap and auth_provider = ldap 2. For an AD user tick/check "User must Change the password at next login" in AD 3. Try to login as AD user on RHEL it will fail and won't give you prompt to reset password * Actual results: AD user login fails with: --- # ssh aduser@localhost Sat Nov 11 00:25:30 CET 2017 aduser@localhost's password: Permission denied, please try again. aduser@localhost's password: Permission denied, please try again. aduser@localhost's password: Ctrl+c --- Expected results: AD user login should work and it should force user to change its password with: --- # ssh aduser@localhost aduser@localhost's password: <----- Current Password Password expired. Change your password now. Creating home directory for aduser password has expired. You must change your password now and login again! Changing password for user aduser. Current Password: <----- Current Password New password: <----- New Password Retype new password: <----- New Password passwd: all authentication tokens updated successfully. Connection to localhost closed. --- Additional info: I have already discussed this issue with Jakub and as he stated this has been never implemented in SSSD and thus filed this bug.
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1513277
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD Patches welcome
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Thank you for understanding.
Metadata Update from @pbrezina: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/4606
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.
Login to comment on this ticket.