Skip to content

[Security] Deprecated using more than one role in access_control rules #12371

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

Merged
merged 1 commit into from
Sep 26, 2019
Merged

[Security] Deprecated using more than one role in access_control rules #12371

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 security/access_control.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,6 +103,11 @@ Take the following ``access_control`` entries as an example:
],
]);

.. deprecated:: 4.4

Using more than one role in a single ``access_control`` rule is deprecated
and will stop working in Symfony 5.0.

For each incoming request, Symfony will decide which ``access_control``
to use based on the URI, the client's IP address, the incoming host name,
and the request method. Remember, the first rule that matches is used, and
Expand Down Expand Up @@ -153,6 +158,11 @@ options:
is thrown). If this value is an array of multiple roles, the user must have
at least one of them.

.. deprecated:: 4.4

Using more than one role in a single ``access_control`` rule is deprecated
and will stop working in Symfony 5.0.

* ``allow_if`` If the expression returns false, then access is denied;

* ``requires_channel`` If the incoming request's channel (e.g. ``http``)
Expand Down