> - krb5/winbind as an alternative to sssd: this was explicitly requested by paying customers with specific
> requirements related to cross-domain forest setups which could not be satisfied by sssd directly -- it's
> documented (albeit in a terse manner, only mentioning winbind) in the 0.10.0 changelog
I haven't looked at the specifics of winbind + adsys, or whether one could pick one or the other at runtime, but indeed, sssd is not able to integrate well with cross-domain AD forests. I wrote about winbind in such environments in the server guide[1].
> - krb5/winbind as an alternative to sssd: this was explicitly requested by paying customers with specific
> requirements related to cross-domain forest setups which could not be satisfied by sssd directly -- it's
> documented (albeit in a terse manner, only mentioning winbind) in the 0.10.0 changelog
I haven't looked at the specifics of winbind + adsys, or whether one could pick one or the other at runtime, but indeed, sssd is not able to integrate well with cross-domain AD forests. I wrote about winbind in such environments in the server guide[1].
1. https:/ /ubuntu. com/server/ docs/choosing- an-integration- method