I'm not so sure I would call it a defect as much as I would call it a lack of feature.
Remedy is case sensitive with its logins. That is a 'feature'. A really nice feature would be to have a configuration option to turn that off and make it case insensitive....but I don't think you could really classify it as a bug :) On Thu, May 30, 2013 at 11:22 AM, Pierson, Shawn < [email protected]> wrote: > ** > > I know this isn’t directly in response to your question (which seems to be > resolved by some other folks) but I’ve encountered the exact same problem > on Remedy using Microsoft SQL Server so I think it’s an ARS defect and not > related to the underlying database’s preferences. My “workaround” was to > implement SSO, and the tool we use gives us the option to force lowercase. > **** > > ** ** > > Thanks,**** > > * * > > *Shawn Pierson * > > Remedy Developer | Energy Transfer**** > > ** ** > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Tommy Morris > *Sent:* Thursday, May 30, 2013 10:58 AM > *To:* [email protected] > *Subject:* Mixed Case Login Issues**** > > ** ** > > ** **** > > AR 7.6.4 sp1**** > > ** ** > > Just to be honest, I stole the summary of this issue from > *jshyman<https://communities.bmc.com/people/jshyman> > **but the answer to this was concerning Analytics and I could not find > another thread so here goes.*** > > * * > > If a user logs into Remedy using all lowercase then AREA LDAP checks with > LDAP, which is case-insensitive, and returns a positive result. Remedy then > checks the log in information with the Remedy Login ID in CTM:People and > finds a match and the user is logged in with all their expected rights..** > ** > > However, if a user logs into Remedy using mixed case or call CAPS then > AREA LDAP checks with LDAP, which is case-insensitive, and returns a > positive result. Remedy then checks the log in information with the Remedy > Login ID in CTM:People and does not find a match, due to Oracle being > case-sensitive, and the user is logged in as a guest.**** > > ** ** > > The easy solution would be to tell end-users to use all lower case when > they log into Remedy but instead our Problem Management team decided this > was a recurring issue with Remedy and opened a PBI on it. Does anyone have > a thought as to how I can capture the login ID and drop it to lower case on > both the UT and mid-tier? Or an any other useful suggestion will be > appreciated.**** > > ** ** > > _ARSlist: "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 hyperlink, please e-mail sender. > _ARSlist: "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"
