Odd Duo Exception after upgrading to 3.3.0 from 3.2.0

[Michael A Grady]

> On Mar 16, 2017, at 6:13 PM, Strickland, David R <dstrickland at austin.utexas.edu> wrote:
> 
> Christopher,
> 
> Thanks, this is really helpful. We were still scratching our heads about how
> you got this working based on your earlier email.
> 
> Since you're going with native Duo support, are there any notable
> differences between the native Duo flow and the Unicon plugin? I can see the
> advantage of not having to fiddle with a third party plugin, but I couldn't
> find a compare/contrast of the two methods anywhere.
> 
> Thanks!
> David
> 
> David Strickland
> Lead Software Engineer
> Identity and Access Management
> The University of Texas at Austin

I'd be interested to know what the reasons are why you would rather get the Unicon plugin working with 3.3.x than switch to the now built-in support for such with the combo of the MFA and Duo flows? There are no features in our Unicon plugin that at least I'd had occasion to leverage for deployments that I wasn't also able to configure with the new MFA/Duo support in IdP 3.3.x. Is it simply the "learning curve" of how to configure it the "new way" versus the "old way"? Or is there something you could do with the Unicon plugin that you don't think you can do with the new MFA/Duo support?


> 
> -----Original Message-----
> From: users [mailto:users-bounces at shibboleth.net <mailto:users-bounces at shibboleth.net>] On Behalf Of Christopher
> Bongaarts
> Sent: Thursday, March 16, 2017 5:46 PM
> To: users at shibboleth.net <mailto:users at shibboleth.net>
> Subject: Re: Odd Duo Exception after upgrading to 3.3.0 from 3.2.0
> 
> So it turns out I was mistaken about this.  Duo was not actually working in
> this case, it just allowed the IdP to load successfully.  Trying to invoke a
> Duo-protected login lead to an error, I think (something like the flow
> couldn't be found). Ultimately after fiddling with it long enough, we
> managed to get things working again by tweaking the web.xml file and the
> layout of the plugin jar.
> 
> This is essentially what we ended up with.  If I was planning to continue
> using the Unicon plugin instead of the 3.3 native Duo/MFA flow support,
> there is probably some cleanup that could be done. This is mostly intended
> as a hint in case other folks are in the same situation.
> 

--
Michael A. Grady
IAM Architect, Unicon, Inc.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170316/993b9041/attachment-0001.html>