getPrincipals() typing

[Cantor, Scott]

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

> Not worried about accidents.  It is exposed-ish to the client, which is an accident
> waiting to happen.  That's where I join the flow along with users and back buttons.

It is not possible by accident at all, that's what I'm telling you. It doesn't happen unless you do it deliberately, and that's why the little input variable guard is there. It can't happen with the back button at all.

Just because the subflow can be invoked at a URL, it doesn't mean you end up at that URL when another flow runs that subflow internally. The URL is not changed to match that of the subflow, it stays set to the original flow's path. Yes, it's weird, until you get what it's doing.

The stage it's in and what subflow it's executing is all part of the state of the execution stored inside the SWF objects in the session.

So, no, you never access /idp/authn/Password as any kind of redirect, and hitting the back button won't take you there.

A user could access it, yes, and get an error, but they would never know to do it, and if they do nothing breaks, they just see an error that can be changed into whatever people want it to be.

> People are just going to treat the 3.3 authentication stuff as a black box, but none of
> this is really a black box.

There are very powerful things you can do while totally ignoring the internals, but writing flows is not one of them.

-- Scott