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.
+++ This bug was initially created as a clone of Bug #1404697 +++
Description of problem:
If the groupPolicyContainer created by some tool (for example the https://www.quest.com/products/password-manager/) does not conatin gpcFunctionalityVersion attribute and sssd stumbles upon such container, it stops the processing and just quit with the default decision (wich is usually deny).
To avoid this problem, the SSSD should skip any GPO that does not contain the gpcFunctionalityVersion because this is the behavior specified by the MS-GPOL, see 3.2.5.1.6:
-----
3.2.5.1.6 GPO Filter Evaluation
In this step, the client MUST process the GPO as follows:
1. Check for the functionality version of the GPO. If the gPCFunctionalityVersion
field of the Group Policy Object Search message (as defined in [MS-ADA1]
section 2.278) is not set to 2, the GPO MUST NOT be included in the rest
of the protocol sequence. The GPO MUST be considered denied.
-----
given that the GPO itself does not have access control rules, you filter
it out.
Version-Release number of selected component (if applicable):
sssd-1.14.0-43.el7.x86_64
Steps to Reproduce:
1. create GPO with https://www.quest.com/products/password-manager/
2. try to log in with such user
Actual results:
login fails
Expected results:
should log in
--- Additional comment from Andrey Bondarenko on 2016-12-14 08:48:48 EST ---
Correct versions for the 6.8 related bug:
sssd-1.13.3-22.el6_8.4.x86_64 Sun Oct 30 11:19:34 2016
sssd-ad-1.13.3-22.el6_8.4.x86_64 Sun Oct 30 11:19:32 2016
sssd-client-1.13.3-22.el6_8.4.x86_64 Sun Oct 30 11:19:30 2016
sssd-common-1.13.3-22.el6_8.4.x86_64 Sun Oct 30 11:19:31 2016
Verified against sssd-1.15.2-24.el7.x86_64, the user is able to login and the policy with the deleted attribute is ignored.
---
[root@dell-per905-01 /]# ssh test_sssd@localhost
test_sssd@localhost's password:
Last login: Wed May 17 16:38:03 2017 from ::1
---
(Wed May 17 16:31:51 2017) [sssd[be[sssdad2012r2.com]]] [ad_gpo_sd_process_attrs] (0x4000): smb_path: /sssdad2012r2.com/Policies/{0A72F5AD-88B2-48C8-B220-8779592E03F9}
(Wed May 17 16:31:51 2017) [sssd[be[sssdad2012r2.com]]] [ad_gpo_sd_process_attrs] (0x4000): GPO with GUID {0A72F5AD-88B2-48C8-B220-8779592E03F9} is missing attribute gPCFunctionalityVersion and will be skipped.
00C04FB984F9}
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/RHEA-2017:2294