Google Groups Home
Help | Sign in
pipeline authentication
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
Jim  
View profile
 More options Jul 3, 9:01 am
From: Jim <thatsj...@gmail.com>
Date: Wed, 2 Jul 2008 16:01:37 -0700 (PDT)
Local: Thurs, Jul 3 2008 9:01 am
Subject: pipeline authentication
Hi All!

I was just wondering how I could implement two authentication sources
(both LDAP) using the pipeline feature (so that if a user fails
authentication in the first source, then it will try to authenticate
with the second).
I tried messing around with the spring configuration for the
userPassword plugin but had no luck.

I am using version 0.7.0

Any help would be much appreciated!
thanks,
Jim


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Bradley Beddoes  
View profile
 More options Jul 3, 9:49 am
From: Bradley Beddoes <bedd...@intient.com>
Date: Thu, 03 Jul 2008 09:49:58 +1000
Local: Thurs, Jul 3 2008 9:49 am
Subject: Re: [esoe-users] pipeline authentication
Hi Jim,

Jim wrote:
> Hi All!

> I was just wondering how I could implement two authentication sources
> (both LDAP) using the pipeline feature (so that if a user fails
> authentication in the first source, then it will try to authenticate
> with the second).
> I tried messing around with the spring configuration for the
> userPassword plugin but had no luck.

usernamePassword is handler is implemented as what we term "catch-all".
So the pipeline doesn't progress past that point until a user is
identified. (Gory details here:
http://esoeproject.org/confluence/display/ed/ESOE+Design#ESOEDesign-U...
)

This handler takes in its constructor an object that implements the
interface UserPassAuthenticator. Currently you'll see from the spring
configuration we ship by default an implementation called
LDAPBasicAuthenticator. It simply uses the passed credentials to attempt
a bind or compare against a single LDAP server.

My advice to you is to create your own object that implements
UserPassAuthenticator that checks against as many LDAP (or database or
flatfile whatever you like) sources until it either finds a valid user
and returns a successful result or exhausts them all and returns a
negative result. This new object can then be easily wired in using the
spring config files.

Hope that is of assistance, additionally this kind of custom work is how
we support ESOE development if you'd like to discuss us building this
for you please contact me off list.

regards,
Bradley


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2008 Google