Closed burgessjp closed 1 year ago
@tjuerge Need Help.
This screenshot is pretty useless - the wrapped root BadJOSEException
is missing here.
You can manually validate the received ID token (value of JSON attribute id_token
) with https://oauth.tools/ as described here.
And which OpenID Connect identity provider are you using?
And check if your identity provider has signed the ID token with the same algorithm (HMAC, RSA or ECDSA) as you selected in the plugin configuration ID token signature algorithm
. If you're unsure then deactivate this feature.
Its seems your identity provider is signing with HMAC because the JWT of your ID token header eyJhbGciOiJIUzI1NiJ9
contains
{
"alg": "HS256"
}
This is in accordance with the log message Validating ID Token with HS256 and...
. Did you select HMAC
for the plugin configuration ID token signature algorithm
?
Its seems your identity provider is signing with HMAC because the JWT of your ID token header
eyJhbGciOiJIUzI1NiJ9
contains{ "alg": "HS256" }
This is in accordance with the log message
Validating ID Token with HS256 and...
. Did you selectHMAC
for the plugin configurationID token signature algorithm
?
Yes, The Configration is OK.
Ok, then only the full stacktrace (including the wrapped BadJOSEException
) can give us a hint. Please post the full stacktrace - or the wrapped root exception of the IllegalStateException
.
Btw. you can deactivate the plugin's ID token validation by resetting the ID token signature algorithm
. Is this (default) mode working for you?
The wrapped BadJOSEException
is thrown in Nimbus JOSE JWT's DefaultJWTProcessor
. Here you can find all the different error messages and the corresponding JWT object validations.
A detailed explanation of the inner workings of validating signed ID Tokens can be found here.
Which identity provider are you using?
@tjuerge
Thank you for your answer, this identity provider is our own company, I am looking for their assistance.
I will sync here when there is a result.
SonarQube Version: 9.0.1