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

Cantor, Scott cantor.2 at
Mon Aug 20 12:03:43 EDT 2012

On 8/20/12 11:52 AM, "Rainer Hoerbe" <rainer at> wrote:

>I ran into a state where the SP is stuck with a
>shibsp::ConfigurationException at
>( . Session initiator did not
>handle request for a new session, check configuration.

That's the message I changed that crops up in the case where you have it
require a session, but don't provide it with either an entityID or a DS to
use, so the config is corrupt/unusable.

>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.

>The problem is that the SP remains in this state even across restarts.

Well, yes, the configuration is unusable.

> But it did reset itself over the lunch break. Is there a kind of
>clean-flush-purge -f command to have that effect immediately?

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

-- Scott

More information about the users mailing list