After some inspection in our members list we identified that, after the user sync between github and sonarcloud, some of the new users added to sonarcloud now have the following user name pattern:
-<5 letters randon sequence>@github
Example:
somegithublogin-sCcY0@github
But what we expect after the user sync is:
somegithublogin@github
We don’t know exactly when this behavior started to happen.Is this an issue in the sync process? If not, there is way to avoid this behavior?
After some inspection in our members list we identified that, after the user sync between github and sonarcloud, some of the new users added to sonarcloud now have the following user name pattern:
-<5 letters randon sequence>@github
Example:
somegithublogin-sCcY0@github
But what we expect after the user sync is:
somegithublogin@github
We don’t know exactly when this behavior started to happen.Is this an issue in the sync process? If not, there is way to avoid this behavior?
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.
Do you provide any kind of API to translate this data? I mean I have an automation that add user to groups in sonar cloud according to internal permission rules and I need to have the relation between the github user and sonar user.
You can achieve this by using the api/users/search endpoint and search by email with the q parameter. The documentation is available here. You will be able to retrieve the user login and use it to add user to groups.