Case Insensitive Logins with RQM
In order that case insensitive logins can be used with RQM, I have switched the option 'Use case insensitive user ID matching' to 'true' within the 'Advanced Properties' section of the Jazz Team Server.
The behaviour now being seen is that when I log in using mixed case, I seem to be logged in as the user 'ADMIN' rather than myself. There is not a problem if I use lower case logins.
Can anyone explain this behaviour to me?
I have RQM 3.0.1 installed and using OpenLDAP.
The behaviour now being seen is that when I log in using mixed case, I seem to be logged in as the user 'ADMIN' rather than myself. There is not a problem if I use lower case logins.
Can anyone explain this behaviour to me?
I have RQM 3.0.1 installed and using OpenLDAP.
4 answers
I encountered this issue with RTC 4.0.0.1 but couldnt figure out the reason behind this behaviour.
If the user belongs to JazzAdmin group, case insensitive username allow user to login as ADMIN user(which I disabled during JTS setup). If the user is a member of JazzUser group he/she cant login to jazzteamserver.
Why is this happening?
If the user belongs to JazzAdmin group, case insensitive username allow user to login as ADMIN user(which I disabled during JTS setup). If the user is a member of JazzUser group he/she cant login to jazzteamserver.
Why is this happening?
Are you able to login to jts/admin page with mixed case?
If so, make sure that you update 'Use case insensitive user ID matching' to 'true' in the 'Advanced Properties' section on RQM admin page too.
Comments
Hello,
if you are able to login with your user name but you see ADMIN as logged in user in the upper right corner that means that the application server found the user in LDAP but the user is not found in the application, in your case in QM.
This works only for jazzadmins that way. A none jazzadmin user would not be able to login but a jazzadmin has to be able to login even he is not added to the application yet.
There maybe different reasons why the user is not found in the application:
- user is not imported from LDAP
- the application is not set to case insensitive
- LDAP is not configured correctly for this application
Hope this makes sense.
Elisabeth