Shibboleth handler invoked at an unconfigured location
sabiretude at gmail.com
Wed May 18 11:40:51 EDT 2016
Yeah I did forgot that you suggested this. Anyway, can anyone be clear and
write an example of how we can set the cookie scope (you know write a
simple line of shibboleth2.xml illustrating the how)?
2016-05-18 16:26 GMT+02:00 Peter Schober <peter.schober at univie.ac.at>:
> * reda sabir <sabiretude at gmail.com> [2016-05-18 11:27]:
> > I found a more simple solution:
> You didn't, that's exactly what I wrote in my previous reply which you
> even quoted again:
> * Peter Schober <peter.schober at univie.ac.at> [2016-05-17 19:40]:
> > If the vhosts share a common DNS domain you could try to forgo
> > SAML-based SSO (involving a set of IDPs) and instead use a shared
> > domain cookie across all services. (Either the Shibboleth SP's session
> > cookie or an application cookie initially bootstrapped from one Shib
> > SP session and shared across all vhosts).
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users