No permission to edit a newly created portfolio

SonarQube Server / Community Build
1

Hi,

we have a productive instance, SonarQube Enterprise on-premise 10.5 with LDAP authentication, and a test instance, with SonarQube Enterprise on-premise 10.6 with SAML-Azure-AD authentication.

Now we observed a strange behaviour on our SonarQube test instance, when editing a portfolio. I am able to create a portfolio, but when I click on “Edit Definition” to add content to it, I am again asked to login, which leads me back to the start page.

This behaviour only happens on our test instance, on our productive instance the same user is able to create and edit portfolios without any issues.

Is this a problem with our SAML authentication oder is it a bug in SonarQube 10.6?

Thanks!

Regards,
Carsten

2

Hey there.

It sounds like the permission template being applied to the portfolios doesn’t include Creators. You can modify this.

3

Hi @Colin ,

thanks for your answer! Yes, the Creators have no permissions assigned in the permission template and if I add the “Administer” permission, it works as expected.
But on our productive instance with SonarQube 10.5, the Creators as well do not have this permission. If it is necessary now, this would be a behaviour change.

Regards,
Carsten

4

Is it possible that on your production instance, said users belong to groups you are also granting permission to via the permission template? I don’t expect any recent (or frankly, non-recent) changes to how this works.

5

Hi @Colin ,

that was the decisive hint! One of the (new SAML) groups did not have the correct permissions. Now it works, thanks a lot!

Regards,
Carsten

1 Like
6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.