This repository was archived by the owner on Jan 5, 2026. It is now read-only.
port: [#4432] Expired JWT token exception not being handled (#6572) - #4436
Merged
Conversation
Pull Request Test Coverage Report for Build 4204595324
💛 - Coveralls |
tracyboehrer
approved these changes
May 5, 2023
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Fixes #4432
Description
This PR ports the changes in the PR#6572 to handle expired tokens and return a most accurate error message.
Specific Changes
jwtTokenExtractorfor TokenExpiredErrors.jwtTokenExtractor.test.jsto cover the new code.cloudAdapter.test.jsto verify the exception is properly thrown.Testing
These images show the exception being displayed to the user in Emulator and the new unit tests passing.
