StorageService-backed RelayState mechanism did not return a state value.
cantor.2 at osu.edu
Mon Nov 19 17:57:00 EST 2018
On 11/19/18, 5:49 PM, "users on behalf of Dan McLaughlin" <users-bounces at shibboleth.net on behalf of dmclaughlin at tech-consortium.com> wrote:
> I'm guessing you noticed that I had the DataSealer configured, which is why you commented about the relay
> state and clustering.
It's why I assumed you were clustering but it's not connected to the scenario I was assuming. I can't know whether somebody's load balancer is working, and the symptom fit a node change.
> But what you were pointing out earlier was that because I had a relayState
> of ss:mem that clients that failed over would have issues unless I set
> the relayState to cookie.
That's a very rare matter of timing, it would not affect things in a noticeable way unless "fail over" means "lack of stickiness".
> I think if there was an update to Session Recovery section that made it a little more clear that
> relayState="cookie" was required then I might not have missed that step.
I didn't design that feature to eliminate stickiness. It might not perform adequately in that scenario, it wasn't meant to be done that frequently.
More information about the users