Allow to set a custom response in case of authentication failure or invalid/not found token #157
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
…feature Allow users to create an AuthenticationFailureListener and set a custom Response to the Events::AUTHENTICATION_FAILURE Add Events::JWT_INVALID and allow users to listen on it and set a custom Response Fix services Replace JWTInvalidEvent|AuthenticationFailureEvent::setMessage() by setResponse(), Replace dispatcher constructor injection in favor of setter injection Handle case of no token found as JWTInvalid Update documentation for JWT_INVALID & AUTHENTICATION_FAILURE Events Fix mistake in doc remove duplicated code in JWTInvalidEvent by extending AuthenticationFailureEvent Rollback lite comit squashing
|
OK to merge. Thanks ! |
|
👍 |
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.
This make developers able to subscribe on the
AUTHENTICATION_FAILURE/INVALID_JWTevents.The first is dispatched when the provider cannot retrieve/authenticate credentials sent to the login route.
The second (new) is dispatched when the listener cannot
retrieve/authenticate a token on a secured route.Tests and documentation have been updated.