Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1111528 - Expired shadow policy user(shadowLastChange=0) is not prompted for password change
Expired shadow policy user(shadowLastChange=0) is not prompted for password c...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd (Show other bugs)
6.6
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Jakub Hrozek
Kaushik Banerjee
: Regression
Depends On: 1089250
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-20 04:58 EDT by Kaushik Banerjee
Modified: 2015-11-19 16:53 EST (History)
10 users (show)

See Also:
Fixed In Version: sssd-1.11.6-25.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1089250
Environment:
Last Closed: 2014-10-14 00:48:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1375 normal SHIPPED_LIVE sssd bug fix and enhancement update 2014-10-13 21:06:25 EDT

  None (edit)
Comment 1 Jakub Hrozek 2014-08-20 10:45:52 EDT
This is a regression caused by rewrite of the error codes in 1.10
Comment 2 Jakub Hrozek 2014-08-20 11:41:51 EDT
Here is a test build:
http://brewweb.devel.redhat.com/brew/taskinfo?taskID=7863299

It would be nice if QE could confirm the fix helps.
Comment 3 Kaushik Banerjee 2014-08-21 05:18:02 EDT
(In reply to Jakub Hrozek from comment #2)
> Here is a test build:
> http://brewweb.devel.redhat.com/brew/taskinfo?taskID=7863299
> 
> It would be nice if QE could confirm the fix helps.

Works with the scratch build. User is now prompted for the password change. Thanks Jakub.
Comment 4 Jakub Hrozek 2014-08-21 05:22:52 EDT
(In reply to Kaushik Banerjee from comment #3)
> (In reply to Jakub Hrozek from comment #2)
> > Here is a test build:
> > http://brewweb.devel.redhat.com/brew/taskinfo?taskID=7863299
> > 
> > It would be nice if QE could confirm the fix helps.
> 
> Works with the scratch build. User is now prompted for the password change.
> Thanks Jakub.

Thank you very much for testing. I will build an official package once the patch is merged upstream.
Comment 8 Kaushik Banerjee 2014-08-28 05:20:21 EDT
Verified with sssd-1.11.6-28.el6

Output from beaker run:
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: shadow7: Account expired
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
modifying entry "uid=shadowuser1,ou=Users,dc=example,dc=com"

Stopping sssd: [  OK  ]
Starting sssd: [  OK  ]

spawn ssh -o StrictHostKeyChecking=no -l shadowuser1 localhost
shadowuser1@localhost's password: 
Password expired. Change your password now.
WARNING: Your password has expired.
You must change your password now and login again!
Changing password for user shadowuser1.
Current Password: 
New password: 
Retype new password: 
:: [   LOG    ] :: Sleeping for 5 seconds
:: [   PASS   ] :: File '/var/log/sssd/sssd_LDAP.log' should contain 'Found shadow password expiration attributes' 
:: [   PASS   ] :: File '/var/log/sssd/sssd_LDAP.log' should contain 'Last change day is not set, new password needed' 
:: [   PASS   ] :: File '/var/log/sssd/sssd_LDAP.log' should contain 'Initial authentication for change password operation successful' 
:: [   LOG    ] :: Duration: 9s
:: [   LOG    ] :: Assertions: 3 good, 0 bad
:: [   PASS   ] :: RESULT: shadow7: Account expired
Comment 9 errata-xmlrpc 2014-10-14 00:48:53 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1375.html
Comment 10 Trevor Vaughan 2015-11-19 16:53:58 EST
I know that this is closed, but when performing the test above, did the user have a valid SSH key in LDAP?

Is the user still prompted for a password change if they do have a valid SSH key?

If they are not, this is a deviation from the way that NSCD has always functioned.

Thanks,

Trevor

Note You need to log in before you can comment on or make changes to this bug.