From 4aac6e6f252f4f0598920b96df5a90fe60e63382 Mon Sep 17 00:00:00 2001 From: asandjivy Date: Fri, 19 Aug 2016 15:06:28 +0200 Subject: [PATCH] Update custom_provider.rst "in_memory" does not exist. This is a just a provider name. The real keyword is "memory" --- security/custom_provider.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/security/custom_provider.rst b/security/custom_provider.rst index 82d3ef2c8e9..71c9dbe4fd7 100644 --- a/security/custom_provider.rst +++ b/security/custom_provider.rst @@ -9,7 +9,7 @@ When a user submits a username and password, the authentication layer asks the configured user provider to return a user object for a given username. Symfony then checks whether the password of this user is correct and generates a security token so the user stays authenticated during the current session. -Out of the box, Symfony has four user providers: ``in_memory``, ``entity``, +Out of the box, Symfony has four user providers: ``memory``, ``entity``, ``ldap`` and ``chain``. In this entry you'll see how you can create your own user provider, which could be useful if your users are accessed via a custom database, a file, or - as shown in this example - a web service.