Oct 24, 2022 · Oct 23, 2022 · Oct 24, 2022
diff --git a/security/access_control.rst b/security/access_control.rst
 * ``host``: a regular expression
 * ``methods``: one or many HTTP methods
 * ``request_matcher``: a service implementing ``RequestMatcherInterface``
 * ``attributes``: an array, which can be used to specify one or more :ref:`request attributes <accessing-request-data>` that must match exactly
 * ``route``: a route name

 .. versionadded:: 6.1

    The ``request_matcher`` option was introduced in Symfony 6.1.

 .. versionadded:: 6.2

    The ``route`` and ``attributes`` options were introduced in Symfony 6.2.

 Take the following ``access_control`` entries as an example:

 .. configuration-block::
                # for custom matching needs, use a request matcher service
                - { roles: ROLE_USER, request_matcher: App\Security\RequestMatcher\MyRequestMatcher }

                # require ROLE_ADMIN for 'admin' route. You can use the shortcut "route: "xxx", instead of "attributes": ["_route": "xxx"]
                - { attributes: {'_route': 'admin'}, roles: ROLE_ADMIN }
                - { route: 'admin', roles: ROLE_ADMIN }

    .. code-block:: xml

        <!-- config/packages/security.xml -->

                <!-- for custom matching needs, use a request matcher service -->
                <rule role="ROLE_USER" request-matcher="App\Security\RequestMatcher\MyRequestMatcher"/>

                <!-- require ROLE_ADMIN for 'admin' route. You can use the shortcut route="xxx" -->
                <rule role="ROLE_ADMIN">
                    <attribute key="_route">admin</attribute>
                </rule>
                <rule route="admin" role="ROLE_ADMIN"/>
            </config>
        </srv:container>

                ->roles(['ROLE_USER'])
                ->requestMatcher('App\Security\RequestMatcher\MyRequestMatcher')
            ;

            // require ROLE_ADMIN for 'admin' route. You can use the shortcut route('xxx') mehtod,
            // instead of attributes(['_route' => 'xxx']) method
            $security->accessControl()
                ->roles(['ROLE_ADMIN'])
                ->attributes(['_route' => 'admin'])
            ;
            $security->accessControl()
                ->roles(['ROLE_ADMIN'])
                ->route('admin')
            ;
        };

 For each incoming request, Symfony will decide which ``access_control``
Original file line number	Diff line number	Diff line change
Expand Up		@@ -30,11 +30,17 @@ options are used for matching:
		* ``host``: a regular expression
		* ``methods``: one or many HTTP methods
		* ``request_matcher``: a service implementing ``RequestMatcherInterface``
		* ``attributes``: an array, which can be used to specify one or more :ref:`request attributes <accessing-request-data>` that must match exactly
		* ``route``: a route name

		.. versionadded:: 6.1

		The ``request_matcher`` option was introduced in Symfony 6.1.

		.. versionadded:: 6.2

		The ``route`` and ``attributes`` options were introduced in Symfony 6.2.

		Take the following ``access_control`` entries as an example:

		.. configuration-block::
Expand All		@@ -60,6 +66,10 @@ Take the following ``access_control`` entries as an example:
		# for custom matching needs, use a request matcher service
		- { roles: ROLE_USER, request_matcher: App\Security\RequestMatcher\MyRequestMatcher }

		# require ROLE_ADMIN for 'admin' route. You can use the shortcut "route: "xxx", instead of "attributes": ["_route": "xxx"]
		- { attributes: {'_route': 'admin'}, roles: ROLE_ADMIN }
		- { route: 'admin', roles: ROLE_ADMIN }

		.. code-block:: xml

		<!-- config/packages/security.xml -->
Expand DownExpand Up		@@ -93,6 +103,12 @@ Take the following ``access_control`` entries as an example:

		<!-- for custom matching needs, use a request matcher service -->
		<rule role="ROLE_USER" request-matcher="App\Security\RequestMatcher\MyRequestMatcher"/>

		<!-- require ROLE_ADMIN for 'admin' route. You can use the shortcut route="xxx" -->
		<rule role="ROLE_ADMIN">
		<attribute key="_route">admin</attribute>
		</rule>
		<rule route="admin" role="ROLE_ADMIN"/>
		</config>
		</srv:container>

Expand DownExpand Up		@@ -144,6 +160,17 @@ Take the following ``access_control`` entries as an example:
		->roles(['ROLE_USER'])
		->requestMatcher('App\Security\RequestMatcher\MyRequestMatcher')
		;

		// require ROLE_ADMIN for 'admin' route. You can use the shortcut route('xxx') mehtod,
		// instead of attributes(['_route' => 'xxx']) method
		$security->accessControl()
		->roles(['ROLE_ADMIN'])
		->attributes(['_route' => 'admin'])
		;
		$security->accessControl()
		->roles(['ROLE_ADMIN'])
		->route('admin')
		;
		};

		For each incoming request, Symfony will decide which ``access_control``
Expand Down