IBX-8140: Enabled authenticator manager-based security

[konradoboza]

🎫 Issue	IBX-8140

The idea is to engage Symfony mechanisms to check permissions. Otherwise, we end-up in the BO-user-protected templates which cannot perform any operations on null user which is anonymous in the new Symfony security approach.

Removal of the Ibexa\Contracts\AdminUi\Controller\Controller definition is done due to duplication, ref: https://github.com/ibexa/admin-ui/blob/main/src/bundle/Resources/config/services.yaml#L49.

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 recipes-dev#118

Description:

For QA:

Documentation:

[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

[Steveb-p]

I don't really immediately see how setting this as parent definition helps. Especially since this definition lies in a completely different file it seems.

Have you considered using _instanceof to prevent forgetting that this parent has to be added to each controller of this type?

[konradoboza]

Actually I haven't. Til this point we have followed adding parent controller to all of the admin-ui-related ones. I only aimed to fix the ones that slipped between cracks and which I tracked down while working on enabling new security layer.

I would say that if this approach needs revisiting we should work on that separately as it's a bit out of scope of security-related changes.

Unless you had something else in mind.