Plug-in Not Working with SonarQube Version 9.9

[Ethereal0mega]

Plugin Version: 1.3.2 but also tested with 1.2.0
SonarQube Version: 9.9.0.65466
Error: 403

I'm setting up a new instance of 9.9 Enterprise Edition. This is not an upgrade, so the database and configs are fresh with no existing users. After configuring the SPN info as the built-in administrator and logging out, I'm unable to log in with AAD SSO. I see a successful authentication in AAD but getting a 403 returned by SonarQube/AAD Plugin. I'm also having issues setting up SonarQube's out-of-the-box SAML option so maybe this issue and that are related. Attaching sanitized console output from Firefox, but I am seeing this error which I'm not seeing with our older version 9.4 instance running the 1.2.0 plugin:

The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol.

Not sure if SonarQube has changed something with 9.9 that has broken the plugin's integration or not. Since my company has a cloud-only AAD instance, this plugin is the only way I have to sync our groups. If the files are too heavily redacted to be useful I can probably share more verbose outputs/packet captures via a more secure (less public) channel--will need to check with my security team.

aad_sso_plugin_1-3-2_console_export_request.txt
aad_sso_plugin_1-3-2_console_export_headers.txt

[srvrguy]

Unfortunately, client-side logs won't help much here. The 403 means that there's a problem on the server-side processing the authentication. You will want to look at the SonarQube server logs for errors.

By default, the log level is pretty basic, so you need to increase the verbosity of the logs. You can make this adjustment in the sonar.properties file by setting sonar.log.level to DEBUG from the default of INFO. Make sure to restart the SonarQube instance so it picks up the new settings. This plugin primarily outputs logs into the web.log file, so that will be the best place to check things. You might find some stuff in the main sonar.log too.