clarifying the need of a factory for auth-provider

leberknecht · leberknecht · commit bd3e5f3ed369 · 2014-06-01T18:49:03.000+02:00
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.
diff --git a/cookbook/security/custom_authentication_provider.rst b/cookbook/security/custom_authentication_provider.rst
@@ -299,8 +299,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
