Skip to content
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

Cleanup security voters cookbook recipes #5453

Merged
merged 3 commits into from
Jul 16, 2015
Merged
Show file tree
Hide file tree
Changes from all commits
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
10 changes: 5 additions & 5 deletions book/security.rst
Original file line number Diff line number Diff line change
Expand Up @@ -929,10 +929,10 @@ other users. Also, as the admin user, you yourself want to be able to edit

To accomplish this you have 2 options:

* :doc:`Voters </cookbook/security/voters_data_permission>` allow you to
use business logic (e.g. the user can edit this post because they were
the creator) to determine access. You'll probably want this option - it's
flexible enough to solve the above situation.
* :doc:`Voters </cookbook/security/voters>` allow you to use business logic
Copy link
Member

Choose a reason for hiding this comment

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

[...] to use business logic [...] looks very generic to me. I'd like something like: ... apply your own business logic ..., ... define the custom logic applied to ..., etc.

Choose a reason for hiding this comment

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

👍

(e.g. the user can edit this post because they were the creator) to determine
access. You'll probably want this option - it's flexible enough to solve the
above situation.

* :doc:`ACLs </cookbook/security/acl>` allow you to create a database structure
where you can assign *any* arbitrary user *any* access (e.g. EDIT, VIEW)
Expand Down Expand Up @@ -1281,7 +1281,7 @@ Learn More from the Cookbook

* :doc:`Forcing HTTP/HTTPS </cookbook/security/force_https>`
* :doc:`Impersonating a User </cookbook/security/impersonating_user>`
* :doc:`/cookbook/security/voters_data_permission`
* :doc:`/cookbook/security/voters`
* :doc:`Access Control Lists (ACLs) </cookbook/security/acl>`
* :doc:`/cookbook/security/remember_me`
* :doc:`/cookbook/security/multiple_user_providers`
Expand Down
1 change: 0 additions & 1 deletion cookbook/map.rst.inc
Original file line number Diff line number Diff line change
Expand Up @@ -151,7 +151,6 @@
* :doc:`/cookbook/security/remember_me`
* :doc:`/cookbook/security/impersonating_user`
* :doc:`/cookbook/security/voters`
* :doc:`/cookbook/security/voters_data_permission`
* :doc:`/cookbook/security/acl`
* :doc:`/cookbook/security/acl_advanced`
* :doc:`/cookbook/security/force_https`
Expand Down
2 changes: 1 addition & 1 deletion cookbook/security/acl.rst
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ the ACL system comes in.
Using ACL's isn't trivial, and for simpler use cases, it may be overkill.
If your permission logic could be described by just writing some code (e.g.
to check if a Blog is owned by the current User), then consider using
:doc:`voters </cookbook/security/voters_data_permission>`. A voter is passed the object
:doc:`voters </cookbook/security/voters>`. A voter is passed the object
being voted on, which you can use to make complex decisions and effectively
implement your own ACL. Enforcing authorization (e.g. the ``isGranted``
part) will look similar to what you see in this entry, but your voter
Expand Down
1 change: 0 additions & 1 deletion cookbook/security/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,6 @@ Security
remember_me
impersonating_user
voters
voters_data_permission
acl
acl_advanced
force_https
Expand Down
24 changes: 0 additions & 24 deletions cookbook/security/voter_interface.rst.inc

This file was deleted.

Loading