[Security] AccessDecisionManager refactoring #942
Closed
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.
Hi Fabien, hi Johannes,
I've tried to refactor the AccessDecisionManager class in the security component. I split the three access decision strategies (affirmative, consensus and unanimous) into three dedicated classes. Each strategy class implements the AccessStrategyInterface interface to enforce they have the same public API.
With this changeset, it's now easier to add new access decision strategies into the AccessDecisionManager object.
I couldn't manage to check if any regression came up because I have the following exception:
I'm not sure this exception is due to my changeset. Could you please test this pull request or help me to find and understand why I have this exception.
Thanks.
Hugo.