Question

Unisys
NZ
Last activity: 8 Jul 2019 5:57 EDT
JSON Web Token is not validated correctly despite being correct
Hi Everyone,
We are generating a JSON Web Token using the Generation Token Profile and sending it to the front end.
For every subsequent service calls from the front end we are receiving the same generated token for validation.
The issue is sometime pega is able to process the token using the Processing Token profile and sometimes it fails.
This is issue is happening irregularly and after debugging and tracing we notice the claims under the processing token are not getting mapped on to the clipboard and the logs show something like following:
Hi Everyone,
We are generating a JSON Web Token using the Generation Token Profile and sending it to the front end.
For every subsequent service calls from the front end we are receiving the same generated token for validation.
The issue is sometime pega is able to process the token using the Processing Token profile and sometimes it fails.
This is issue is happening irregularly and after debugging and tracing we notice the claims under the processing token are not getting mapped on to the clipboard and the logs show something like following: