Skip to content

make the advantage and disadvantage of the ACL more clear #2989

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 3 commits into from
Closed
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
12 changes: 12 additions & 0 deletions cookbook/security/acl.rst
Original file line number Diff line number Diff line change
Expand Up @@ -215,4 +215,16 @@ added above:

The user is now allowed to view, edit, delete, and un-delete objects.

Looking for Alternatives
------------------------

For more simple use cases this seems to be an overhead for many developers.
As a downside there is that in case you change the permissions in any way,
you need to change all the existing granted permissions as well. As well
when you want to change a specific part of the ACL you need to understand
the structure and process of this complex voter. So you should consider if
a classical and simple conditional permission check would fit for you.
Some do it with the existing voter ":doc:`/cookbook/security/voters`"
structure as well, or a custom build solutions.

.. _`MongoDBAclBundle`: https://github.com/IamPersistent/MongoDBAclBundle