getPrincipals() typing

Cantor, Scott cantor.2 at osu.edu
Wed Aug 31 20:25:23 EDT 2016


On 8/31/16, 8:11 PM, "dev on behalf of Klingenstein, Nate" <dev-bounces at shibboleth.net on behalf of nklingenstein at calstate.edu> wrote:

> I shouldn't, but I can't prevent it.  This is why I asked about entrance points and why
> those seemingly meaningless checks are meaningful.  I'm very thankful that things bomb out
> by default, actually.

I don't know how you could do that by accident. Nothing in the IdP would ever cause that to happen.

If you're trying to debug it by running those flows by themselves, that's not going to work. The contracts require that the context tree is set up in the right way or the actions will simply fail.

Also, if you're trying to debug this outside of Eclipse using the testbed we have, then that would also be a big mistake. I work inside that exclusively.

> If you're not a developer -- and I appreciate the inherent irony of me writing that here
> -- that is one heck of a reference manual.  The example they have makes some of the
> assumptions that I did, for instance.  It's all "typically", but it's not really bounded
> in any ways.

I'm not saying you can understand what I did by reading it, but I am saying you can't understand what I did without reading it.

You have to start with how SWF works, and then it's much easier to explain what we did that isn't normal. You have to know normal to get to what isn't.

> But it could be persisted entirely by the client, and that's an assumption that I need to
> retain.

You shouldn't need to worry about that. The client storage options behave exactly like the server ones from the point of view of the IdP, and the data is all loaded and saved for you, and if you're working with the front-channel the differences don't really matter.

-- Scott




More information about the dev mailing list