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 2103325 - Supported AD group types should be explained in the docs
Summary: Supported AD group types should be explained in the docs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: sssd
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: jstephen
QA Contact: shridhar
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-02 08:10 UTC by Anton Bobrov
Modified: 2023-05-09 10:28 UTC (History)
10 users (show)

Fixed In Version: sssd-2.8.1-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 08:19:50 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd pull 6263 0 None open MAN: Add note about AD Group types 2022-07-15 07:16:31 UTC
Red Hat Issue Tracker RHELPLAN-126890 0 None None None 2022-07-02 08:11:22 UTC
Red Hat Issue Tracker SSSD-4887 0 None None None 2022-07-14 21:00:52 UTC
Red Hat Product Errata RHBA-2023:2514 0 None None None 2023-05-09 08:20:14 UTC

Description Anton Bobrov 2022-07-02 08:10:22 UTC
Description of problem:

sssd maps only specific AD group types (ie those that contain security related attributes like sid and guid or uidNumber and gidNumber for posix) and while it is quite logical and understandable from implementation perspective it is not at all clear from end user perspective at all which group types are supported and what requirements on AD side are to create groups that can be used with sssd. the docs / man pages should dedicate a small section somewhere explaining that and listing supported AD group types. this is specifically relevant to deployments where distribution type groups are used on AD side and then some customers have expectations that those would work with sssd mapping as well which they of course do not so this has to be explained or at least stated clearly somewhere in the docs.

Comment 2 Alexey Tikhonov 2022-07-18 11:08:52 UTC
Upstream PR: https://github.com/SSSD/sssd/pull/6263

Comment 3 Alexey Tikhonov 2022-09-16 13:45:05 UTC
Pushed PR: https://github.com/SSSD/sssd/pull/6263

* `master`
    * 794fd130e184e175f952b293833efe017bcdf13a - MAN: Add note about AD Group types

Comment 10 errata-xmlrpc 2023-05-09 08:19:50 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-2023:2514


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