Skip to content

Commit 8f9a31a

Browse files
committed
minor #12371 [Security] Deprecated using more than one role in access_control rules (javiereguiluz)
This PR was merged into the 4.4 branch. Discussion ---------- [Security] Deprecated using more than one role in access_control rules Fixes #12363. Commits ------- 19475ed [Security] Deprecated using more than one role in access_control rules
2 parents e1b79e0 + 19475ed commit 8f9a31a

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

security/access_control.rst

+10
Original file line numberDiff line numberDiff line change
@@ -103,6 +103,11 @@ Take the following ``access_control`` entries as an example:
103103
],
104104
]);
105105
106+
.. deprecated:: 4.4
107+
108+
Using more than one role in a single ``access_control`` rule is deprecated
109+
and will stop working in Symfony 5.0.
110+
106111
For each incoming request, Symfony will decide which ``access_control``
107112
to use based on the URI, the client's IP address, the incoming host name,
108113
and the request method. Remember, the first rule that matches is used, and
@@ -153,6 +158,11 @@ options:
153158
is thrown). If this value is an array of multiple roles, the user must have
154159
at least one of them.
155160

161+
.. deprecated:: 4.4
162+
163+
Using more than one role in a single ``access_control`` rule is deprecated
164+
and will stop working in Symfony 5.0.
165+
156166
* ``allow_if`` If the expression returns false, then access is denied;
157167

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

0 commit comments

Comments
 (0)