Commit92eecd3

committed

Merge branch '2.3' into 2.6

* 2.3: [#5453] Minor tweaks - mostly thanks to Javier

2 parentsf71cc85 +d4afd3a commit92eecd3Copy full SHA for 92eecd3

File tree

-3

lines changed

-3

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -994,7 +994,7 @@ other users. Also, as the admin user, you yourself want to be able to edit`
`994`	`994`
`995`	`995`	`To accomplish this you have 2 options:`
`996`	`996`
`997`		-*:doc:`Voters</cookbook/security/voters>` allow you touse business logic
	`997`	+*:doc:`Voters</cookbook/security/voters>` allow you towrite own business logic
`998`	`998`	`(e.g. the user can edit this post because they were the creator) to determine`
`999`	`999`	`access. You'll probably want this option - it's flexible enough to solve the`
`1000`	`1000`	`above situation.`

Lines changed: 3 additions & 2 deletions

Original file line number	Diff line number	Diff line change
@@ -28,8 +28,9 @@ All voters are called each time you use the ``isGranted()`` method on Symfony's
`28`	`28`	authorization checker (i.e. the ``security.authorization_checker`` service). Each
`29`	`29`	`one decides if the current user should have access to some resource.`
`30`	`30`
`31`		`-Ultimately, Symfony uses one of three different approaches on what to do`
`32`		`-with the feedback from all voters: affirmative, consensus and unanimous.`
	`31`	`+Ultimately, Symfony takes the responses from all voters and makes the final`
	`32`	`+decission (to allow or deny access to the resource) according to the strategy defined`
	`33`	`+in the application, which can be: affirmative, consensus or unanimous.`
`33`	`34`
`34`	`35`	`For more information take a look at`
`35`	`36`	:ref:`the section about access decision managers<components-security-access-decision-manager>`.

Comments

(0)