How to set case sensitivity for RTC logins with Websphere
- In JTS advanced page, we have case insensitive user ID matching set to false
- In Websphere, in LDAP settings,
if we select
U
One answer
Hi Kevin,
We had the setting to case sensitive in JTS for RTC. We didnt make any change to the setting after the initial setup.
Sorry, that was a typo. The two user IDs are USerA and usera
On selecting Ignore case for authorization in WAS it is still not case sensitive in RTC.
setting Use case insensitive user ID matching to true or false in JTS page has not effect.
Am i missing any specific change required in WAS or JTS ?
Comments
Ok, this is weird. I was able to login to a couple of different RTC we have ( one has case insensitive = true, another false ) using a mixed case version of my ID. My expectation would to have been rejected on the RTC with case insensitive = false.
Let me try with mixed case / bad password to see what WebSphere logs.
WebSphere logs the ID in the same case as I entered it.
Comments
Kevin Ramer
Mar 05 '15, 8:44 a.m.We migrated to WebSphere from tomcat w/o any issues of this sort. In our Global Security / Standalone LDAP realm, ignore case for authorization is checked. Non of the case sensitive settings was changed in any CLM application from their pre-websphere days.
Do you have the case sensitive the same in ALL applications ( not just the JTS ) ?
Not sure if this is a typo, but you mixed case of UserA -- assuming that's a real example ( USerA )