IBX-8140: Enabled authenticator manager-based security

[konradoboza]

🎫 Issue	IBX-8140

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:

• IBX-8140: Enabled authenticator manager-based security core#368
• IBX-8140: Enabled authenticator manager-based security rest#90
• IBX-8140: Enabled authenticator manager-based security admin-ui#1264

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):

Symfony Security has received major changes in 5.3. This article explains the new authenticator-based system (identified by the enable_authenticator_manager: true config option).

Refer to the [5.2 version of this documentation](https://symfony.com/doc/5.2/security.html) if you're still using the legacy security system.

[github-actions]

Thanks for contribution! 🎉

To test the changes please execute:

composer config extra.symfony.endpoint https://api.github.com/repos/ibexa/recipes-dev/contents/index.json?ref=flex/pull-118

before executing the recipes.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud