C
Crystal
Can anyone tell me why MS uses the Full name (John Smith)
as the cn when building the distinguished name as opposed
to the samaccount name?
Our domain users are set up in an Active Directory
evironment. The application im setting up currently
authenticates to the CN attribute. the problem is the AD
installation stores the username (ie. jdoe) in an
attribute called sAMAccountName and the Full Name in CN
(ie. John Doe).
Is there a way to build a new user and place the
samaccount name in the cn attribute instead of the full
name? I don't want to have to rename 10k+ accounts! Can
I change the default way that MS builds the dist. name
during user creation?
Thanks -
Crystal
as the cn when building the distinguished name as opposed
to the samaccount name?
Our domain users are set up in an Active Directory
evironment. The application im setting up currently
authenticates to the CN attribute. the problem is the AD
installation stores the username (ie. jdoe) in an
attribute called sAMAccountName and the Full Name in CN
(ie. John Doe).
Is there a way to build a new user and place the
samaccount name in the cn attribute instead of the full
name? I don't want to have to rename 10k+ accounts! Can
I change the default way that MS builds the dist. name
during user creation?
Thanks -
Crystal