Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitf11f34b

Browse files
committed
bug#6892 Update custom_provider.rst (asandjivy)
This PR was submitted for the 3.1 branch but it was merged into the 2.8 branch instead (closes#6892).Discussion----------Update custom_provider.rst"in_memory" does not exist. This is a just a provider name. The real keyword is "memory"Commits-------2d5b420 Update custom_provider.rst
2 parentsbc00741 +2d5b420 commitf11f34b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎security/custom_provider.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ When a user submits a username and password, the authentication layer asks
99
the configured user provider to return a user object for a given username.
1010
Symfony then checks whether the password of this user is correct and generates
1111
a security token so the user stays authenticated during the current session.
12-
Out of the box, Symfony has four user providers: ``in_memory``, ``entity``,
12+
Out of the box, Symfony has four user providers: ``memory``, ``entity``,
1313
``ldap`` and ``chain``. In this entry you'll see how you can create your
1414
own user provider, which could be useful if your users are accessed via a
1515
custom database, a file, or - as shown in this example - a web service.

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp