8000 [Security] add & update doc entries on AbstractVoter implementation by inoryy · Pull Request #4257 · symfony/symfony-docs · GitHub
[go: up one dir, main page]

Skip to content

[Security] add & update doc entries on AbstractVoter implementation #4257

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.

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 5 commits into from
Closed
Show file tree
Hide file tree
Changes from 1 commit
Commits
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
Next Next commit
add & update doc entries on AbstractVoter implementation
  • Loading branch information
inoryy committed Sep 23, 2014
commit 28c6536cfae7f995bd65d08725dabafe03b9dd76
31 changes: 31 additions & 0 deletions cookbook/security/abstract_voter.rst.inc
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
.. code-block:: php

abstract class AbstractVoter implements VoterInterface
{
public function supportsAttribute($attribute);
public function supportsClass($class);
public function vote(TokenInterface $token, $object, array $attributes);

abstract protected function getSupportedClasses();
abstract protected function getSupportedAttributes();
abstract protected function isGranted($attribute, $object, $user = null);
}

Behind the scenes this class implements the
:class:`Symfony\\Component\\Security\\Core\\Authorization\\Voter\\VoterInterface`,
which has this structure:

.. include:: /cookbook/security/voter_interface.rst.inc

The basic functionality covering common use cases is provided
and end developer is expected to implement the abstract methods.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

end developer does not convey end user, either settle for end user or just developer


The :method:`Symfony\\Component\\Security\\Core\\Authorization\\Voter\\AbstractVoter::getSupportedClasses`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think you miss the () at the end?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no

method is used to provide an array of supported classes, i.e. ['\Acme\DemoBundle\Model\Product']
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm skipping all formatting, but what about:

The getSupportedClasses method tells Symfony that your voter should be called whenever an object of one of the given classes is passed to isGranted. For example, if you return array('\Acme\DemoBundle\Model\Product'), Symfony will call your voter when a Product object is passed to isGranted().


The :method:`Symfony\\Component\\Security\\Core\\Authorization\\Voter\\AbstractVoter::getSupportedAttributes`
method is used to provide an array of supported attributes, i.e. ['CREATE', 'READ']
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The getSupportedAttributes method tells Symfony that your voter should be called whenever one of these strings is passes as the first argument to isGranted. For example, if you return array('CREATE', 'READ'), then Symfony will call your voter when one of these is passed to isGranted.


The :method:`Symfony\\Component\\Security\\Core\\Authorization\\Voter\\AbstractVoter::isGranted`
method must implement the business logic that verifies whether or not a given
user is allowed a given attribute on a given object. This method must return a boolean.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

access to a ...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also check your eol

7 changes: 7 additions & 0 deletions cookbook/security/voters.rst
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,13 @@ the security layer. This can be done easily through the service container.
methods in your implementation of the ``vote()`` method and return ``ACCESS_ABSTAIN``
if your voter does not support the class or attribute.


Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should actually use the AbstractVoter in this example. Other than mentioning that VoterInterface exists and you can just implement it, I don't see any disadvantage to always using AbstractVoter. Agree?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think in this particular use case VoterInterface is actually the better choice.
AbstractVoter assumes you know exactly what attributes and classes you want to match, whereas in this situation we're meant to allow everything through (look at how supportsAttribute and supportsClass are defined).

.. tip::

An
:class:`Symfony\\Component\\Security\\Core\\Authorization\\Voter\\AbstractVoter`
is provided to cover the common use cases when implementing security voters.

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

Expand Down
84 changes: 23 additions & 61 deletions cookbook/security/voters_data_permission.rst
Original file line number Diff line number Diff line change
Expand Up @@ -38,10 +38,11 @@ The Voter Interface
-------------------

A custom voter must implement
:class:`Symfony\\Component\\Security\\Core\\Authorization\\Voter\\VoterInterface`,
which has this structure:
:class:`Symfony\\Component\\Security\\Core\\Authorization\\Voter\\VoterInterface`
and an :class:`Symfony\\Component\\Security\\Core\\Authorization\\Voter\\AbstractVoter`
class is provided with following structure:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A custom voter needs to implement VoterInterface or extend AbstractVoter, which makes creating a voter even easier.


