Re: How does Non-Unicode AR Server handle AREA LDAP authentication having unicode characters in CN ?
If you are able to get onto the 9.1 platform, you can open a defect with BMC regarding it and they will fix I would recommend checking it against 9.1.04 if possible because that's the latest currently available... On Mon, Mar 5, 2018 at 12:45 AM, Narayanan, Radhika < radhika.naraya...@cgi.com> wrote: > Hi, > > > > Thank you. I’m trying to reproduce this error on non-unicode ARS 9.1.03. > If it gives the same error there due to AREA Plugin defect, perhaps it will > be fixed on 9.1.03 ? > > > > *Thanks,* > > *Radhika Narayanan* > > > > *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 ? > > > > 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 is no > longer supported from a 'code fix' perspectiveso 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 > yourselfunfortunately, 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.naraya...@cgi.com> wrote: > > 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 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. > > > > *Thanks,* > > *Radhika Narayanan* > > > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist > <https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.rrr.se_cgi_listinfo_arslist=DwMFaQ=H50I6Bh8SW87d_bXfZP_8g=blQKSsGpUV3vEddB0ufOi2izy5lUOikNQGO3le4xQkw=VqG7Dzwd_ygboR3qGti7ARgXbQvyjENLC0PLBiR7ugI=HEir2-e0ByIuGYxRvcOWntYIIKtQHzdff1DVDUjBlVY=> > > > > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist > > -- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
RE: How does Non-Unicode AR Server handle AREA LDAP authentication having unicode characters in CN ?
Hi, Thank you. I’m trying to reproduce this error on non-unicode ARS 9.1.03. If it gives the same error there due to AREA Plugin defect, perhaps it will be fixed on 9.1.03 ? Thanks, Radhika Narayanan 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 ? 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 is no longer supported from a 'code fix' perspectiveso 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 yourselfunfortunately, 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.naraya...@cgi.com<mailto:radhika.naraya...@cgi.com>> wrote: 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 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. Thanks, Radhika Narayanan -- ARSList mailing list ARSList@arslist.org<mailto:ARSList@arslist.org> https://mailman.rrr.se/cgi/listinfo/arslist<https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.rrr.se_cgi_listinfo_arslist=DwMFaQ=H50I6Bh8SW87d_bXfZP_8g=blQKSsGpUV3vEddB0ufOi2izy5lUOikNQGO3le4xQkw=VqG7Dzwd_ygboR3qGti7ARgXbQvyjENLC0PLBiR7ugI=HEir2-e0ByIuGYxRvcOWntYIIKtQHzdff1DVDUjBlVY=> -- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
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 is no longer supported from a 'code fix' perspectiveso 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 yourselfunfortunately, 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.naraya...@cgi.com> wrote: > 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 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. > > > > *Thanks,* > > *Radhika Narayanan* > > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist > > -- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
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 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. Thanks, Radhika Narayanan -- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
