[Samba] samba4 and sssd and user mapping

[Michael Adam]

On 2014-01-27 at 08:55 -0800, Jeremy Allison wrote:
> On Mon, Jan 27, 2014 at 04:14:17PM +0100, Michael Adam wrote:
> > Question:
> >   What is winbindd that sssd is not?
> > 
> > Answer:
> >   Winbindd is the part of the samba software suite
> >   that is developed with samba, and has the responsibilty
> >   of doing authentication (e.g. against AD) and id-mapping
> >   for smbd. As such it is the component recommended by the
> >   samba developers to use (e.g.) in adomain-member-setup
> >   along with smbd.
> > 
> >   sssd, on the other hand, is not developed by the samba team.
> >   It is a 3rd party software that can take on similar roles
> >   as winbindd in some scenarios. As such it is of course not
> >   recommended by the samba developers, even though you might
> >   get it to work.
> 
> I think "not recommended" might be a bit strong. "Not
> tested with in our default builds.." would be a better
> statement :-).

No. I don't see why samba should recommend to use sssd
instead of winbindd.  Why would the samba team develop
a major piece of software but recommend to use a third
party piece of software instead? That would make no sense
at all to me. I am also not aware of any official samba document
recommending to use sssd instead of winbindd. So this is
my very definition of "samba does not to use sssd". :-)

(Of course those sssd developers who happen to be samba
developers as well might recommend sssd, but probably
not with their "samba hat" on..)

Cheers - Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 215 bytes
Desc: Digital signature
URL: <http://lists.samba.org/pipermail/samba/attachments/20140127/9dba9f71/attachment.pgp>