My Oracle Support Banner

Login IDs Should Not Be Case Sensitive, If a User Enters a Username Without Being case-sensitive At The Time Of Login, System Should Not Throw An Error Invalid UserName / Password. (Doc ID 2816124.1)

Last updated on OCTOBER 22, 2021

Applies to:

Oracle Banking Digital Experience - Version to [Release 20]
Information in this document applies to any platform.


On : version, Production Support

The issue can be reproduced at will with the following steps:
1. While Creating a User, the System throw a duplicate error while creating users in different CASE (System does not allow users to be created in different Case)
2. While Login into an application, the system Authenticates on the USER ID case also.
for example:- User is created with the name "john"
At the time of login:
User_id -> john -> it will work, no error.
User_id -> JOHN -> it will not work.


The system should either remove case sensitive checks during login ID creation or
while authentication it should not check the LOGIN ID Case.

The issue can be reproduced at will with the following steps:
1. Create any user with lower case eg. john from the admin user.
2. log in to an application with user_id as "JOHN"
3. System throws an error -> Invalid UserName /Password.

The issue has the following business impact:
Due to this issue, users are not able login into the application, if a user enters a username without being case-sensitive.


 No changes done to hardware/product or environment cause this issue.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.