Issue Task Under Review

#111237Add policy decision point and Core security voters

Benni Mack 10/25/26, 14:16 updated 11/18/26, 19:16

Description

Voters translate the subject of an authorization check into a resource and ask one decision service, instead of reading group data themselves.

- PolicyDecisionPointInterface: allow or deny for a principal, a scope and a resource (also batched); unknown scopes and resource types are denied.
- LegacyGroupDataPolicyDecisionPoint: answers from the be_users/be_groups permission lists exactly as BackendUserAuthentication::check(), checkLanguageAccess() and checkAuthMode() do (tables, exclude fields, field values, languages, page types, modules, widgets, MFA providers, custom options).
– Core voters: TableVoter, FieldVoter, LanguageVoter, ResourceVoter, and ModuleVoter in EXT:backend.

Functional “golden” tests compare every decision with the legacy checks. Page and file permissions follow separately. All new classes are internal.

Reviews 2

History 015