.. include:: /cookbook/security/voter_interface.rst.inc
.. include:: /cookbook/security/abstract_voter.rst.inc
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm kind of thinking we shouldn't include this at all. Instead, let's show the 3 abstract methods below with an explanation of what they do down there. And maybe later, we can have a quick sidebar talking about the VoterInterface and its methods.


In this example, the voter will check if the user has access to a specific
object according to your custom conditions (e.g. they must be the owner of
Expand All @@ -61,84 +62,45 @@ edit a particular object. Here's an example implementation:
// src/Acme/DemoBundle/Security/Authorization/Voter/PostVoter.php
namespace Acme\DemoBundle\Security\Authorization\Voter;

use Symfony\Component\Security\Core\Authorization\Voter\VoterInterface;
use Symfony\Component\Security\Core\Authorization\Voter\AbstractVoter;
use Symfony\Component\Security\Core\Authentication\Token\TokenInterface;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to import this TokenInterface class when using the new AbstractVoter?

use Symfony\Component\Security\Core\User\UserInterface;

class PostVoter implements VoterInterface
class PostVoter extends AbstractVoter
{
const VIEW = 'view';
const EDIT = 'edit';

public function supportsAttribute($attribute)
protected function getSupportedAttributes()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wonder why the visibility has changed from public to protected? even if it is an abstract ...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's actually a different method

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes sorry did miss it, thanks!

{
return in_array($attribute, array(
self::VIEW,
self::EDIT,
));
return array(self::VIEW, self::EDIT);
}

public function supportsClass($class)
protected function getSupportedClasses()
{
$supportedClass = 'Acme\DemoBundle\Entity\Post';

return $supportedClass === $class || is_subclass_of($class, $supportedClass);
return array('Acme\DemoBundle\Entity\Post');
}

/**
* @var \Acme\DemoBundle\Entity\Post $post
*/
public function vote(TokenInterface $token, $post, array $attributes)
protected function isGranted($attribute, $post, $user = null)
{
// check if class of this object is supported by this voter
if (!$this->supportsClass(get_class($post))) {
return VoterInterface::ACCESS_ABSTAIN;
}

// check if the voter is used correct, only allow one attribute
// this isn't a requirement, it's just one easy way for you to
// design your voter
if(1 !== count($attributes)) {
throw new \InvalidArgumentException(
'Only one attribute is allowed for VIEW or EDIT'
);
}

// set the attribute to check against
$attribute = $attributes[0];

// check if the given attribute is covered by this voter
if (!$this->supportsAttribute($attribute)) {
return VoterInterface::ACCESS_ABSTAIN;
}

// get current logged in user
$user = $token->getUser();

// make sure there is a user object (i.e. that the user is logged in)
if (!$user instanceof UserInterface) {
return VoterInterface::ACCESS_DENIED;
return false;
}

// the data object could have for example a method isPrivate()
// which checks the Boolean attribute $private
if ($attribute == self::VIEW && !$post->isPrivate()) {
return true;
}

switch($attribute) {
case self::VIEW:
// the data object could have for example a method isPrivate()
// which checks the Boolean attribute $private
if (!$post->isPrivate()) {
return VoterInterface::ACCESS_GRANTED;
}
break;

case self::EDIT:
// we assume that our data object has a method getOwner() to
// get the current owner user entity for this data object
if ($user->getId() === $post->getOwner()->getId()) {
return VoterInterface::ACCESS_GRANTED;
}
break;
// we assume that our data object has a method getOwner() to
// get the current owner user entity for this data object
if ($attribute == self::EDIT && $user->getId() === $post->getOwner()->getId()) {
return true;
}

return VoterInterface::ACCESS_DENIED;
return false;
}
}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Down here is where I'd want to see a list of what each method does (similar to what you have in the included file now).

Expand Down
0