Home › Forums › OS X Server and Client Discussion › Active Directory › Problems with AD-OD UniqueIDs (UIDs)
- This topic has 1 reply, 1 voice, and was last updated 16 years, 4 months ago by
BDude004.
-
AuthorPosts
-
July 9, 2010 at 8:01 pm #379061
BDude004
ParticipantHi All,
As the subject implies, I’m having problem getting unix UIDs set in AD to propogate to the OD Workgroup Manager and client macs.
We’ve already been using the extended AD schema that allows us to set unix attributes, and it has been working phenomenally with our NIS based home directories for Windows users.
I’ve tested (on both the OSX server and client, both running 10.6) going to Directory Utility -> Services -> Active Directory -> Edit, then under Advanced Options -> Mappings, checked “Map UID to attribute:” and mapped it to “msSFU30UidNumber”.
When I do so on the server, the UIDs set in AD do not show up in Workgroup Manager, and logging into the client (bound to both OD and AD) with a domain user account does so with the OD generated UID. When I do so on the client, and try to log in with a domain user account it fails completely to authenticate.
Any help with this would be greatly appreciated!!!
Thanks,
BrianJuly 12, 2010 at 4:24 pm #379070BDude004
ParticipantHi MacTroll,
Thanks for your reply!
I looked into accessing AD via dscl, but I couldn’t wrap my head around it. Luckily, I found the “id” command, which was able to tell me that “something” is being pulled from AD when the mapping is in place. If you know the command syntax for dscl that I could use to access AD, please let me know. Anyways…
The user I am testing with is “test”, and the AD domain is “TEST”. In AD on the UNIX Attributes tab, the UID is set to 219448. With the server and client bound to AD, but no mapping in place, OD shows the UID as 1206407831.
With the mapping disabled on the client, I ran:
>id test
and got:
uid=1206407831(test) gid=1219304567(TEST\domain users)
If I enable the mapping on the client and run:
>id test
I get:
uid=4294967294(test) gid=1219304567(TEST\domain users)
So, it IS pulling something, maybe it’s the wrong field, or maybe it’s doing some translation on the field, but either way, that’s not gonna work.
Anything else you want me to try? Anybody else want to chime in?
Thanks,
Brian -
AuthorPosts
- You must be logged in to reply to this topic.