Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1462348

Summary: [rfe] sssd should be able to process host-based security filtering when processing active directory gpos
Product: Red Hat Enterprise Linux 8 Reporter: Striker Leggette <striker>
Component: sssdAssignee: SSSD Maintainers <sssd-maint>
Status: CLOSED ERRATA QA Contact: sssd-qe <sssd-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: abokovoy, atikhono, dlavu, grajaiya, jhrozek, lslebodn, mkosek, mzidek, pbrezina, rharwood, sbose, sgoveas, ssorce, thalman, tscherf
Target Milestone: pre-dev-freezeKeywords: FutureFeature, Triaged
Target Release: 8.1Flags: striker: needinfo-
pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard: sync-to-jira
Fixed In Version: sssd-2.3.0-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-04 02:04:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Striker Leggette 2017-06-16 19:47:33 UTC
[+] Description of problem:
 - Active Directory GPOs which are applied to Linux hosts per their security filtering should be properly handled by SSSD.  At the moment, GPOs can only be applied to Linux hosts which live within the OU that the GPO is linked to.

Comment 3 Jakub Hrozek 2017-06-28 18:38:25 UTC
Upstream ticket:
https://pagure.io/SSSD/sssd/issue/3443

Comment 9 Michal Zidek 2018-11-12 12:10:27 UTC
I am just adding a short summary for convenience:

On Win server machine it is possible to specify security filter for each GPO. This filter can contain users, groups and host entries. The meaning of the filter is "this GPO is applicable only if we deal with entries specified in this list".

SSSD currently ignores the host entries and only works with user and group entries so if the list contains host A and no users/groups SSSD will always evaluate the GPO as not applicable even if users log into host A.

Comment 13 Michal Zidek 2020-07-29 07:58:36 UTC
Sorry I have not answered the question before. I do not remember what the behaviour should be exactly, but as a rule of thumb we always wanted to have the behaviour as close to Windows clients as possible, so whatever Windows clients are doing in that situation SSSD should do the same.

Comment 18 Dan Lavu 2020-09-02 15:09:26 UTC
Verified against sssd-2.3.0-8.el8.x86_64

