Skip to content

Move caution plus reword #13192

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
Feb 20, 2020
Merged

Move caution plus reword #13192

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
5 changes: 5 additions & 0 deletions security/user_provider.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -215,6 +215,11 @@ It's not recommended to use this provider in real applications because of its
limitations and how difficult it is to manage users. It may be useful in application
prototypes and for limited applications that don't store users in databases.

.. caution::

When using a ``memory`` provider, the :class:`Symfony\\Component\\Security\\Core\\User\\User`
and not the ``auto`` algorithm, you have to choose an encoding without salt (i.e. ``bcrypt``).

This user provider stores all user information in a configuration file,
including their passwords. That's why the first step is to configure how these
users will encode their passwords:
Expand Down