IDP node stickiness without an SLB?

[Martin Haase]

Dear Scott, dear list,

we are implementing the IdP v3 in a project with dynamically clustered
nodes, i.e. the single IdP nodes will be created and shut down as
needed. One requirement was a non-sticky Load Balancer in order to
detect failing nodes even during log-in. So we must find a way to work
around the "degree of session 'stickiness'" mentioned at
https://wiki.shibboleth.net/confluence/display/IDP30/Clustering#Clustering-ConversationalState


That page says the IdP does not support this kind of thing, however,
some containers would (in our case it is Tomcat, we tried
https://code.google.com/p/memcached-session-manager) and Spring WebFlow
could use that in principle. Here our questions:

a) which parts of the IdP software are affected by the
Not-Serializable-Issue (we found:
org.opensaml.profile.context.ProfileRequestContext, there are maybe more)

b) what do people do to work around this?

Regards,
Martin


Am 21.01.2014 um 23:25 schrieb Cantor, Scott:
> I can't help you but I want to emphasize that this is not changing in V3.
> We are not trying to solve the essentially unsolveable problem of
> clustering every request. The Web Flow engine will only work reliably with
> stickiness through the flow.
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net

-- 
Dr. Martin Haase, Solutions Engineer

DAASI International GmbH        
Europaplatz 3                   
D-72072 Tübingen                
Germany                    

phone: +49 7071 407109-6
fax:   +49 7071 407109-9  
email: martin.haase at daasi.de
web:   www.daasi.de

Sitz der Gesellschaft: Tübingen
Registergericht: Amtsgericht Stuttgart, HRB 382175
Geschäftsleitung: Peter Gietz