[BUG] Username is case-sensitive when logging into MC Administrator

[elavy-harris]

Describe the bug
Login to Mirth Connect Administrator fails if the case of the username doesn't match.

To Reproduce

1. Try to log in to MCA with different case on the letters.

Expected behavior
Login succeeds.

Actual behavior
Login fails

Environment (please complete the following information):

• OS: Windows 10
• Connect Version 4.1.1

[elavy-harris]

Note: I am NOT using LDAP, so I don't think the fix in #5396 would fix my problem.

[pacmano1]

Is that a behavior change from the last release?

Curious really. Sounds like a new feature, lol.

Email addresses before the domain name by RFC are actually case sensitive by RFC 5321. Folks don't enforce it though.

[elavy-harris]

I don't know if it's a change from prior versions. I happened to create a mixed-case username on 4.1.1 and then couldn't get signed on because I didn't know it mattered.

The official and actual behavior of email addresses isn't relevant, is it?

[pacmano1]

Not relevant, just a random fact.

[joshmc82]

I noticed this as well using 4.1.1 "ADMIN" vs "admin". Also tested on 3.10.1 and experienced the same thing.

[ChristopherSchultz]

Hah. Multiply-confirmed on 4.1.1.

I'm using my own hand-rolled LDAP authentication plug-in and while the login worked (it's using LDAP), I was immediately presented with the "new user" dialog asking me to set up a password and give all my contact information to NextGen.

+1 to making usernames case-insensitive.