StorageService-backed RelayState mechanism did not return a state value.
dmclaughlin at tech-consortium.com
Mon Nov 19 17:24:00 EST 2018
So the benefit of switching the relayState from ss:mem to cookie is
that if a client starts a request on one node in a webserver/SP
cluster and then we stop the server they are on and the client fails
over to another webserver/SP in the cluster they will still be logged
in? If that's correct, then what's the down side of using relayState
cookie, and why would you ever want to use relayState ss:mem?
On Mon, Nov 19, 2018 at 4:10 PM Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 11/19/18, 5:00 PM, "users on behalf of Dan McLaughlin" <users-bounces at shibboleth.net on behalf of dmclaughlin at tech-consortium.com> wrote:
> > To use cookie is the only thing we have to do is change the relayState
> > from ss:mem to cookie?
> To change the mechanism used for tracking RelayState, yes.
> -- Scott
> For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users