On 01-03-2018 5:04 AM, kevinmsrs wrote:
>
> Sorry for not including more information, but was able to resole the
> issue. I am currently running NAM 4.4.0.0-337 and NAAF 5.6-341. The
> Dynamic AAF class did not like the EVENTNAME property. I located a doc
> that stated that by default it looks for event name NAM on the NAAF
> server. I added my chains to this event and removed the property. Once
> this was saved, the Dynamic class was able to provide the second factors
> from the NAM event.


Interesting, i've used it successfully with dynamic auth class in a lab. Ah well, its resolved which is the important part.


--
Cheers,
Edward