IBX-8140: Enabled authenticator manager-based security #118
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 PR is about switching to the new authorization mechanism that was introduced as part of Symfony 5.4 release. The main trigger allowing us to rely on the new mechanism from now on is setting
enable_authenticator_manager: true
. All the related PRs adapt the existing codebase and base functionalities like login/logout/redirect to work with the new setup.The most important part is not having a token for anonymous users which forces us to revisit the approach to such users. In practice we need to deal with
null
value instead of token for anonymous users.Related PRs:
Description:
For QA:
Documentation:
We should mention that those changes are necessary due to switching to the new auth system coming from Symfony (ref: https://symfony.com/doc/5.x/security.html):