Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 790107 - Document sss_tools better
Document sss_tools better
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd (Show other bugs)
6.3
Unspecified Unspecified
low Severity unspecified
: rc
: ---
Assigned To: Jakub Hrozek
Kaushik Banerjee
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-02-13 11:50 EST by Dmitri Pal
Modified: 2013-02-21 04:20 EST (History)
3 users (show)

See Also:
Fixed In Version: sssd-1.9.1-1.el6
Doc Type: Bug Fix
Doc Text:
Do not document.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-02-21 04:20:03 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0508 normal SHIPPED_LIVE Low: sssd security, bug fix and enhancement update 2013-02-20 16:30:10 EST

  None (edit)
Description Dmitri Pal 2012-02-13 11:50:23 EST 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/917

Manual pages for sss_* commands do not explain when/why those tools should be preferred instead of the standard utilities and on what data do the sss_* tools operate on.

For example, sss_groupadd(8) says:

DESCRIPTION
       sss_groupadd creates a new group. These groups are compatible with
       POSIX groups, with the additional feature that they can contain other
       groups as members.

It should be documented where this group is created (LDAP, SSSD's TDB, other), does it depend on sssd.conf, or is it perhaps useful only with IPA? When should groupadd(8) be used and when not instead of sss_groupadd or should most administrators use sss_* tools after deploying SSSD regardless of the server side?

Few sentences which would at least partly answer to these questions would be helpful for administrators deploying SSSD.
Comment 1 RHEL Product and Program Management 2012-07-10 01:49:52 EDT 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 2 RHEL Product and Program Management 2012-07-10 22:04:08 EDT 
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 4 Kaushik Banerjee 2013-01-20 11:05:34 EST 
Additional text verified in version 1.9.2-74

manpage of sss_useradd and sss_groupadd has:
The sss_user* and sss_group* tools use a local LDB storage to
       store users and groups.
Comment 5 errata-xmlrpc 2013-02-21 04:20:03 EST 
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.

http://rhn.redhat.com/errata/RHSA-2013-0508.html
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.