Working example of using Duo AuthAPI/PreAuth call with Shibboleth IdP 5.1?

[Christopher Bongaarts]

On 5/15/2024 2:12 PM, Michael Grady via users wrote:
> Thanks, that got me to looking one more time at the secretKey 
> definition. And it is not defined twice, the problem was one small 
> typo I've looked at multiple times and not seen. And it was only the 
> IdP on start up that was warning about having those "old" 
> idp.duo.nonbrowser"  property names like:
>
>    idp.duo.nonbrowser.secretKey
>
> that caused me to decide to rename it to
>
>    idp.duo.oidc.nonbrowser.secretKey
>
> that introduced my error thru an unnoticed mistype. Should have just 
> left it named as I had it before, and ignored the "warnings"  :-)
>
> (I changed the property name back when I couldn't even get the flow to 
> initiate, before I got the PreAuth bean defined correctly.)

In a similar vein, we were confused for a while until we realized that 
the integrationKey property was renamed to clientId for the duo-oidc 
integration primary auth (but not for the non-browser one).

-- 
%%  Christopher A. Bongaarts   %%  cab at umn.edu          %%
%%  OIT - Identity Management  %%  http://umn.edu/~cab  %%
%%  University of Minnesota    %%  +1 (612) 625-1809    %%