8000 minor #3898 clarifying the need of a factory for auth-provider (leber… · symfony/symfony-docs@1dc8b4a · GitHub
[go: up one dir, main page]

Skip to content

Commit 1dc8b4a

Browse files
committed
minor #3898 clarifying the need of a factory for auth-provider (leberknecht)
This PR was submitted for the 2.4 branch but it was merged into the 2.3 branch instead (closes #3898). Discussion ---------- clarifying the need of a factory for auth-provider I think the documentation is a little bit unclear here. It doesnt actually explain why we dont simply expose the provider via "normal" service definition, but instead doing it in a compiler pass. Commits ------- bd3e5f3 clarifying the need of a factory for auth-provider
2 parents 0626f2b + 51a8856 commit 1dc8b4a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

cookbook/security/custom_authentication_provider.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -287,8 +287,8 @@ The Factory
287287
-----------
288288

289289
You have created a custom token, custom listener, and custom provider. Now
290-
you need to tie them all together. How do you make your provider available
291-
to your security configuration? The answer is by using a *factory*. A factory
290+
you need to tie them all together. How do you make a unique provider available
291+
for every firewall? The answer is by using a *factory*. A factory
292292
is where you hook into the Security component, telling it the name of your
293293
provider and any configuration options available for it. First, you must
294294
create a class which implements

0 commit comments

Comments
 (0)
0