On 05/19/2010 08:24 AM, David O'Brien wrote:
Stephen Gallagher wrote:
> On May 19, 2010, at 4:51 AM, Jakub Hrozek<jhrozek(a)redhat.com> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> On 05/19/2010 01:04 AM, David O'Brien wrote:
>>> Recently it was recommended that I not include the LOCAL domain,
>>> groups, and related functionality in the end-user doc (limiting it to
>>> the man pages). This raises the following issue:
>>> There is a section in the draft doc at present, "Using the SSSD
>>> Management Tools", which includes info on working with users, groups,
>>> nested groups, examples, etc., all of which will disappear if we
>>> LOCAL domains from the topic list. Is this what we want? I know we're
>>> moving towards the "SSSD functions transparently in the b/g when
>>> approach, but I want to double-check before I remove this section
>>> 2 pages).
>> Right now the local domain plus the management tools are usable
>> primarily for testing, their only benefit is nested groups.
>> I vote for not documenting them in the deployment guide, but leaving
>> documentation in the SSSD sources (manpages, config file example..)
> I agree.
ok, sounds like a plan.
Can I ask for a real-world example or two to replace:
Working with Users
- Adding a new user
This should just disappear. When not using the local domain, users are
managed by the central user authority (e.g. LDAP), not by SSSD.
- Requesting user information
I don't have the doc in front of me (and don't know where to get it),
but requesting user information should be mostly unchanged, except for
mentioning valid LDAP users instead of local SSSD users.
Ditto for Groups
I guess the Nested Group section will just disappear...
I'd just like to have *something* there that illustrates SSSD in action,
something that's easy for a user to try and verify.
All the man pages, etc., I intended to leave as-is.
Thanks a lot.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.