Ex: Re: attribute access in duo velocity template

[Paul B. Henson]

> From: Cantor, Scott
> Sent: Tuesday, April 6, 2021 6:11 PM
> 
> But there are no attributes by this point, and if there are, you populated them
> and where you put them is not something defined by us. I tend to encourage
> stuffing them underneath the AuthenticationContext if you produce them
> during authentication.

I ended up adding

	authCtx.setHintedName("duo_init");

to the MFA transition script and

	#set ($MfaHint = $authenticationContext.getHintedName())

to the duo velocity template and was able to get it to do what I needed. I'm not sure if that was the cleanest way to do it, but it sure ended up being simple, and based on the documentation:

	Set a non-normative hint provided by the request about the user's identity

	Get a non-normative hint provided by the request about the user's identity.
	This is NOT a trustworthy value, but may be used to optimize the user experience.

It seemed apropos :).

Thanks for the hint...