opensaml::RetryableProfileException

Cantor, Scott cantor.2 at osu.edu
Wed Jul 25 13:24:26 EDT 2012


On 7/25/12 1:11 PM, "Jose Reyes" <jreyes at egmail.com> wrote:

>Here is the mention I found on the web and it said the error disappeared
>when the identityid was set, or maybe I am just misunderstanding what
>they said.
>
>http://shibboleth.1660669.n2.nabble.com/Session-Initiation-URLs-td2529820.
>html

Thanks. I think you just helped me figure it out. I'll have to think about
it, see if I can do something to handle that case better.

So, the deal is, you have a misconfigured SessionInitiator that is not
able to issue a request to an IdP. When you have a rule set up to require
a session for some resource, it intercepts the request with no session and
tries to dispatch control to the SessionInitiator implicitly. That's
supposed to do *something* and return a response to the client. In your
case, it doesn't do so, and the code falls through to the logic later on.
That logic knows that a session is required and doesn't find one, and so
it panics.

You'd never get that under normal use, but initially setting up things and
getting it slightly wrong, you might.

Basically, you didn't supply an entityID *or* a discovery mechanism. In
newer configs, you have a <SSO> element in place of all the
SessionInitiator stuff. You need to supply either an entityID or a
discoveryProtocol and URL. One of the two.

-- Scott



More information about the users mailing list