Shibboleth handler invoked at an unconfigured location

Peter Schober peter.schober at
Wed May 18 10:26:21 EDT 2016

* reda sabir <sabiretude at> [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> [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).


More information about the users mailing list