search

deepy / sonar-crowd

GNU Lesser General Public License v3.0
32 stars 37 forks source link

User renamed in crowd. Can not log in to sonarqube #26

Open gumbo2k opened 5 years ago

gumbo2k commented 5 years ago

Hi, we just renamed a bunch of users in crowd. (Not just changed the display name or Email, but changed the login name) The atlassian tools picked up on the rename without a hitch. Sonarqube apparently did not. (At least I can still see the old names in Administration > Security > Users, and the user can no longer login.) Question1: Is this a bug or a missing feature? Question2: What is the workaround? (stop sonarqube; change users.login in the database; start sonarqube ?)

Thanks

ogtool commented 5 years ago

The Atlassian products handle renames by storing all content "owned" by you under the first username you logged in to the system with. There's then a table (app_user in Jira) that maps from your original username to your current username. If your Unique User Attribute in Crowd is configured to pull from an objectGUID or similar in AD/LDAP, then changing a user in your source directory will keep the same user in Crowd, and on the next application sync to Crowd, a re-name process happens where the app_user (or equivalent) table is updated to your new username and the cwd_user table will have your username updated too (which links to the Crowd directoryID:userID record).

As there's no "sync" process for the SonarQube connector, the system is effectively just seeing a new user/username - it's unaware of any part of the rename event, so makes a new user.

CCM