Ex: Re: finger pointing

[Paul B. Henson]

> From: users Cantor, Scott
> Sent: Friday, May 7, 2021 12:58 PM
> 
> No, the CAS flow is a redirect.

Hmm, potentially so is the SAML flow. So if somebody used the redirect binding for SAML my message would also not be displayed.

> You can customize the template you're talking about though of course.

You mean the saving session one? I could, but then it still wouldn't work if the idp wasn't using that feature, it would stall on the previous displayed screen.

< In fact I just realized my copy is still so old that I never
> adjusted it to rely on the system resource that carries the actual logic of the
> page

The storage one? I didn't use it before we deployed idp 4,  so it should be up-to-date on mine.

So currently as defined in system/flows/cas/login/login-flow.xml, the second to last state is:

    <decision-state id="ReturnToService">
        <if test="flowScope.serviceTicketRequest.method == 'POST'"
            then="PostBackToService"
            else="RedirectToService" />
    </decision-state>

For the POST case, there is a template rendered:

    <end-state id="PostBackToService" view="cas/postBack">

So the file system/views/cas/postBack.vm could be updated to include the same additional head/body content as rendered in the SAML POST case:

	views/templates/add-html-head-content.vm
	views/templates/add-html-body-content.vm

Would this be acceptable if I opened a ticket and pull request? However, does CAS ever actually do a post? Hmm, based on the specification the ability to request POST rather than a redirect is an optional feature added in version 3.0. I don't think I've ever seen a client do that. So while this would be good to add for the sake of completeness, I don't think it would actually do anything in the wild.

In the other case, there is no additional template displayed, it just immediately issues a redirect:

    <end-state id="RedirectToService" view="externalRedirect:#{flowScope.redirectUrl}">

What you think of adding an additional state, say perhaps RedirectToServiceNotify, which simply renders a template and immediately jumps to the existing RedirectToService? Could that be done directly in login-flow.xml, or would that need to be a new sub flow with other files/pieces floating around?

Then again for the sake of completeness, something similar for the SAML redirect case?

Thanks...