LDAP userid case sensitive using WebSphere
I have a new Jazz server Beta 2a running WAS/DB2 with a database imported from a previous server running Tomcat/Derby. On both servers authentiction was done using bluegroups. The problem I am having now is that all userid's were created in lower case on the initial server. After importing into the new server, logins are failing due to the case of the userid's in the Jazz database not matching the bluepage entry exactly. Note that the issue is the userid as it is entered in the Jazz database, not how it is entered at the login prompt.
Is there any way to configure WAS to have it ignore case? I have tried the "ignore case for authentication" check box on the WAS standalone ldap configuration page, but this does not help. |
3 answers
Your best bet may be to start your tomcat instance again and change the
UserIds using the RTC Client. You can change the user ID from the the USER Editor. Simply right click the repository->Administer->Open Users mmartin wrote: I have a new Jazz server Beta 2a running WAS/DB2 with a database |
That doesn't really help us because our users are used to just entering their ID in lowercase. No other app that uses IBM Intranet Password (IIP) requires a mixed case ID, so forcing that for TeamConcert is just going to be confusing.
My understanding was that TC doesn't deal with authentication, instead delegating to the app server. If Websphere is set to ignore case why is the TC client not complying? The WebUI works fine with either case but the client won't follow suit. I consider this a bug. |
I've filed the following work item:
Case Insensitive Login (45640) (web) At login the application verifies a user with the userid that authenticate also exists in the Jazz database. -- Ritchie ********************************************** Ritchie Schacher Jazz Repository/Server Team "gcastro" <gabriel_castro@ca.ibm-dot-com.no-spam.invalid> wrote in message news:fpk726$397$1@localhost.localdomain... That doesn't really help us because our users are used to just |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.