Self- managed AAD to SAML migration

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
    SonarQube 9.9 LTS
  • how is SonarQube deployed: zip, Docker, Helm
    Azure App Service
  • what are you trying to achieve
    Migration from AAD plugin to built in SAML authentication.
  • what have you tried so far to achieve this
    So far I have been testing few users and everything is going well. The only thing is that I am concerned about deleting the 3rd party plugin for AAD authentication and then restarting the app service. Is it just to delete the folder after users have been migrated to SAML and restart the app service or is there anything else to be worried about? Also, the best would be at first to disable this option in the screenshot that users won’t see the AAD login, only SAML. Thanks.

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

Hey there.

Toggling the Enabled option seems like a great way to be able to quickly revert if your users encounter an issue.

Having that plugin installed won’t harm anything. Make sure you only remove the sepcific .jar file for the plugin, not the extensions/plugins folder overall.

1 Like