Permalink
Browse files

minor #3898 clarifying the need of a factory for auth-provider (leber…

…knecht)

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
  • Loading branch information...
weaverryan committed Jun 7, 2014
2 parents 0626f2b + 51a8856 commit 1dc8b4af41b6e89a22ca79ed95c84955e1e8a1e6
Showing with 2 additions and 2 deletions.
  1. +2 −2 cookbook/security/custom_authentication_provider.rst
@@ -287,8 +287,8 @@ The Factory
-----------
You have created a custom token, custom listener, and custom provider. Now
you need to tie them all together. How do you make your provider available
to your security configuration? The answer is by using a *factory*. A factory
you need to tie them all together. How do you make a unique provider available
for every firewall? The answer is by using a *factory*. A factory
is where you hook into the Security component, telling it the name of your
provider and any configuration options available for it. First, you must
create a class which implements

0 comments on commit 1dc8b4a

Please sign in to comment.