Frank, I have personally found that while Remedy is user id case sensitive, active directory isn't....so really, the only thing that matters is that you match the case of the user id in your remedy user table...the password is of course case sensitive...but the user name should not be, not in AD at least.
On Thu, Sep 5, 2013 at 11:16 AM, Frank Caruso <caruso.fr...@gmail.com>wrote: > 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" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
