Sonarqube SAML - AD SSO Login failed

Must-share information (formatted with Markdown):

  • SonarQube using v9.6.1

  • Aplication registered in Azure AD using SSO - SAML login

    • But when trying to login, got the below error, we have been getting this for long.
      we set the X_forwaded_Proto : https also, but still having issue, Kindly help asap

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

Reason: The response was received at http:/xxxx.com/oauth2/callback/saml instead of
https://x.com/oauth2/callback/saml

Hey there.

What do the logs say?

GET / HTTP/1.1" 200 - “https://xxxx.xx.com/sessions/unauthorized” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36” “AYWDfYfRJWNdcKCrAAA6”
10.10.63.90 - - [05/Jan/2023:20:52:43 +0100] "GET / " 200 - “-” “-” “dfghdghfgdhfghdgA5”

2023.01.05 21:00:41 DEBUG web[o.a.http.headers] http-outgoing-0 << HTTP/1.1 200 OK
2023.01.05 21:00:41 DEBUG web[o.a.http.headers] http-outgoing-0 << X-elastic-product: Elasticsearch
2023.01.05 21:00:41 DEBUG web[o.a.http.headers] http-outgoing-0 << content-type: application/json; charset=UTF-8
2023.01.05 21:00:41 DEBUG web[o.a.http.headers] http-outgoing-0 << content-length: 4990
2023.01.05 21:00:41 DEBUG web[o.a.h.i.n.c.InternalIODispatch] http-outgoing-0 [ACTIVE(4990)] Response received
2023.01.05 21:00:41 DEBUG web[o.a.h.i.n.c.MainClientExec] [exchange: 138] Response received HTTP/1.1 200 OK
2023.01.05 21:00:41 DEBUG web[o.a.h.i.n.c.InternalIODispatch] http-outgoing-0 [ACTIVE(4990)] Input ready
2023.01.05 21:00:41 DEBUG web[o.a.h.i.n.c.MainClientExec] [exchange: 138] Consume content
2023.01.05 21:00:41 DEBUG web[o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 138] Connection can be kept alive indefinitely
2023.01.05 21:00:41 DEBUG web[o.a.h.i.n.c.MainClientExec] [exchange: 138] Response processed
2023.01.05 21:00:41 DEBUG web[o.a.h.i.n.c.InternalHttpAsyncClient] [exchange: 138] releasing connection
2023.01.05 21:00:41 DEBUG web[o.a.h.i.n.c.ManagedNHttpClientConnectionImpl] http-outgoing-0 127.0.0.1:60418<->127.0.0.1:9001[ACTIVE][r:r]: Remove attribute http.nio.exchange-handler
2023.01.05 21:00:41 DEBUG web[o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Releasing connection: [id: http-outgoing-0][route: {}->http://127.0.0.1:9001][total kept alive: 0; route allocated: 1 of 10; total allocated: 1 of 30]
2023.01.05 21:00:41 DEBUG web[o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection [id: http-outgoing-0][route: {}->http://127.0.0.1:9001] can be kept alive indefinitely
2023.01.05 21:00:41 DEBUG web[o.a.h.i.n.c.ManagedNHttpClientConnectionImpl] http-outgoing-0 127.0.0.1:60418<->127.0.0.1:9001[ACTIVE][r:r]: Set timeout 0
2023.01.05 21:00:41 DEBUG web[o.a.h.i.n.c.PoolingNHttpClientConnectionManager] Connection released: [id: http-outgoing-0][route: {}->http://127.0.0.1:9001][total kept alive: 1; route allocated: 1 of 10; total allocated: 1 of 30]
2023.01.05 21:00:41 DEBUG web[o.a.h.i.n.c.InternalIODispatch] http-outgoing-0 [ACTIVE] [content length: 4990; pos: 4990; completed: true]
2023.01.05 21:00:43 DEBUG web[gfdfgfhgfhfghfgdhd][auth.event] login failure [cause|User must be authenticated][method|BASIC][provider|LOCAL|local][IP|10.10.60.30|][login|]