Skip to content

Commit 3a7020c

Browse files
committed
[#3356] Fixing ticks that don't work inside a bold and removing extra details in intro area that aren't necessary (you'll need to read the cookbook entry for more details anyways)
1 parent 2a1a349 commit 3a7020c

File tree

1 file changed

+1
-14
lines changed

1 file changed

+1
-14
lines changed

book/security.rst

Lines changed: 1 addition & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -660,7 +660,7 @@ see :doc:`/cookbook/security/form_login`.
660660
),
661661
),
662662
663-
**3. Be sure ``/login_check`` is behind a firewall**
663+
**3. Be sure /login_check is behind a firewall**
664664

665665
Next, make sure that your ``check_path`` URL (e.g. ``/login_check``)
666666
is behind the firewall you're using for your form login (in this example,
@@ -1206,19 +1206,6 @@ custom user class is that it implements the :class:`Symfony\\Component\\Security
12061206
interface. This means that your concept of a "user" can be anything, as long
12071207
as it implements this interface.
12081208

1209-
.. versionadded:: 2.1
1210-
In Symfony 2.1, the ``equals`` method was removed from ``UserInterface``.
1211-
If you need to override the default implementation of comparison logic,
1212-
implement the new :class:`Symfony\\Component\\Security\\Core\\User\\EquatableInterface`
1213-
interface.
1214-
1215-
.. note::
1216-
1217-
The user object will be serialized and saved in the session during requests,
1218-
therefore it is recommended that you `implement the \Serializable interface`_
1219-
in your user object. This is especially important if your ``User`` class
1220-
has a parent class with private properties.
1221-
12221209
Next, configure an ``entity`` user provider, and point it to your ``User``
12231210
class:
12241211

0 commit comments

Comments
 (0)