Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We have around 70% linux users, all of which are configured to authenticate against Active Directory through LDAP. In order for this to work, we used the "Windows Services for Unix" under Windows Server 2003, and it all works fine.

We are now at a point where the server running this contraption is getting a bit tired and will be replaced with a newer machine, running Windows Server 2008 (where the relevant services such as user name mapping and password changes, etc., are integrated with the OS).

And here's the rub: If a new user is configured through the Win2k3 server, then it all works fine. If the same thing is done through the Win2k8 server, then :

  1. The ADS plugin on the 2k3 server does not recognize it and behaves as if the UNIX attributes were never set.
  2. The user cannot authenticate against ADS using LDAP.

Has anybody encountered this problem? If so, how did you overcome this?

If you need any additional information to provide further help, just ask and I shall provide it.

share|improve this question

2 Answers 2

up vote 3 down vote accepted

The LDAP name mapping has changed between Win2K3 and 2K8. The new mapping (to apply in /etc/ldap.conf) is:

nss_map_attribute uid sAMAccountName
nss_map_attribute uidNumber uidNumber
nss_map_attribute gidNumber gidNumber
nss_map_attribute cn sAMAccountName
nss_map_attribute uniqueMember member
nss_map_attribute userPassword msSFUPassword
nss_map_attribute homeDirectory unixHomeDirectory
nss_map_attribute loginShell loginShell
nss_map_attribute gecos cn
nss_map_objectclass posixGroup Group
nss_map_attribute shadowLastChange pwdLastSet

Please let me know if that helps. You may have to migrate the old users as well-- I'd use ldapsearch and compare new and old users (but I think they will just have both attributes, if I recall)

share|improve this answer
    
Thanks for the advice, I will check it out. Migration isn't a big problem, because we have all of this packaged into a local debian package, which we can just upgrade and let all users know that they should simply update their machines. –  wolfgangsz Jan 13 '11 at 17:27
    
Well, it's actually slightly different (at least in our environment : uid, uidNumber, gidNumber and cn don't need mapping at all (names are identical), uniqueMember -> to msSFUPosixMember, userPassword -> msSFU30Password, and a few other changes. Put I accept the answer for pointing me in the right direction. –  wolfgangsz Jan 28 '11 at 15:31

I've decided to post another answer here, since this is usually the place where people find the information they are looking for.

Whilst the above is all still very valid and true, I have now found a much, much easier way to connect my clients via AD. Debian squeeze (the latest stable release) contains sssd (a package that originates in the redhat/fedora environment), which makes all of this a complete breeze. Upon installation it finds and suggests domain controllers, and I only needed to change very few things in the config file to make it work for me. It works perfectly fine with Windows Server 2008, and it can also cache passwords (important for laptop users).

share|improve this answer
    
wolfgangsz, can i contact you to get more info on sssd? how? –  pcharlesleddy Aug 10 '12 at 15:04

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.