[ci-vm-10-0-107-229.h] ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
[ci-vm-10-0-107-229.h] ::   parent domain Don't ignore host entries in Group Policy security filters
[ci-vm-10-0-107-229.h] ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
[ci-vm-10-0-107-229.h] :: [ 09:23:49 ] :: [   LOG    ] :: GPO :: Moving CN=CLIENT1,CN=Computers,DC=adgpo12r83,DC=com to OU=GPO,DC=adgpo12r83,DC=com
[ci-vm-10-0-107-229.h] :: [ 09:24:01 ] :: [   LOG    ] :: GPO :: Setting Authenticated Users permissions to None for computer_policy
[ci-vm-10-0-107-229.h] :: [ 09:24:25 ] :: [   LOG    ] :: GPO :: Setting CLIENT1$ permissions to GpoRead for computer_policy
[ci-vm-10-0-107-229.h] :: [ 09:25:03 ] :: [   PASS   ] :: File '/var/log/sssd/sssd_adgpo12r83.com.log' should contain 'Option ad_gpo_access_control has value enforcing'
[ci-vm-10-0-107-229.h] :: [ 09:25:03 ] :: [  BEGIN   ] :: Running 'ssh_user_password_login 'allowed_ou_user' Secret123'
[ci-vm-10-0-107-229.h] :: [ 09:25:09 ] :: [   PASS   ] :: Command 'ssh_user_password_login 'allowed_ou_user' Secret123' (Expected 0, got 0)
[ci-vm-10-0-107-229.h] :: [ 09:25:09 ] :: [  BEGIN   ] :: Running 'ssh_user_password_login 'allowed_ou_user1' Secret123'
[ci-vm-10-0-107-229.h] :: [ 09:25:15 ] :: [   PASS   ] :: Command 'ssh_user_password_login 'allowed_ou_user1' Secret123' (Expected 0, got 0)
[ci-vm-10-0-107-229.h] :: [ 09:25:15 ] :: [  BEGIN   ] :: Running 'ssh_user_password_login 'regular_user' Secret123'
[ci-vm-10-0-107-229.h] :: [ 09:25:21 ] :: [   PASS   ] :: Command 'ssh_user_password_login 'regular_user' Secret123' (Expected 0, got 0)
[ci-vm-10-0-107-229.h] :: [ 09:25:21 ] :: [  BEGIN   ] :: Running 'ssh_user_password_login 'denied_ou_user' Secret123'
[ci-vm-10-0-107-229.h] :: [ 09:25:27 ] :: [   PASS   ] :: Command 'ssh_user_password_login 'denied_ou_user' Secret123' (Expected 0, got 0)
[ci-vm-10-0-107-229.h] :: [ 09:25:27 ] :: [  BEGIN   ] :: Running 'ssh_user_password_login 'denied_ou_user1' Secret123'
[ci-vm-10-0-107-229.h] :: [ 09:25:33 ] :: [   PASS   ] :: Command 'ssh_user_password_login 'denied_ou_user1' Secret123' (Expected 0, got 0)
[ci-vm-10-0-107-229.h] :: [ 09:25:33 ] :: [   LOG    ] :: GPO :: Linking computer_policy to OU=GPO,DC=adgpo12r83,DC=com
[ci-vm-10-0-107-229.h] :: [ 09:26:12 ] :: [   PASS   ] :: File '/var/log/sssd/sssd_adgpo12r83.com.log' should contain 'Option ad_gpo_access_control has value enforcing'
[ci-vm-10-0-107-229.h] :: [ 09:26:12 ] :: [  BEGIN   ] :: Running 'ssh_user_password_login 'allowed_ou_user' Secret123'
[ci-vm-10-0-107-229.h] :: [ 09:26:18 ] :: [   PASS   ] :: Command 'ssh_user_password_login 'allowed_ou_user' Secret123' (Expected 0, got 0)
[ci-vm-10-0-107-229.h] :: [ 09:26:18 ] :: [  BEGIN   ] :: Running 'ssh_user_password_login 'allowed_ou_user1' Secret123'
[ci-vm-10-0-107-229.h] :: [ 09:26:24 ] :: [   PASS   ] :: Command 'ssh_user_password_login 'allowed_ou_user1' Secret123' (Expected 0, got 0)
[ci-vm-10-0-107-229.h] :: [ 09:26:24 ] :: [  BEGIN   ] :: Running 'ssh_user_password_login 'regular_user' Secret123'
[ci-vm-10-0-107-229.h] :: [ 09:26:25 ] :: [   PASS   ] :: Command 'ssh_user_password_login 'regular_user' Secret123' (Expected 255, got 255)
[ci-vm-10-0-107-229.h] :: [ 09:26:25 ] :: [  BEGIN   ] :: Running 'ssh_user_password_login 'denied_ou_user' Secret123'
[ci-vm-10-0-107-229.h] :: [ 09:26:25 ] :: [   PASS   ] :: Command 'ssh_user_password_login 'denied_ou_user' Secret123' (Expected 255, got 255)
[ci-vm-10-0-107-229.h] :: [ 09:26:25 ] :: [  BEGIN   ] :: Running 'ssh_user_password_login 'denied_ou_user1' Secret123'
[ci-vm-10-0-107-229.h] :: [ 09:26:26 ] :: [   PASS   ] :: Command 'ssh_user_password_login 'denied_ou_user1' Secret123' (Expected 255, got 255)
[ci-vm-10-0-107-229.h] :: [ 09:26:26 ] :: [   LOG    ] :: GPO :: Moving CN=CLIENT1,OU=GPO,DC=adgpo12r83,DC=com to CN=Computers,DC=adgpo12r83,DC=com
[ci-vm-10-0-107-229.h] :: [ 09:26:39 ] :: [   LOG    ] :: GPO :: Unlinking computer_policy from OU=GPO,DC=adgpo12r83,DC=com

Comment 21 errata-xmlrpc 2020-11-04 02:04:28 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:4569