Le 13/05/2011 13:30, Jimmy Bourassa a écrit :
On May 13, 4:00 am, Christophe COEVOET<s...@notk.org> wrote:
Define it as a service and configure the provider using the id of you
service:
security:
providers:
custom:
id: my_custom_provider
--
Christophe | Stof
I'm affraid that's for injecting UserProvider, what I am looking for
is a way to inject AuthentificationProvider.
This is the error I got :
Argument 1 passed to Symfony\Component\Security\Core\Authentication
\Provider\DaoAuthenticationProvider::__construct() must be an instance
of Symfony\Component\Security\Core\User\UserProviderInterface,
instance of Soutex\SoutexBundle\Security\Authentication\LdapProvider
given
(My LdapProvider class implements the AuthenticationProviderInterface)
Ok, I missed your point. Implementing your own AuthenticationProvider is
one of the most advanced thing in the security component. Thus, I don't
think you need it for an Ldap authentication. The good interface would
be UserProviderInterface IMO.
You should probably look at https://github.com/opensky/LdapBundle to see
if it fits your needs. using this bundle developed by some core devs
would be easier than implementing your own (and they are not using a
custom AuthenticationProvider in thier bundle)
--
Christophe | Stof
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
