-
Nov 23rd, 2011, 02:11 AM
#1
AuthenticationProvider or AbstractAuthenticationProcessingFilter for web app?
Is it enough to implement the attemptAuthentication of the AbstractAuthenticationProcessingFilter to support custom authentication? Or, do I have to delegate the actual authentication to an AuthenticationProvider through the authenticate method of the AuthenticationManager?
The system I am working on authenticates users using an API of a content management system by passing the username, password and repository to create a connection with the repository. I am not sure whether the authentication need to be done in an AbstractAuthenticationProcessingFilter or an AuthenticationProvider. Luke Taylor suggested using AuthenticationProcessingFilter for web authentication in the following thread http://forum.springsource.org/showth...792#post245792. However, most of the online resources that I have read used an AuthenticationProvider.
Last edited by suikodian; Nov 29th, 2011 at 12:40 AM.
-
Nov 29th, 2011, 12:44 AM
#2
I would appreciate your advice and thoughts on this.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules