[Security] Merge UserAuthorizationCheckerInterface
into AuthorizationCheckerInterface
#59793
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 is a follow up of #48142 which was merged recently into 7.3
Having
UserAuthorizationCheckerInterface
separate fromAuthorizationCheckerInterface
doesn't make sense to me.It makes things confusing IMHO, as in "which interface should I implement?"
Of course,
AccessDecisionManagerInterface
is the central point, but still, I don't see how a separateUserAuthorizationCheckerInterface
is useful here.The PR also fixes a few issues found in tests and replaces the internal
UserAuthorizationCheckerToken
by an anonymous class.