JWT Expired Error in Deployment Manager logs
Hi @nayam
We see below error in logs, even though the sample pipeline setup is working in non prod.
Error while processing JWT JSON web token is rejected during signature verification due to bad signature : Expired JWT
No changes were done to the OOTB rule DeploymentManagerClientJWTProfile.
Any suggestions to address this issue please?
Pegasystems Inc.
GB
@VenuJ637 Based on the error message, it seems like the JSON Web Token (JWT) used for authentication has expired. This could be due to the 'Expiration Time' setting in the JWT profile. Here are a few steps you can take to resolve this issue:
Check the 'Expiration Time' setting in the JWT profile. If it's set to a short duration, consider increasing it.
Ensure that the system time on your server is correct. If the system time is ahead of the actual time, it could cause tokens to expire prematurely.
If you're using an external system to generate the JWT, ensure that the token is not expired at the time of generation.
Check the 'DeploymentManagerClientJWTProfile' rule and ensure that it's configured correctly. The 'Send access token as Query string parameter' setting should be changed to 'Authorization header'.
Remember to always check the logs for any additional error messages that could help identify the issue.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Pega Deployment Manager 5.4 gives exception Access Token Not Found
Selective Insurance
US
@VenuJ637 I've seen a similar issue in our environments as well. As far as I can tell, it isn't impacting the functionality of the deployment manager but is causing quite a lot log entries.
Were you able to figure out the cause of the issue?