Skip to content

Adding anonymous #13414

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 27, 2020
Merged

Adding anonymous #13414

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 15 additions & 1 deletion reference/configuration/security.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@ Configuration

* `access_denied_url`_
* `always_authenticate_before_granting`_
* `anonymous`_
* `erase_credentials`_
* `hide_user_not_found`_
* `session_fixation_strategy`_
Expand Down Expand Up @@ -61,6 +62,19 @@ If ``true``, the user is asked to authenticate before each call to the
``isGranted()`` method in services and controllers or ``is_granted()`` from
templates.

anonymous
~~~~~~~~~

**type**: ``string`` **default**: ``~``

When set to ``lazy``, Symfony loads the user (and starts the session) only if the
application actually accesses the ``User`` object (e.g. via a ``is_granted()`` call
in a template or ``isGranted()`` in a controller or service.

.. versionadded:: 4.4

The option ``lazy`` was introduced in Symfony 4.4.

erase_credentials
~~~~~~~~~~~~~~~~~

Expand Down Expand Up @@ -554,7 +568,7 @@ logout_on_user_change
The ``logout_on_user_change`` option was deprecated in Symfony 4.1.

If ``false`` this option makes Symfony to not trigger a logout when the user has
changed. Doing that is deprecated, so this option should set to ``true`` or
changed. Doing that is deprecated, so this option should be set to ``true`` or
unset to avoid getting deprecation messages.

The user is considered to have changed when the user class implements
Expand Down