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 1804005 - sssd doesn't follow the link order of AD Group Policy Management
Summary: sssd doesn't follow the link order of AD Group Policy Management
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Sumit Bose
QA Contact: sssd-qe
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-18 01:07 UTC by Muneaki Sugaya
Modified: 2023-09-07 21:58 UTC (History)
11 users (show)

Fixed In Version: sssd-1.16.5-10.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-29 19:50:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 5103 0 None closed GPO: Incorrect processing / inheritance order of HBAC GPOs 2020-11-03 01:48:22 UTC
Red Hat Issue Tracker SSSD-2174 0 None None None 2023-09-07 21:58:33 UTC
Red Hat Issue Tracker SSSD-2424 0 None None None 2023-09-07 21:58:39 UTC
Red Hat Product Errata RHBA-2020:3904 0 None None None 2020-09-29 19:50:24 UTC

Comment 7 Sumit Bose 2020-02-26 11:42:19 UTC 
Upstream ticket:
https://pagure.io/SSSD/sssd/issue/4145
Comment 11 Pavel Březina 2020-06-05 09:07:33 UTC 
Pushed PR: https://github.com/SSSD/sssd/pull/5159

* `master`
    * dce025b882db7247571b135e928afb47f069a60f - GPO: fix link order in a SOM
* `sssd-1-16`
    * 7cf6b86408e53c5c2c5f6da89aef3dec68223c59 - GPO: fix link order in a SOM
Comment 14 Dan Lavu 2020-06-16 02:52:49 UTC 
Verified against sssd-1.16.5-10.el7.x86_64

Created GPOs, gpo1 permitting user1, gpo2 permitting user2

[root@client1 yum.repos.d]# ssh user1@localhost
user1@localhost's password: 
Last login: Mon Jun 15 22:43:49 2020 from ::1
[user1@client1 ~]$ exit
logout
Connection to localhost closed.

[root@client1 yum.repos.d]# ssh user2@localhost
user2@localhost's password: 
Authentication failed.

Modified the link order, now gpo2 is processed second after the default Default Domain Policy

[root@client1 yum.repos.d]# ssh user2@localhost
user2@localhost's password: 
Last failed login: Mon Jun 15 22:45:02 EDT 2020 from ::1 on ssh:notty
There was 1 failed login attempt since the last successful login.
Last login: Mon Jun 15 22:43:57 2020 from ::1
[user2@client1 ~]$ exit
logout
Connection to localhost closed.

[root@client1 yum.repos.d]# ssh user1@localhost
user1@localhost's password: 
Authentication failed.
Comment 16 errata-xmlrpc 2020-09-29 19:50:00 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 (sssd bug fix and enhancement update), 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-2020:3904
Note You need to log in before you can comment on or make changes to this bug.