Sonar plugin for crowd just stopped working

[CptPlastic]

All of the sudden new users added to a group in crowd are not able to login with sonar. I also noticed the groups dont update anymore. Is anyone else having this issue?

[pekarp]

I have noticed same issue when we upgraded SonarQube from version 5.6.6 to 6.7.3.
Old Crowd users are able to login and groups are synced (but with some delay).
New Crowd users get authentication failed message.

[deepy]

@pekarp could you try it with 2.1 and see if the issue persists?

[pekarp]

@deepy we tested with version 2.1.
We added group right (sonar-users) to old Corwd user which was not found in Sonar users.
We were able to login with that user (new user on that group).
Group changes worked correctly to that user (new groups).

Then we created new Crowd user and added group sonar-users but we could not login in (authentication failure). We added sonar-users group to third user (old user in Crowd and not user in Sonar) and we could not login wither with that user.

Old users worked correclty.

We also tried and restarted Sonar to test if restart made any efect on this but situation is same.
I can't figur out why first old Crowd user but after adding sonar-users group worked only and after that situation was same as with version 2.0.

br.pekarp

[pekarp]

Hi @deepy,
we continued testing and founded that new user can't be added from Crowd if user has same email adderess that on someone current Sonar user.
In our first test email address was not used on Sonar users.
We changed email address for second and third user (those had same email address then on current Sonar user) and after email address change on Crowd for those two users we were could login to Crowd.

This 2.1 version seems to work with Sonar 6.7.3 with this email limitation.

Thank you.

br.Pekka

[deepy]

Thank you for testing it and reporting the results!

I have some good news in regards to the email issue, it seems like it has been fixed in sonarqube 7.2 :-)
If I'm reading it right it'll now create an error message detailing why it went wrong instead of giving a nondescript 500
https://jira.sonarsource.com/browse/SONAR-10532

[CptPlastic]

I am going to try to get this to work today I was holding off until I had time to work on this.

[mdeboer]

Same here using SonarQube 8.4.1 (build 35646). To get it working I deleted the existing SQ user and then signed in as that user with the Crowd credentials.