Mapping an x509 cert to one of multiple possible accounts

Tony Plovich aplovich at anl.gov
Thu Nov 9 13:12:28 EST 2017


> Which is to say, the MFA flow lets you capture and dispatch on any event signaled by the Password flow/form, and as long as that doesn't transit another view it should contain the parameters and allow your script rule to save them off in the same state map as the extended flow feature does.
Thanks, this was the nudge I needed.  Figured out I could access the 
form parameters from the shibboleth.HttpServletRequest object.

Tony Plovich (aplovich at anl.gov)
Business Information Systems (BIS)
Argonne National Laboratory

On 11/09/2017 10:08 AM, Cantor, Scott wrote:
> On 11/9/17, 11:04 AM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
>
>> If it isn't already possible, but I would think it is.
> Which is to say, the MFA flow lets you capture and dispatch on any event signaled by the Password flow/form, and as long as that doesn't transit another view it should contain the parameters and allow your script rule to save them off in the same state map as the extended flow feature does.
>
> There will be more general scratch space in 3.4 to save off data, but for authentication cases, the AuthenticationContext has that map for use.
>
> -- Scott
>
>



More information about the users mailing list