-----BEGIN PGP SIGNED MESSAGE-----
On 03/05/2014 06:31 PM, Matt Mencel wrote:
Problem was the loginShell attribute in LDAP was "/bin/csh"
that shell did not exist on my client.
- SSH failed to bind (LDAP error 49) - Local console would bind but
not login. - 'su - account' would bind, not login, and presented an
error indicating /bin/csh was not present.
Switched my loginShell attribute to /bin/bash and all worked as it
Alternately, see the SSSD documentation for the fallback_shell option.
It allows you to set a shell to use if the one in LDAP doesn't exist
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----