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.

Description of problem:

man page of idmap_sss suggests to use * for backend sss. 


idmap config * : backend        = sss
idmap config * : range          = 200000-2147483647


The above recommendation in the man page is incorrect as sss backend is readonly  


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

sssd-ldap-2.0.0-23.el8.x86_64
python3-sssdconfig-2.0.0-23.el8.noarch
sssd-krb5-common-2.0.0-23.el8.x86_64
sssd-ad-2.0.0-23.el8.x86_64
sssd-client-2.0.0-23.el8.x86_64
sssd-dbus-2.0.0-23.el8.x86_64
sssd-kcm-2.0.0-23.el8.x86_64
sssd-libwbclient-2.0.0-23.el8.x86_64
sssd-common-pac-2.0.0-23.el8.x86_64
sssd-2.0.0-23.el8.x86_64
sssd-common-2.0.0-23.el8.x86_64
sssd-winbind-idmap-2.0.0-23.el8.x86_64
sssd-krb5-2.0.0-23.el8.x86_64
sssd-ipa-2.0.0-23.el8.x86_64
sssd-tools-2.0.0-23.el8.x86_64
sssd-nfs-idmap-2.0.0-23.el8.x86_64
sssd-proxy-2.0.0-23.el8.x86_64


How reproducible:


Steps to Reproduce:
1. Install sssd-winbind-idmap-2.0.0-23.el8.x86_64
2. run man idmap_sss
3.

Since the sss backend is readonly, the example should be as below:

idmap config <AD-DOMAIN-SHORTNAME> : backend        = sss

Upstream ticket:
https://pagure.io/SSSD/sssd/issue/3912

Niranjan, can you qa_ack the bug?

* master: ea7ada6c0629df45348f699e30acc44194550801

[root@host-8-254-0 ~]# rpm -q sssd
sssd-2.0.0-36.el8.x86_64


[root@host-8-254-0 ~]# man idmap_sss
IDMAP_SSS(8)                                                                            SSSD Manual pages                                                                            IDMAP_SSS(8)

NAME
       idmap_sss - SSSD's idmap_sss Backend for Winbind

DESCRIPTION
       The idmap_sss module provides a way to call SSSD to map UIDs/GIDs and SIDs. No database is required in this case as the mapping is done by SSSD.

IDMAP OPTIONS
       range = low - high
           Defines the available matching UID and GID range for which the backend is authoritative.

EXAMPLES
       This example shows how to configure idmap_sss as the default mapping module.

           [global]
           security = ads
           workgroup = <AD-DOMAIN-SHORTNAME>

           idmap config <AD-DOMAIN-SHORTNAME> : backend        = sss
           idmap config <AD-DOMAIN-SHORTNAME> : range          = 200000-2147483647