#2946 "domains" description in pam_sss(8) is misleading
Opened 3 years ago by jhrozek. Modified 2 years ago

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1302595

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?

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
patch: 0 => 1
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

owner: somebody => preichl
status: new => assigned

Since there is a patch, 1.14 alpha should be safe.

milestone: NEEDS_TRIAGE => SSSD 1.14 alpha

trivial man page patch, but we need to release 1.14 soon.

milestone: SSSD 1.14 alpha => SSSD 1.14 backlog

Since the 1.14 branch is transitioning into maintenance mode and new functionality is being developed in master which will become 1.15 eventually, I'm mass-moving tickets from the 1.14 backlog milestone to the "Future releases" milestone.

milestone: SSSD 1.14 backlog => SSSD Future releases (no date set yet)

Fields changed

milestone: SSSD Future releases (no date set yet) => SSSD 1.15.3

Metadata Update from @jhrozek:
- Issue assigned to preichl
- Issue set to the milestone: SSSD 1.15.3

2 years ago

Metadata Update from @jhrozek:
- Custom field design_review reset
- Custom field mark reset
- Custom field patch adjusted to on (was: 1)
- Custom field review reset
- Custom field sensitive reset
- Custom field testsupdated reset
- Issue close_status updated to: None
- Issue set to the milestone: SSSD 1.15.4 (was: SSSD 1.15.3)

2 years ago

Metadata Update from @jhrozek:
- Assignee reset
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue tagged with: cleanup-future

2 years ago

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue untagged with: cleanup-future
- Issue set to the milestone: SSSD Future releases (no date set yet) (was: SSSD 1.15.4)

2 years ago

Login to comment on this ticket.

Metadata