Enhance user and tenant information on invalidToken errors #1454
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AsterITA
changed the title
AsterITA
requested review from
beetlecrunch,
galales,
Carminepo2 and
taglioni-r
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[Closes PIN-5789 & PIN-5791]
Improve error messages during token verification by including user and tenant details. Update the JWT verification process to return more informative responses and ensure proper error handling in the authorization flow.
jwt expired / invalid signature on BFF retrieve of session token
Before
After
jwt expired / invalid signature on BFF
Before
After
jwt expired / invalid signature on process
Before
After