IDP node stickiness without an SLB?

[Martin Haase]

Thanks Scott for your prompt reply.

What about my other question (copied below), any ideas anybody?
> 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
> b) what do people do to work around this?

We just thought about some kind of SAMLRequest replay for/at the node
that would say "stale request". Other thoughts?

Regards,
Martin



Am 28.09.2015 um 15:56 schrieb Cantor, Scott:
> On 9/28/15, 9:34 AM, "users on behalf of Martin Haase" <users-bounces at shibboleth.net on behalf of Martin.Haase at DAASI.de> wrote:
>> 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)
> The entire state of the request is explicitly non-serializable. It's fundamental. You would have to build your own logic to serialize and deseralize the state, and figure out how to plug that into webflow. It would not be maintainable by anyone else, but if there were a way to do it, it's possible we would accept the code. I don't think it's practical (not to say impossible).
>
> -- Scott
>

-- 
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