RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1385665 - Incorrect error code returned from krb5_child (updated)
Summary: Incorrect error code returned from krb5_child (updated)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Sumit Bose
QA Contact: Dan Lavu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-17 13:12 UTC by Dan Lavu
Modified: 2020-11-04 21:13 UTC (History)
9 users (show)

Fixed In Version: sssd-1.16.0-22.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 10:40:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 4231 0 None closed Incorrect error code returned from krb5_child for expired/locked user with id_provider AD 2020-11-09 03:06:07 UTC
Red Hat Product Errata RHSA-2018:3158 0 None None None 2018-10-30 10:41:50 UTC

Description Dan Lavu 2016-10-17 13:12:26 UTC 
Description of problem:

It seems that the exit status has changed causing the following automated test that is used for regression testing to fail.

account-password-policy-003-User-account-disabled
account-password-policy-004-bz1081046-User-account-is-expired 


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


How reproducible:
Always


Steps to Reproduce:
1. Run the AD Parameters test
2. The following test cases; account-password-policy-003-User-account-disabled and account-password-policy-004-bz1081046-User-account-is-expired fails.
3.

Actual results:

:: [   FAIL   ] :: File '/var/log/secure' should contain 'User account has expired' 
:: [   FAIL   ] :: Command 'id user1-1478375 | cut -f2 -d " " | grep group1-1478375' (Expected 0, got 1)

Expected results:

:: [   PASS   ] :: File '/var/log/secure' should contain 'User account has expired' 
:: [   PASS   ] :: Command 'id user1-1478375 | cut -f2 -d " " | grep group1-1478375' (Expected 0, got 1)

Additional info:


Previous patch that caused this bug.

https://lists.fedorahosted.org/archives/list/sssd-devel@lists.fedorahosted.org/thread/OM2BME5DKH3HBD23BB5SC73I5VTATIGD/#FFKZZXSHZXYIC3P6H3P4Z5INSPEZD6MC
Comment 1 Lukas Slebodnik 2016-10-17 13:19:00 UTC 
Upstream ticket:
https://fedorahosted.org/sssd/ticket/3198
Comment 2 Lukas Slebodnik 2016-10-17 13:27:00 UTC 
> Previous patch that caused this bug.
> 
> https://lists.fedorahosted.org/archives/list/sssd-devel@lists.fedorahosted.
> org/thread/OM2BME5DKH3HBD23BB5SC73I5VTATIGD/#FFKZZXSHZXYIC3P6H3P4Z5INSPEZD6MC
The behaviour before the change was not correct either. sssd returned error code for expired user even for disabled user.

The current behaviour is that sssd returns error code for disabled user for expired and disabled user.

This BZ should properly distinguish between expired and disabled user from AD with id provider ad
Comment 4 Jakub Hrozek 2017-03-28 08:09:58 UTC 
This bugzilla still needs work upstream. Because we are nearing the development freeze of RHEL-7.4 and the work is not finished yet, I'm reproposing the bug to RHEL-7.5.

Please push back if you disagree.
Comment 8 Jakub Hrozek 2018-02-07 14:00:31 UTC 
* master:
 * d380148b0a23dd1a04d1d0767ba41d3e76fb7d23
 * 5a7b76bf3dc1b7a4a6ca6608c750cbffef73a3eb
Comment 10 Dan Lavu 2018-07-18 18:42:34 UTC 
Verified. 

Jul 18 02:39:44 cypher sshd[25498]: pam_sss(sshd:account): system info: [The user account is expired on the AD server]
Jul 18 02:39:44 cypher sshd[25498]: pam_sss(sshd:account): Access denied for user testuser01-2620451: 13 (User account has expired)
Jul 18 02:39:44 cypher sshd[25498]: fatal: Access denied for user testuser01-2620451 by PAM account configuration [preauth]
Jul 18 02:42:38 cypher su: pam_unix(su:session): session opened for user nobody by (uid=0)


tested against sssd-1.16.2-7.el7.x86_64, test case needs to be updated since the secure message has changed.
Comment 12 errata-xmlrpc 2018-10-30 10:40:47 UTC 
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.

https://access.redhat.com/errata/RHSA-2018:3158
Note You need to log in before you can comment on or make changes to this bug.