MI
2016-07-07 20:06:31 UTC
I'm confused about how to authenticate users of other Unix services with Samba4 AD.
After trying the classic upgrade on a test server, I can use smbclient. However,
"getent passwd" doesn't show the users, and I'm not sure what I have to do now.
On the live machines, I have openldap, pam-ldapd and nslcd running to authenticate
users of Samba 3 as well as ssh, postfix, dovecot, apache, mediawiki, postgresql, etc.
For Samba4 AD, I see mentions of pam-winbind, pam-sss, sssd, kerberos, and don't
quite understand which of these I actually need.
The point is to use the Samba4 AD-DC to authenticate users for the other Linux
services, including on other machines which may not be running Samba. Particularly
for SSH and mail.
All the Linux machines run Debian 8.
After trying the classic upgrade on a test server, I can use smbclient. However,
"getent passwd" doesn't show the users, and I'm not sure what I have to do now.
On the live machines, I have openldap, pam-ldapd and nslcd running to authenticate
users of Samba 3 as well as ssh, postfix, dovecot, apache, mediawiki, postgresql, etc.
For Samba4 AD, I see mentions of pam-winbind, pam-sss, sssd, kerberos, and don't
quite understand which of these I actually need.
The point is to use the Samba4 AD-DC to authenticate users for the other Linux
services, including on other machines which may not be running Samba. Particularly
for SSH and mail.
All the Linux machines run Debian 8.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba