Invalid token exceptionn #38
Merged
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.
This pull request improves error handling and robustness in the authentication and token validation process. The main changes include more granular exception handling for JWT token errors and centralized exception resolution in the security filter.
Authentication and Exception Handling Improvements:
SecurityFilternow uses aHandlerExceptionResolverto handle exceptions during authentication, ensuring that errors are processed in a centralized and consistent way.UsernameNotFoundExceptionwith a clear message when a user is not found by ID, improving error clarity.Token Validation Enhancements:
TokenServicenow logs errors and distinguishes between different JWT-related exceptions, throwing specific messages for expired, malformed, unsupported, invalid signature, or empty tokens. This provides more informative feedback for each token validation failure scenario. [1] [2] [3]