I've had similar issues. What I did was 1) change my LDAP ARDBC integration to do a lower() function on the AD attributes (such as cn) that stored the login name when I pulled it in to Remedy, and 2) customized the login.jsp page to automatically set the values in the Login Name field to be lower case I believe when it lost focus. However, since then we've been using an SSO tool so it hasn't been an issue for a few years.
Thanks, Shawn Pierson Remedy Developer | Energy Transfer -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Frank Caruso Sent: Thursday, September 05, 2013 12:16 PM To: arslist@ARSLIST.ORG Subject: LDAP Authentication Case Sensitivity ITSM 764 sp2; RHEL, Oracle, Weblogic Using AREALdap for authentication. From the web the user types in their network ID and we match against the sAMAccountName in LDAP. The ID is stored in AD in all upper case letters; at least that is what I thought. Come to find out the ID is stored in mixed case; sometimes all upper, sometimes all lower and sometimes mixed. So, unless the user knows how their ID is stored in LDAP the login to Remedy will fail. I was forcing all logins to upper case when the login button was clicked but am now realizing that will not work for all IDs. Is this something I can handle in AREALDAP? Thank you Frank Caruso _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" Private and confidential as detailed here: http://www.energytransfer.com/mail_disclaimer.aspx . If you cannot access the link, please e-mail sender. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
