Upgrade to IdP 3.3 flow definitions

[unicon]

Upgrade to IdP 3.3 flow definitions

[jtgasper3]

@tsschmidt Thanks for the report.

Are you saying the cas-shib-authn3 needs to be upgraded to support 3.3.0 or the Duo flow needs to be upgraded. Which Duo module are you using Duo's, Unicon's, or the new "native" support?

[tsschmidt]

cas-shib-authn3 needs to be upgraded to support 3.3.0. It looks like the
flow has been modified slightly to pull user name for the new MFA flow that
allows for Duo or other 2FA providers. As it is now, the Shibcas flow is
not compatible with the new MFA flow in the IdP.

On Tue, Nov 15, 2016 at 10:12 AM John Gasper [email protected]
wrote:

@tsschmidt https://github.com/tsschmidt Thanks for the report.

Are you saying the cas-shib-authn3 needs to be upgraded to support 3.3.0
or the Duo flow needs to be upgraded. Which Duo module are you using Duo's,
Unicon's, or the new "native" support?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#18 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AS0kvXEKP9bcqXVSbjUDamDOgGI1iqyEks5q-fYjgaJpZM4KysOm
.

[mmoayyed]

This probably merits a 3.3 version of the plugin as well, plus a separate branch to move the current master into.

[jwandrews4]

What modifications need to be made to the login flow of Shibcas to work with 3.3 flows specifically Duo?

[jtgasper3]

Can you be more specific about what you are desiring to do? Most adopters manage/control Duo from the CAS side.

[jtgasper3]

It should be said that the latest Shib-cas-authn3 release support IdP 3.3.0/3.3.1. This issue should have been closed at that time.

@jwandrews4 Can I ask that you create a new issue for your Duo questions?