[Date Prev] [Date Next] [Prev in Thread] [Next in Thread] [Date Index] [Thread Index]

Re: How does Non-Unicode AR Server handle AREA LDAP authentication having unicode characters in CN ?

Ultimately the only thing that matters is the login name, so the CN in AD shouldn't matter, but apparently, everyone else is working but the unicode ones aren't?...if that's the case you may be dealing with a defect in the AREA plugin....unfortunately for you, the version that you are on is no longer supported from a 'code fix' perspective....so I'm not sure you are going to be able to get this working without doing either data cleanup to remove all of the unicode characters, or potentially converting to unicode yourself....unfortunately, if the problem is in the area plugin in relation to unicode, converting to unicode for Remedy might not help you out...

On Thu, Feb 22, 2018 at 7:34 AM, Narayanan, Radhika <radhika.narayanan@cgi.com> wrote:



We’ve a non-unicode AR Server. Remedy Login Ids are in English only both on AD and AR Server.

Where the Active Directory had First or Last Name with Unicode character such as Vytautas Morkūnas, the corresponding name will be held in ITSM CTM:People form as Vytautas Morknas (ARS can’t store the Unicode character ū as it is currently installed as non-unicode). When this user logs in with correct AD password,  he/she gets Authentication failed.


In AREA Configuration, User Search Filter = sAMAccountName=$\USER$. In the AREA Plugin Log, we see that bind is successful for login id = abc1234 and AD returns the following : CN=Morkūnas\, Vytautas (abc1234),OU=Users,OU=xx,OU=yy,OU=zz,DC=xyz.

Even though bind is successful, AR still throws authentication failed error. Is it because AREA Plugin or ARS is unable to read the Unicode character in CN ?CN=Morkūnas\, Vytautas (abc1234). Please suggest how to get authenticated successfully.


Environment: ARS & ITSM 8.1.02

Non-Unicode Setup.



Radhika Narayanan        

ARSList mailing list