- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
11-27-2024 09:46 AM
We've set up a JWT authenticator with Azure's JWKS-uri in its configuration (https://login.microsoftonline.com/{tenant_ID}/discovery/v2.0/keys). We have an enterprise application on Azure and we're generating a JWT token through client credentials. We've set it up such that a host xyz has the permissions to authenticate to this JWT authenticator.
However, when we try to reach the authenticate endpoint of Conjur for JWT authenticators, we're receiving the following error: conjur:user:xyz failed to authenticate with authenticator authn-jwt service conjur:webservice:conjur/authn-jwt/{Our_serviceID}: CONJ00035E Failed to decode token (3rdPartyError ='#<JWT::VerificationError: Signature verification failed>')
What could we be doing wrong?
11-27-2024 01:49 PM
Hi @Tanishq Pandey
I’m assuming you would have validated JWKS URI configured in Conjur.
Please validate that the JWT token generated by Azure. You can use https://jwt.io/ to validate and decode the JWT token.
As the error suggest, it’s a signature verification is failing, please check that Azure is signing the token with an algorithm supported by Conjur.
In addition, please validate Client ID, Secret, Scope and Permissions in Azure.
Also check,the xyz host in Conjur has the correct permissions to authenticate using the JWT.
Hope the above steps helps !
11-28-2024 05:25 PM
Hi @Tanishq Pandey
Could you please do check these points
Verify that you're using the correct token endpoint (v1.0 or v2.0).
Ensure the aud claim matches the App ID URI defined in Azure and Conjur.
Decode the token and check the kid field against the JWKS.
Confirm that Azure is signing the token with RS256.
Double-check permissions, scopes, and Conjur host configurations.
Synchronize system clocks between Azure and Conjur servers.
12-05-2024 07:52 AM
Hi @Tanishq Pandey ,
Since several community members answered your question, please let us know if these solutions addressed your query.
If so, it would be great if you could mark the most helpful response as 'Select as Best' to assist other community members with similar questions.
Thank you, Liad.
12-06-2024 03:22 PM
Thanks Malhar! We have validated these items, but to no avail. We're still receiving the same error. I've confirmed the kid value matches an entry on the JWKS URI page and has an associated public key. The token is in RS256 as expected by Conjur. However, Conjur doesn't seem to like it.
12-06-2024 03:26 PM
Thanks for the response, pkgajula! Could you elaborate on the 2nd point? When you say that the aud claim on the JWT token should match the App ID URI, what is the App ID URI in this scenario?
The aud claim is auto-generated by Azure as we're using the OAuth v2 token endpoint: https://login.microsoftonline.com/{tenant_id}/oauth2/v2.0/token
12-07-2024 12:07 PM
Hi @Tanishq Pandey
Have you manually validated the token against the public key retrieved from Azure's JWKS URI ? If not, you can leverage curl command and if that works then the issue might be with Conjur's parsing of the JWKS URI response.
curl https://login.microsoftonline.com/{tenant_ID}/discovery/v2.0/keys
Hope it helps !
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

