Best practice MFA IdP3.3.1

[Cantor, Scott]

> I opted to try the webflow variable option, by setting a requestScope
> variable representing the user's selection at the interceptor.  The problem
> now is that there doesn't seem to be any access to the flowRequestContext
> when I attempt to 'Script' a policy rule in the attribute-filter.  Is that to be
> expected?  Here is an example of what I attempted in the attribute-filter:

Scripts are not view templates. There's nothing in the script but what we define and the "custom" hook you can inject your own objects into via that customObject property on the scripted bean.

> The error indicates that flowRequestContext is not found.  I have also tried
> 'requestContext' and 'flowScope', to no avail.

Those are populated by Spring Web Flow when it processes view templates.

I know how to walk from a flow context up into the servlet request. I don't know how easy it is to go the other way (it's easy to inject shibboleth.HttpServletRequest as a custom object ref, but I don't know how to get from there to flow gunk). That's basically why I don't advocate using flow variables.

-- Scott