Odd Duo Exception after upgrading to 3.3.0 from 3.2.0

[Cantor, Scott]

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

>    We had a similar error that we fixed by updating our customized web.xml file from 3.2.1 with the new version in 3.3.0
> and reapplying our changes.  We did *not* have to add the classpath settings that the Duo module doc installation
> recommends; 3.3.0 already has those paths included.

I don't know why that would be exactly, but there were/are specific things the Unicon flow was doing that certainly might have stopped working, including the way it was trying to programmatically  define the flow to the IdP, which isn't supported.

I'm not aware of any web.xml changes that should matter.

-- Scott