On Mon, Feb 6, 2012 at 1:53 PM, Stephen Gallagher sgallagh@redhat.comwrote:

On Mon, 2012-02-06 at 13:46 +0100, Marco Pizzoli wrote:

...

Hi guys, please could you explain what the meaning of "local" as id_provider is?

I can figure out it is a SSSD-local user database. By specifing this I'm not considering the /etc/passwd file, am I right? If I would like to point to /etc/passwd do I have to specify "proxy" and eventually in /etc/nsswitch.conf "passwd files". Am I right again?

The 'local' provider is basically just using SSSD's cache without connecting it to an LDAP server (instead using the /usr/sbin/sss_* tools to populate it). It is unrelated to /etc/passwd.

Now it's more clear. I read the explanation on https://fedorahosted.org/sssd/wiki/HOWTO_Configure#TheLOCALprovider Anyway I still don't understand on what occasion one would use ssd_useradd to populate a second local user database in alternative to /etc/passwd. I'm missing the use-case...

If you wanted for some reason to have SSSD use /etc/passwd, it COULD be done with id_provider = proxy and proxy_lib_name = files, but I'm not sure what exactly you would be trying to accomplish by doing so.

Now I understand that I was missing the logic flow. I'm actually not trying to accomplish anything, not yet of course. I'm currently exploring sssd (and shortly FreeIPA) features, both for a university thesis and for a pilot project to one of my customers, so a complete understanding of the product is for me necessary at first.

Hoping to give a contribute, I would like to suggest a little modification to the man pages:

- sssd.conf --> the final example --> inclusion of a [domain/LOCAL] section - sssd.conf --> id_provider --> proxy: Support a legacy NSS provider *(e.g. nss_nis)* -------> exactly as reported here: https://fedorahosted.org/sssd/wiki/HOWTO_Configure#Domainconfigurationoption...

Thanks again Marco