IBX-8356: Reworked JWT firewall to be in-tact with the new Symfony auth #122
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.
Related PRs:
Ibexa\Core\MVC\Symfony\Security\Authentication\AuthenticatorInterface
to be replaced with Symfony-based authentication core#375 (will be merged at the end, not blocking this part)Ibexa\Core\MVC\Symfony\Security\Authentication\AuthenticatorInterface
usages to comply with Symfony-based authentication rest#101Description:
This PR is about making JWT authentication compliant with the Symfony security changes (and bringing it back in the first place 😅). The main source of truth that was used is https://symfony.com/bundles/LexikJWTAuthenticationBundle/current/index.html#symfony-5-3-and-higher.
Additionally, I used
to make the request payload BC safe (username and password are taken from specific keys from the payload so no changes are needed on consumer's end).
For QA:
Documentation:
If we mention security configuration changes anywhere, we need to include changes from this PR as well.