[SSSD] [patch] Make example sssd.conf a working example with a local domain

Stephen Gallagher stephen at gallagherhome.com
Fri May 28 11:45:08 UTC 2010


Truthfully, it would be best to just have it ask questions, similar to
how nss_ldap works today (IIRC).

We have the SSSDConfig API for exactly that reason. It is a python API
that will construct an sssd.conf for you.


But if your preference is to have a local domain, then you shouldn't
need anything but:

[sssd]
domains = LOCAL

[domain/LOCAL]
id_provider = local

All of the defaults beyond that should be sensible (and the auth,
access and chpass providers will be auto-set appropriately to local,
permit and local, respectively).

On May 28, 2010, at 2:27 AM, Petter Reinholdtsen <pere at hungry.com>
wrote:

>
> [Simo Sorce]
>> Hi Petter,
>> the reason we do not configure LOCAL by default is that at the
>> moment it has limited value.
>
> Given that we want a working default configuration for sssd in Debian,
> which make sure the daemon start when the package is installed without
> any questions, what should such default configuration look like?
>
> At the moment it is a simple LOCAL, as neither Kerberos nor LDAP work
> without any configuration.
>
> Is it possible to make a no-op configuration, while still getting sssd
> to start?
>
> (And stating that you believe this goal is not wanted after all do not
> really help, so please keep such replies to a minimum. :)
>
> Happy hacking,
> --
> Petter Reinholdtsen
>
> _______________________________________________
> sssd-devel mailing list
> sssd-devel at lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/sssd-devel



More information about the sssd-devel mailing list