Hello.
We recently updated from SonarQube 8.9.x to 9.9.4. We use LDAP for authentication. We tell new developers to log into SonarQube at least one time before the first commit, so that their SonarQube user exists and issues will be assigned to them. However, the automatic issue assignment does not work for them. After some investigation we realized that the underlying problem is what was discussed here (I’m starting this new post because the guidelines stated to not write replies to old discussions).
Our developers get the same username for Windows login and Subversion login. Prior to the SonarQube update, the Windows username was saved to the USERS.LOGIN column and (apparently) used to match with the SCM author. After the SonarQube update, USERS.LOGIN no longer stores the Windows username (that was used to log into SonarQube), instead it shows the fullname with a random number added. Because of this, new issues can no longer be matched to that SonarQube user.
The only solution we have so far is that some SonarQube admin has to regularly check for new users and manually add the SCM username to the SonarQube user. That’s not really a great experience.
I don’t understand why this change was done to the LDAP plugin.
Any suggestions how we can avoid to manually check for new users and manually add the SCM username?
Thanks,
Markus