Unexpected behavior in user synchronization

[mariolopezserrano96]

Hello everyone,

We recently detected unexpected behavior when a user first accesses our organization on Sonar. We are using user sync from GitHub.

We have detected that it includes a random suffix (it looks like an identifier) ​​after username. This means that the IaC automations that we have implemented have begun to fail since the login is never known what it really is.

We can see an example in the following screenshot:

Until now, this sonarcloud login completely coincided with the GitHub login and we could have easy traceability.

Why has this change been made? Is it documented? Is it a definitive behavior?

Thank you very much, we look forward to feedback.

[ganncamp (G Ann Campbell)]

Hi,

Welcome to the community!

This should help:

Issues in Sync Between Github and Sonar

Hello Bruno, We have recently modified users login generation and introduced this 5 random letters. This is why you see all the new users login having this pattern. There is currently no way to avoid this behaviour. Regards, Nolwenn

[mariolopezserrano96]

For our part, we would like to emphasize that we have some automations that carry out this synchronization and they have been broken for this reason. It is a disruptive change, which I think you should warn about or, at least, document.

Is it possible that these types of new changes will occur again? Do we have any way of finding out to be warned?

[ganncamp (G Ann Campbell)]

Hi,

I don’t disagree with you, and have already raised this internally.

 
Ann