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 1342058 - In IPA-AD trust environment access is granted to AD user even if the user is disabled on AD.
Summary: In IPA-AD trust environment access is granted to AD user even if the user is ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd
Version: 6.7
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: SSSD Maintainers
QA Contact: Steeve Goveas
URL:
Whiteboard:
Depends On: 1335400
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-02 11:07 UTC by Marcel Kolaja
Modified: 2020-05-04 10:56 UTC (History)
10 users (show)

Fixed In Version: sssd-1.13.3-22.el6_8.3
Doc Type: Bug Fix
Doc Text:
If an Active Directory (AD) user with a disabled user account attempts to log in, Identity Management (IdM) is expected to deny access. Previously, the login attempt succeeded when the user used a login method other than the standard password login, such as an SSH key. To fix this problem, IdM no longer checks only the IdM-specific account lockout attributes, but also the AD lockout attributes. As a result, an AD user with a disabled user account is no longer permitted to log in with an SSH key.
Clone Of: 1335400
Environment:
Last Closed: 2016-07-12 18:36:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 3968 0 None closed In IPA-AD trust environment access is granted to AD user even if the user is disabled on AD. 2021-01-18 05:56:35 UTC
Red Hat Product Errata RHBA-2016:1407 0 normal SHIPPED_LIVE sssd bug fix update 2016-07-12 22:32:15 UTC

Description Marcel Kolaja 2016-06-02 11:07:49 UTC
This bug has been copied from bug #1335400 and has been proposed
to be backported to 6.8 z-stream (EUS).

Comment 4 Kaleem 2016-07-04 10:39:10 UTC
Verified.

[root@dhcp207-58 ~]# rpm -q sssd
sssd-1.13.3-22.el6_8.4.x86_64
[root@dhcp207-58 ~]# 

Snip from console output.
=========================
[root@dhcp207-58 ~]# ssh -i /home/ipaad2012r2.test/aduser1/.ssh/id_rsa aduser1@dhcp207-62.testrelm.test
Connection closed by UNKNOWN
[root@dhcp207-58 ~]# ldapsearch -x -h  x.x.x.x -D "Administrator" -W -b "cn=Aduser1 user,cn=users,dc=ipaad2012r2,dc=test" -s sub "userAccountControl"
Enter LDAP Password: 
....
.....
# Aduser1 user, Users, ipaad2012r2.test
dn: CN=Aduser1 user,CN=Users,DC=ipaad2012r2,DC=test
userAccountControl: 66050

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1
[root@dhcp207-58 ~]#

Comment 7 errata-xmlrpc 2016-07-12 18:36:11 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/RHBA-2016:1407


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