Selecting DuoOIDC 'config' based on user attribute in LDAP

[Cantor, Scott]

> The error we are getting is on that last 'duo' as you might expect. I'm trying
> to emulate what is in the MFA setup, but this one doesn't seem to want to
> handle the string as the 'next bean to call'.

Because that's not what it does. You're mixing two different contracts here.

The MFA contract is that it runs functions that produce state transitions to other flows, so the result of the functions are strings that name flows to run.

The Duo integration strategy contract is that the function returns *a Duo integration object/bean*. Not a string, not a bean name, the integration, period.

The return type of the functions are documented in each case and one is String and the other is the class type the Duo integrations have.

You can't split out your logic into multiple scripts, that won't make any sense here. You need one function that does whatever you need done and returns the designated Duo integration.

-- Scott