@@ -841,15 +841,6 @@ You can easily deny access from inside a controller::
841841 // ...
842842 }
843843
844- ..versionadded ::2.6
845- The ``denyAccessUnlessGranted() `` method was introduced in Symfony 2.6. Previously (and
846- still now), you could check access directly and throw the ``AccessDeniedException `` as shown
847- in the example above).
848-
849- ..versionadded ::2.6
850- The ``security.authorization_checker `` service was introduced in Symfony 2.6. Prior
851- to Symfony 2.6, you had to use the ``isGranted() `` method of the ``security.context `` service.
852-
853844In both cases, a special
854845:class: `Symfony\\ Component\\ Security\\ Core\\ Exception\\ AccessDeniedException `
855846is thrown, which ultimately triggers a 403 HTTP response inside Symfony.
@@ -1016,10 +1007,6 @@ shown above.
10161007Retrieving the User Object
10171008--------------------------
10181009
1019- ..versionadded ::2.6
1020- The ``security.token_storage `` service was introduced in Symfony 2.6. Prior
1021- to Symfony 2.6, you had to use the ``getToken() `` method of the ``security.context `` service.
1022-
10231010After authentication, the ``User `` object of the current user can be accessed
10241011via the ``security.token_storage `` service. From inside a controller, this will
10251012look like::
@@ -1220,9 +1207,6 @@ in the following way from a controller::
12201207
12211208 $user->setPassword($encoded);
12221209
1223- ..versionadded ::2.6
1224- The ``security.password_encoder `` service was introduced in Symfony 2.6.
1225-
12261210In order for this to work, just make sure that you have the encoder for your
12271211user class (e.g. ``AppBundle\Entity\User ``) configured under the ``encoders ``
12281212key in ``app/config/security.yml ``.