Bug 1302595 - "domains" description in pam_sss(8) is misleading
Summary: "domains" description in pam_sss(8) is misleading
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: SSSD Maintainers
QA Contact: Steeve Goveas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-28 08:50 UTC by Aneta Šteflová Petrová
Modified: 2020-05-02 18:18 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-07 20:06:29 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 3987 0 None closed "domains" description in pam_sss(8) is misleading 2020-09-23 13:45:45 UTC

Description Aneta Šteflová Petrová 2016-01-28 08:50:35 UTC 
Description of problem:

From the "domains" option description in pam_sss(8):

---------------
NOTE: Must be used in conjunction with the “pam_trusted_users” and “pam_public_domains” options.
---------------

The sentence implies that users who want to use "domains" must also define "pam_trusted_users" and "pam_public_domains". This isn't true – there is no need to specify the two options when using "domains".


Can you please consider rephrasing the description to prevent this kind of confusion?
Comment 1 Lukas Slebodnik 2016-01-28 08:57:38 UTC 
Pavel wrote this feature.
Comment 3 Jakub Hrozek 2016-01-28 17:22:11 UTC 
Upstream ticket:
https://fedorahosted.org/sssd/ticket/2946
Comment 6 Jakub Hrozek 2017-03-28 08:09:15 UTC 
This bugzilla still needs work upstream. Because we are nearing the development freeze of RHEL-7.4 and the work is not finished yet, I'm reproposing the bug to RHEL-7.5.

Please push back if you disagree.
Comment 7 Jakub Hrozek 2017-08-07 20:06:29 UTC 
Thank you very much for filing this bug.

Since the issue is already tracked upstream and the fix will make its way into one of the future RHEL releases in a rebase, I'm going to close this bugzilla with the resolution of UPSTREAM.
Note You need to log in before you can comment on or make changes to this bug.