IDP node stickiness without an SLB?

[Wessel, Keith]

All,

I'm trying to find a way for our IDP nodes to remain sticky for a user throughout the login process in a GSLB environment where client stickiness isn't an option. The GSLB talks to DNS servers, not clients, and we don't want our entire campus DNS resolver to be sticky to a single IDP node if we can help it.

We deployed Paul's excellent database-backed storage service but had to back out the change. As I understand it, the login process has to stick to a single IDP node when using this solution and, sure enough, we saw problems when a user's browser started on one IDP node then went to the other, either while getting to the login page or when the login page was submitted. Since the session wasn't yet known to the other IDP node, the login couldn't be completed.

Can anyone make any suggestions of how we might, once a user hits node 1 or node 2, keep them going back to that node until they're logged in and returning to the SP? I see no easy way to, say, put an absolute URL in place of /idp for all of the relative URLs presented by the IDP.

If we can't accomplish this, we're planning to still use the database-backed storage service combined with active-passive from our GSLB. But we really do like being able to balance traffic between the two sites when they're both available.

Thanks,
Keith

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140121/424cc02d/attachment-0001.html