Odd Duo Exception after upgrading to 3.3.0 from 3.2.0

[Cantor, Scott]

On 3/27/17, 6:54 PM, "users on behalf of Christopher Bongaarts" <users-bounces at shibboleth.net on behalf of cab at umn.edu> wrote:

> There was one more adjustment required in order to make single sign-on work for Duo.  Had to manually add one line to the end
> of the shibboleth.AvailableAuthenticationFlows list in  conf/authn/general-authn.xml:

That's going to be true of all versions, which seems to be a common thread here. I simply have no explanation for what would be different here, this could *not* work in 3.2 either. Not without that bean. All flows have to have those beans defined to operate.

> I'm not sure how the rest of the authn stuff managed to work without 
> this - maybe it's part of the "magic" of the initial-authn stuff, or the 
> programmatic AFD registration sorta-kinda worked for some things in 3.3.0.

initial-authn remains supported (if discouraged) in 3.3, nothing's changed there. Modulo a bug with the UI extensions, now fixed. It wouldn't have any impact on registering the flow descriptor (or not doing that).

-- Scott