LDAP login username became case sensitive between 2.3.0p20 and 2.3.0p26

Troubleshooting
1

CMK version: 2.3.0p26
OS version: AlmaLinux release 9.5 (Teal Serval)

Error message: Incorrect username or password. Please try again.

Hello, our checkmk instance authenticates from Active Directory, in which our users have either all-capital case, or all-lowercase samaccountname. We use this as User-ID attribute in CMK. With release 2.3.0p20, all our users could log in with all-lowercased samaccountname. Once on 2.3.0p26, our users need to use the right casing when logging in. So users with all-uppercase samaccountname in AD can’t log in anymore to CMK web gui with all-lowercase username.

Is this change of behaviour intentional?

Thank you
Gabor

2

Hello, do you have any news on this one?
It would be good to have at least a confirmation that this is known.

3

Hi Gabor,

the username when logging in to the CMK GUI must exist in CMK exactly like being used.
e.g. if the username in CMK is “gabor”, then you have to login with this username, no matter how the username is written in AD. Same procedure for uppercase users or mixed case users.

I doubt that anything else worked in p20 - and if it did, it was an unintended bug :wink:

In the ldap connection setting in CMK you have a checkbox “lower-case user names” (or like that), which causes the synced users to get created lowercase in CMK, no matter of their writing in AD. Without this checkbox being activated the users are synced as-is: if user is named “Gabor” in AD you would not be able to login with “gabor” in CMK…

I hope this helps.

Best regards,
Marsellus W.

2 Likes
4

Hello Marsellus, many thanks for the feedback, that “Lower case User-IDs” checkbox is indeed there, we totally did not notice that. We’ll check a bit later if it restores the old behaviour.

Thanks again
Gabor