Skip to content

Added tip regarding VoterInterface restrictions #2532

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from
Closed

Added tip regarding VoterInterface restrictions #2532

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ce4f418
Added tip regarding VoterInterface restrictions
peterrehm Apr 21, 2013
3257f43
Added API Links
peterrehm Apr 21, 2013
b6e11ac
Line Format
peterrehm Apr 21, 2013
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions cookbook/security/voters.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,6 +100,16 @@ and compare the IP address against a set of blacklisted IP addresses:
That's it! The voter is done. The next step is to inject the voter into
the security layer. This can be done easily through the service container.

.. tip::

Your implementation of the methods
:method:`Symfony\\Component\\Security\\Core\\Authorization\\Voter\\VoterInterface::supportsAttribute`
and :method:`Symfony\\Component\\Security\\Core\\Authorization\\Voter\\VoterInterface::supportsClass`
are not being called internally by the framework. Once you have registered your
voter the ``vote()`` method will always be called, not depending on your
restrictions. Therefore you need to call those methods in your implementation
of the ``vote()`` method.

Declaring the Voter as a Service
--------------------------------

Expand Down