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

Cantor, Scott cantor.2 at
Mon Aug 20 13:18:41 EDT 2012

On 8/20/12 1:07 PM, "Rainer Hoerbe" <rainer at> wrote:

>> Then I would guess metadata's involved somewhere.
>I own the metadata and did not change it. Shibd did not detect a change
>either for at least 3 days:
>"remote resource (
>unchanged, adjusted reload interval to 7200 seconds"

I'm lost then. The only way you get the error is if the session initiator
chain or handler falls through without dispatching a request (if and only
if you actually require a session and there isn't one). All I did was
inject a more explicit error message for that situation.

I think you'd also have to *not* have a chain in place (and I think you
said you just explicitly configured the SAML 2 handler).

So something prevented it from successfully generate the request. Are
there any logs on either native or shibd side about it?

-- Scott

More information about the users mailing list