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

> *From:* ARSList [mailto:arslist-boun...@arslist.org] *On Behalf Of *LJ > LongWing > *Sent:* Sunday, March 04, 2018 9:51 PM > *To:* ARSList > *Subject:* Re: How does Non-Unicode AR Server handle AREA LDAP > authentication having unicode characters in CN ? > > > > Ra

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

, March 04, 2018 9:51 PM To: ARSList Subject: Re: How does Non-Unicode AR Server handle AREA LDAP authentication having unicode characters in CN ? Radhika, Ultimately the only thing that matters is the login name, so the CN in AD shouldn't matter, but apparently, everyone else is working

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

Radhika, 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 pluginunfortunately for you, the version that you are on

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

Hi, 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