Hi Paul,
If the JWT you’re trying to validate lacks the x5t
parameter, it might be due to changes in the token generation process or the certificate used. The absence of x5t
could lead to signature validation failures, as you’ve observed.
The absence of x5t
might indicate a change in the token generation process. Ensure that the certificate used for signing is correctly configured.
You may need validate the new JWT from the Exchange Microservice - retrieving the public key, checking the thumbprint and verifying the signature.