ldap passwd sync = Yes
ldap delete dn = yes
ldap suffix = dc=ZahidTractor,dc=com
ldap user suffix = dc=zahidtractor,dc=com
ldap group suffix = dc=zahidtractor,dc=com
ldap group suffix = dc=zahidtractor,dc=com
ldap machine suffix =
Also, the Machines and Users must be stored in the same OU.
Beneath a common OU, storing IN the same OU is not required.
It appears that
you have users stored in one OU and Computers stored in another OU. I
don't believe this is supported right now. (I believe this is because
PAM will
It appears that
you have users stored in one OU and Computers stored in another OU. I
don't believe this is supported right now. (I believe this is because
PAM will only search one OU for a UNIX user instead of multiples.)
NSS will only search one OU for account type objects; and both
Adam Tauno Williams rta:
Also, the Machines and Users must be stored in the same OU.
Beneath a common OU, storing IN the same OU is not required.
It appears that
you have users stored in one OU and Computers stored in another OU. I
don't believe this is supported right now. (I believe
Adam Tauno Williams wrote:
It appears that
you have users stored in one OU and Computers stored in another OU. I
don't believe this is supported right now. (I believe this is because
PAM will only search one OU for a UNIX user instead of multiples.)
NSS will only search one OU for
It appears that
you have users stored in one OU and Computers stored in another OU. I
don't believe this is supported right now. (I believe this is because
PAM will only search one OU for a UNIX user instead of multiples.)
NSS will only search one OU for account type objects; and both
It appears that
you have users stored in one OU and Computers stored in another OU. I
don't believe this is supported right now. (I believe this is because
PAM will only search one OU for a UNIX user instead of multiples.)
NSS will only search one OU for account type objects; and both
