Error SAML versión 8.9 Azure AD

SonarQube Server / Community Build
,
1

I have the following error when integrating enter ad with sonarqube

You’re not authorized to access this page. Please contact the administrator.

Reason: The response was received at https://localhost:9200/sonarqube/oauth2/callback/saml instead of SonarQube

In Azure everything is well configured with fqdn and I have configured Apache httpd and the reverse proxy

ProxyPass /sonarqube http://localhost:9200/sonarqube retry=0 timeout=50
ProxyPassReverse /sonarqube http://localhost:9200/sonarqube

And on the sonar I have it configured this way

sonar.core.serverBaseURL=SonarQube

sonar.auth.saml.enabled=true
sonar.auth.saml.entityId=SonarQube
sonar.auth.saml.loginUrl=https://login.microsoftonline.com/1bf7xxxxxxxxxxx/saml2
sonar.auth.saml.callbackUrl=SonarQube

HEEEEELP

2

Hey there.

Your ProxyPassReverse should use the public URL of your SonarQube instance (https://calice.loggro.com/), not localhost:9200, like documented here

  ProxyPass / http://private_sonar_host:sonar_port/
  ProxyPassReverse / http://www.public_sonar.com/

Hi,

Your version of SonarQube is also past EOL. You should upgrade to either the latest version or the current LTA (long-term active version) at your earliest convenience. Your upgrade path is:

8.9 → 9.9.7 → 10.7 (last step optional)

You may find these resources helpful:

3

Hello, I already made the change to the public URL but it didn’t work either, the same error still appears. Could it be due to the version of sonarqube? Although it seems strange to me since in this version it should also work correctly.

Conf apache

RequestHeader set Front-End-Https "On"
ServerAdmin xxxx@xxxx.com

SSLProtocol all -SSLv2 -SSLv3 -TLSv1 -TLSv1.1
SSLCipherSuite HIGH:!aNULL:!MD5
SSLHonorCipherOrder on

SSLEngine On

SSLProxyEngine Off

ProxyPreserveHost On
ProxyRequests Off
AllowEncodedSlashes On


SSLProxyVerify none
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
SSLProxyCheckPeerExpire off
SSLCACertificateFile /xxxxx/xxxxx/xxxx/xxxxx.crt
SSLCertificateFile /xxxx/xxxx/xxxx.crt
SSLCertificateKeyFile /xxxx/xxxxx/xxxxx.key
RequestHeader set X-Forwarded-Proto "https"
RequestHeader set X-Forwarded-For %{REMOTE_ADDR}s
RequestHeader set X-Forwarded-Host "calice.loggro.com"

ServerName calice.loggro.com
ServerAlias titan.loggro.com
ServerAlias 10.10.xx.xxx
ServerAlias calice
ServerAlias calice.loggro.com

Timeout 2400
ProxyTimeout 2400

RewriteEngine  on
RewriteCond %{HTTPS} on

ProxyPass  /sonarqube  http://localhost:9200/sonarqube retry=0 timeout=50
ProxyPassReverse /sonarqube  https://calice.loggro.com/sonarqube
4

You’ve also restarted Apache after making the changes? Is it the exact same error (same URLs?)

The response was received at https://localhost:9200/sonarqube/oauth2/callback/saml instead of https://calice.loggro.com/sonarqube/oauth2/callback/saml

5

Yes, I restarted Apache and Sonarqube too, I even did the test from other computers to rule out that it was the cache and nothing, that’s why my doubt, because I literally have everything configured as it should be, I don’t understand why it keeps getting that error