[Deploying Sakai] SSL load balancing and fault tolerance for Sakai

Steve Swinsburg steve.swinsburg at gmail.com
Thu Aug 13 06:44:55 PDT 2009

If the other group of people are in their own LDAP, then you could use  
a chained LDAP provider which searches your institutional one first,  
then fallsback to the second (and third and so on).

I have an article here about LDAP in Sakai:

If the chained LDAP approach seems reasonable, I can get you the code  
for it. Other people in the community have written other complex  
providers as well so what you want to be done is definitely doable.


On 13 Aug 2009, at 14:36, Grossman,John E wrote:

> Thanks to you both for the suggestions.
> The reason we are using our own app for LDAP auth and then calling  
> the web service is that we need hybrid authentication. We have two  
> groups of users – one group in the institutional LDAP and another  
> group of external users whose credentials are managed in another  
> custom app. Our auth app will direct the authentication request to  
> the appropriate resource depending on which group a user is in.  
> Sorry I didn’t mention that wrinkle.
> BTW - Could you point me to the docs for the built-in LDAP support?  
> Based on my searches I thought the web services approach was the way  
> to go for LDAP. I’d like to understand the built-in facilities.
> _______________________________________________
> production mailing list
> production at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/production
> TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org 
>  with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20090813/47a71717/attachment.html 

More information about the production mailing list