Hi,
Oh I dont know about that..
We have at least 4 AD domains controlled by me (central IT) and at least 3
ADs on the edge, as schools want to do their own thing...then there is at
least one Mac LDAP and one OpenLDAP...and that's the ones I know of.
So my job is to glue this all
When we originally designed SSSD, we looked at it as a solution for
dealing with LDAP and Kerberos identity and authentication for Linux and
UNIX clients. With our initial approach, we decided to include only
marginal support for Microsoft's Active Directory as a source of user
information (only
On Fri, 2011-12-02 at 15:59 +0100, Ondrej Valousek wrote:
Small update so I am not only throwing dirt on winbind:
Winbind has still its use if you can not use / do not have RFC2307
attributes in AD.
So simply, if you want to use RFC2307 attributes, sssd is here for
you. If not, go for
On 12/02/2011 04:06 PM, Stephen Gallagher wrote:
1) SSSD caching instead of nscd
Winbind has its own cache. We do not want to implement the yet another one
causing confusion, do we?
2) Support for multiple AD domains without trust
If needed, winbind itself should provide this
On Fri, 2011-12-02 at 10:06 -0500, Stephen Gallagher wrote:
On Fri, 2011-12-02 at 15:59 +0100, Ondrej Valousek wrote:
Small update so I am not only throwing dirt on winbind:
Winbind has still its use if you can not use / do not have RFC2307
attributes in AD.
So simply, if you want to