On Tue, Nov 15, 2022 at 7:17 AM 'Rowe, Walter P. (Fed)' via Ansible
Project <
ansible...@googlegroups.com> wrote:
>
> Look at SSSD for joining your Linux machine to AD. We use it and find it very reliable. It also enables use of smart card for SSH logins if your public keys are populated in your AD user objects if you work in an environment that requires smart card login (2-factor).
sssd has a lot of configuration issues and some very performance
issues. It works best with FreeIPA rather than Active Directory: it's
basically a Samba core with a FreeIPA body bolted on top of it, and it
does not scale to large AD environments. (Its insistence on
pre-caching the *entire* LDAP of the AD server and crashing if it
times out on that pre-load, is deadly for bulky, remote environments.)
For a very simple AD setup, it can work well. Be aware that it will
transform account names like "nkadel" in the "
example.com" AD domain
to "
nka...@domain.com", except when it doesn't, and the account
management can get pretty funky if you don't want to use the long form
all the time. Also be prepared to overload the 2048 maximum
line-length limit in /etc/group with such account names if you're not
cautious, and has to be dealt with that way unless you do
considerable extra work, in the sssd.conf and elsewhere in ways that
upgrades to sssd tend to erase. If you have to use it, be prepared to
spend time tuning the sssd itself with Ansible and managing
credentials with which to register the ansible target hosts in AD.
Nico Kadel-Garia
Email:
nka...@gmail.com
> To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/22DEC43D-F711-46C6-88C5-0EF6763EBAC8%40nist.gov.