Skip to content

Commit 420b338

Browse files
javiereguiluzweaverryan
authored andcommitted
Added a mention to the @Security annotation
1 parent 14a080f commit 420b338

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

cookbook/security/remember_me.rst

+8-6
Original file line numberDiff line numberDiff line change
@@ -175,21 +175,25 @@ In the following example, the action is only allowed if the user has the
175175
The ``security.authorization_checker`` service was introduced in Symfony 2.6. Prior
176176
to Symfony 2.6, you had to use the ``isGranted()`` method of the ``security.context`` service.
177177

178-
You can also choose to install and use the optional JMSSecurityExtraBundle_,
179-
which can secure your controller using annotations:
178+
If your application is based on the Symfony Standard Edition, you can also secure
179+
your controller using annotations:
180180

181181
.. code-block:: php
182182
183-
use JMS\SecurityExtraBundle\Annotation\Secure;
183+
use Sensio\Bundle\FrameworkExtraBundle\Configuration\Security;
184184
185185
/**
186-
* @Secure(roles="IS_AUTHENTICATED_FULLY")
186+
* @Security("has_role('IS_AUTHENTICATED_FULLY')")
187187
*/
188188
public function editAction($name)
189189
{
190190
// ...
191191
}
192192
193+
.. versionadded:: 2.4
194+
The ``@Security`` annotation was introduced in SensioFrameworkExtraBundle 3.0,
195+
which can only be used with Symfony 2.4 or later.
196+
193197
.. tip::
194198

195199
If you also had an access control in your security configuration that
@@ -212,5 +216,3 @@ which can secure your controller using annotations:
212216

213217
For more information on securing services or methods in this way,
214218
see :doc:`/cookbook/security/securing_services`.
215-
216-
.. _JMSSecurityExtraBundle: https://github.com/schmittjoh/JMSSecurityExtraBundle

0 commit comments

Comments
 (0)