LDAP Case Sensitivity Config Breaks Login

[Colin]

Hey @Alexandra

No worries.

What I’m trying to get at is – if all your users should now have a lowercase username, you are going to update the existing users to also have a lowercase uesrname, either using PATCH /api/v2/users-management/users/{id} or (more simply, but deprecated) POST api/projects/update_login.

LDAP Connection Failed

Hey @vishwanihar and @shiva_sq When connecting SonarQube to a case-insensitive LDAP setup, you should set the sonar.authenticator.downcase=true configuration in your $SONARQUBE_HOME/conf/sonar.properties file and restart your SonarQube server. While not available through the UI, the POST api/users/update_login Web API (documentation linked in the footer of your instance) can be used to rename the logins of existing users so that duplicates aren’t made. You can imagine a script that programmat…

@Alexandra

This is for all existing users. For new users, do you mean testing adding a new user to SonarQube that isn’t authenticated through the LDAP server?

To clarify, I’m confirming whether a new user logging into SonarQube for the first time is successful. If the login works, then your login system is functioning correctly, and you just need to update the existing logins as I previously mentioned. This is just to ensure we’re addressing the real problem.