search

jborgers / sonar-pmd

☕️ PMD Plugin for SonarQube
https://redirect.sonarsource.com/plugins/pmd.html
GNU Lesser General Public License v3.0
263 stars 156 forks source link

Crowd username changes - impact on sonar-pmd plugin #402

Open mos9mu opened 1 year ago

mos9mu commented 1 year ago

Dear Sir or Madam,

I am reaching out to you on behalf of the SonarQube Team. We are using this plugin in our SonarQube EE v9.9. We authenticate to SonarQube via Atlassian Crowd. The team is about to perform a large-scale change of usernames in Crowd across the entire user base, i.e, all usernames in Crowd will be moved to different IDM system. For example, a username like "john.doe" in Crowd will be moved to "DOJ1MU"  which is based on the IDM system we are moving to. Naturally, the team would like to understand the impact this has on your plugin, the data it stores and it uses.

In more detail, we would like to understand how your app references the users in the database. Do you go with the username, which can be updated for a specific user, or do you reference the internal user key/ID. For example, in Jira, this is the app_user.user_key column. Of course, it would be of major interest whether we can expect sound handling of the change of usernames.

For reference's sake, here are two impact examples from Jira and Confluence:-

•    JRASERVER-70685: Renaming the user should also update filters and mentions •    CONFSERVER-82873: Updating the username breaks user macros

At the time of writing, this plugin version in use is v3.4.0. A quick feedback would be most highly appreciated.

Looking forward to your feedback!

KR

mos9mu commented 1 year ago

Hi team, Any feedback here?

mos9mu commented 1 year ago

Hi team, Any feedback here?

jborgers commented 6 months ago

Hi, sorry for the late reply.

As far as I can tell, we don't have the notion of a user in the sonar-pmd plugin. We add extra Java rules and handle them.