Fusion basic authentication logins enforce username case-sensitivity occasionally

Summary:

Hello,

I've noticed occasionally between multiple client environments that use basic auth to log in (due to being early on in implementation) that sometimes the basic auth login enforces case-sensitivity as a requirement to log into the environment.

For example, if the user was John Smith and their username was JSmith in Security Console, the oracle login page would reject the user from logging in if they typed in "jsmith" with their correct password but would let the user log in if they typed in "JSmith" with their correct password.

However, this doesn't happen with all users, and it doesn't even consistently happen to the same users. I've personally experienced it enforcing case-sensitivity with my username one day and then not enforcing it ever again. We can't determine a pattern of why this is happening. From what I can tell in oracle documentation, username should be case-insensitive.