How to clean the SP after "shibsp::ConfigurationException"

Rainer Hoerbe rainer at
Mon Aug 20 12:21:52 EDT 2012

Am 20.08.2012 um 18:03 schrieb "Cantor, Scott" <cantor.2 at>:

>> I did not change the configuration.
> Change it from what? The default has an entityID of
> configured, which obviously won't
> work but won't cause that error either. If you mean it was working, I
> don't think that's possible. About all I could think would be if you use a
> DS and then the user returns from the DS without a selection made.
> Handling that case while still requiring a session won't really work.

I am using a single type SAML2 SessionInitiator, so no chaining, no DS.

I did not change any relevant element in shibboleth2.xml from the previous working configuration, and did not touch or any other config file.

The strange thing is: In the error state I restored former, working versions of my shibboleth2.xml, restarted shibd with them, but the error state remained. Although I did not believe that the browser cache could be the culprit, I tried with another browser from another VM, but it has the same result.

> It can't fix itself unless the configuration is fixed. You're missing
> something somewhere.

This is what I watched, and I did not have a beer with my lunch.

So you are saying that all state is purged when restarting shibd?

- Rainer

More information about the users mailing list