Consent Wording

[Cantor, Scott]

On 11/20/14, 12:41 AM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:


>
>That's what I was trying to say, the outcome here is not supposed to be 
>the user closing the browser, they should be able to abort the login and 
>end up some place the deployer can control and it can say whatever they'd 
>like it to say. It shouldn't trap the user on the consent page or force 
>them to shut down.

One major reason why is server resources. The web flow engine tracks 
conversation state in the Java session, and only by completing a flow to 
an end-state will it free the flow up before the Java session times out.

So we don't ever want anything to lead somebody to naturally just abandon 
a flow if we can help it. It's mostly unavoidable when people can't login 
successfully, but here we would want to at least make sure the form 
options always complete the request one way or the other and free up the 
state.

-- Scott