Clearing consent

[Cantor, Scott]

On 6/30/15, 11:50 AM, "dev on behalf of Tom Zeller" <dev-bounces at shibboleth.net on behalf of tzeller at dragonacea.biz> wrote:
>
>> We could do a subflow, but I think orchestrating that in the middle of the login process would be ugly and pretty invasive, much like all my attempts at making the current query parameter work.
>
>Could you say more please ? See below ...

Well, I don't like the idea in general of creating "special" parameters that have be created in one area and then consumed by an unrelated area without thinking about how we want the actual interface between those components working.

The problem I'm having with query strings is that webflow for me is generating intermediate redirects that drop the query string, so we would have to have something picking up query parameters to preserve them or propagate them in a lot of places.

Kaspar was apparently getting the query to work, but when I try it, I get an intermediate redirect.

For example, the basic flow of a request that runs a separate login flow from the login page via a button seems like it should be:

-> SAML SSO request
<- render login view
-> POST login form to run external flow
<- redirect to external URL

What I get is:

-> SAML SSO request
<- intermediate redirect to same URL with no SAML params and updated execution key
-> request that URL
<- render login view
-> POST login form to run external flow
<- intermediate redirect to same URL with no extra params and updated execution key
-> request that URL
<- redirect to external URL

>Why do you distinguish between a flow and subflow ... what's the
>difference in this case ?

A subflow is a programmatic API for a webflow to invoke a new function by passing control to it, generally with any "state" passed in the context tree.

A flow is a top-level function the client can request generally with any state passed in on the URL or by form.

To do this with a subflow, we would have to embed a call to the subflow inside every web flow that wanted to use it, or at least create a general state transition that would run that subflow and then pick back up where it left off. That might work, I'd have to think about it, but it seems awkward to have to signal two events to SWF, one to get the subflow to run and a second to tell it what to do after.

A new flow would basically just be a redirect and then back to the flowExecutionUrl to resume with a particular transition. That's pretty easy to script, though without Javascript I guess it would be tough.

-- Scott