SAML Authentication Issue after Updating to v8.4

[ganncamp (G Ann Campbell)]

Hi,

Welcome to the community!

There were some changes to SAML auth in 8.4 that we didn’t think would be a big deal. These other threads may help you:

Receive "not authorized" oauth2/callback/saml response error after upgrade to SonarQube 8.4

Version: 8.4 Upgraded from: 8.2 Error observed: “You’re not authorized to access this page. Please contact the administrator. Reason: The response was received at http://sonarqube.domain.com/oauth2/callback/saml instead of https://sonarqube.domain.com/oauth2/callback/saml” Steps to reproduce: Login → {AD FS Login Button] → Error notice Potential workaround: Temporarily (cannot use for long term) - Create tokens for users or give them a direct SonarQube account So, we received this error…

Sonarqube - Developer 8.4.0.35506 - SAML error "[c.o.s.a.SamlResponse] <sonar.auth.saml.applicationId> is not a valid audience for this Response"

Hello team, Being a good internet citizen and creating a ticket in case this is of use for the developers at Sonarqube, or others who bump into the same error. In our case, we are using Microsoft Azure Active Directory App Registrations to enable login to Sonarqube via our corporate system. Affected version: Developer 8.4.0.35506 Errors observed: While logging into Sonarqube via SSO, the user is navigated to the appropriate login screen on Microsoft, authentication is provided, and the use…

SAML error after upgrade to 8.4

I recently upgrading to 8.4 and I am now unable to log on using SAML. The release notes state “This could reveal a non-standard configuration that needs to be updated.” The error message i get is: 2020.07.07 04:49:33 ERROR web[AXMnjbQn6g4l3XB1AAE6][c.o.s.a.SamlResponse] The response was received at http://sonar.mydomain.io:9000/oauth2/callback/saml instead of https://sonar.mydomain.io/oauth2/callback/saml I am not sure where Sonar is constructing this callback url. There is nothing in the G…

 
HTH,
Ann