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 …

The problem for me was resolved by changing the ALB listener to HTTPS. This is because even though i was setting X-Forwarded-Proto to https at nginx layer, the AWS ALB strips that away if your using an http listener.

SAML error after upgrade to 8.4

SonarQube Server / Community Build

Rob_White (Rob White) July 8, 2020, 3:13am 5

I have a feeling the AWS ALB in between nginx and sonarqube is overwriting X-Forwarded-Proto. Just checking on that and will report back.

Sonar SAML Authentication issue with okta on 8.4 and above

Topic		Replies	Views
Error after upgrading to sonarqube-8.9.7 SonarQube Server / Community Build saml	3	715	April 5, 2022
Receive "not authorized" oauth2/callback/saml response error after upgrade to SonarQube 8.4 SonarQube Server / Community Build sonarqube , upgrade	6	7351	July 31, 2020
Sonar SAML Authentication issue with okta on 8.4 and above SonarQube Server / Community Build saml	3	1880	July 28, 2022
SAML Authentication through IIS not working after 8.4 upgrade SonarQube Server / Community Build authentication , saml	4	1738	November 16, 2020
SonarQube upgrade to 8.4.2 failing on SAML login SonarQube Server / Community Build saml	0	441	September 7, 2020

SAML error after upgrade to 8.4

Related topics