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.

Description of problem:
This bugzilla tracks the upstream ticket https://fedorahosted.org/sssd/ticket/2751

It's required to fix to process some GPO files from Windows.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Upstream ticket:
https://fedorahosted.org/sssd/ticket/2751

Michal, can you add some steps to reproduce?

Steps to reproduce:

1. configure SSSD as AD client with enforced GPO access control. Add this line to the domain section in sssd.conf

ad_gpo_access_control = enforcing

2. Create user1 in AD

3. create a GPO for access control on the AD server. The GPO must apply to the client machine and allow login for user1. The GPO ini file must contain line with no equal sign. For example add this as the last line in the GPO ini file

foo,"2"

4. try to login as user1 from AD

Current result:
Access for user1 is denied.

Expected result:
user1 should be able to login.