Must-share information (formatted with Markdown):
- which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
- SonarQube version 9.8.0.63668
- SonarQube is installed into a kubernetes cluster using version 7.0.0 of the sonarqube helm chart. We have an AWS RDS postgresql database connected to the SonarQube server.
- what are you trying to achieve
- I am trying to restore a quality profile using the
Restore
button in the UI on the/profiles
page
- I am trying to restore a quality profile using the
- what have you tried so far to achieve this
- I tried to export a quality profile from an older SonarQube server (8.9.9.56886) and then restore this profile into my new SonarQube server (9.8.0.63668) using the UI on the
/profiles
page. This resulted in a 403 error being logged to my browser’s javascript console. - I manually created a new quality profile in my new SonarQube server (9.8.0.63668) using the UI on the
/profiles
page. Then I clicked theBack up
button on this newly created profile to save it to file on my computer. Next I tried to restore this profile into my new SonarQube server (9.8.0.63668) using the UI on the/profiles
page. This resulted in a 403 error being logged to my browser’s javascript console. - I tried using curl and postman to POST a quality profile backup to the
/api/qualityprofiles/restore
endpoint and got a 403 response. I was able to successfully execute the/api/user_tokens/search
api using both curl and postman so I believe this confirms that my authentication was valid.
- I tried to export a quality profile from an older SonarQube server (8.9.9.56886) and then restore this profile into my new SonarQube server (9.8.0.63668) using the UI on the
I’ve checked the access logs, ce logs, web logs, main process logs, and search logs for errors. None of these logs contain any entries related to my failed attempts to restore my quality profile. This leads me to believe that the 403 error is occurring before the request gets deep into SonarQube. I’m confused as to why this would be occurring only for the /api/qualityprofiles/restore
endpoint and not for the many other endpoints that exist.
Any ideas for how to resolve this 403 error or how to get additional details to help in debugging?