Active Directory Authentication

"Rabanal, Michele R." <[email protected]> Mon, 26 Aug 2013 07:35:29 -0400
Newsgroups gmane.comp.jakarta.turbine.user
Message-ID <4902631D269EAC459E87AA82EFF3A86F2FA852CC3B@GATUCEXCH13ASV.nscorp.ad.nscorp.com>
--_000_4902631D269EAC459E87AA82EFF3A86F2FA852CC3BGATUCEXCH13AS_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am trying to change my Turbine 2.3.3 application (running under Tomcat) t=
o use AD for authentication.  I understand that this is a 2-step process:
1) search by username (I use SAMAccount)
2) Bind or authenticate using the DN and password.

The search by SAMAccount  is successful (I can verify this in trace data), =
but the authentication by DN is not.  What appears to be happening is that =
Turbine is building the CN from the first and last names on the AD record. =
 In AD it appears that the CN varies, it could be first name/last name, fir=
st name/last name/middle initial, etc.  My question, why doesn't Turbine pu=
ll the CN off the AD record for the user object instead of building it from=
 first/last name?  Is there any way to make this work?

Thanks!
Michele

--_000_4902631D269EAC459E87AA82EFF3A86F2FA852CC3BGATUCEXCH13AS_--