JWT has an invalid signature

The access token stored in the APIM cache which is mapped to session key has an invalid signature. Though the JWT itself is valid, however, does not have any valid signature and it is causing the issue at various downstream levels where JWT validation failing.



Further using the token in exchange flows through MSAL or Azure.Identity also deems the signature invalid -


Is it because we are assigned APIMGatewayURL as an issuer while the issuer in the token is different (https://sts.windows.net/tenantId) ?
@prjhawar @jukasper - Kindly help with this issue.

No source file, test, or entry point is named. Start by comparing the APIM issuer configuration with the issuer and signature claims in the cached token, then trace validation through MSAL or Azure.Identity; done means the issuer/signature mismatch is identified and the affected configuration or flow has a confirmed fix.

Vom Indexierungsmodell aus dem Issue-Text verfasst.