errors after upgrade to 3.4.6

[Cantor, Scott]

On 11/8/19, 12:00 PM, "users on behalf of Jim Fox" <users-bounces at shibboleth.net on behalf of fox at washington.edu> wrote:

> I'll make an effort to read release notes more carefully.  We don't use 
> external flow, so I kinda skipped that part.

I didn't make the decision lightly, but the alternatives to fix it were very ugly and a lot less robust.

As for what you're doing, unfortunately there really isn't a supportable way to do it. Duplicating the non-API class(es) you're using is really the only course you can take that won't put you at risk of the same issue in the future, though it will always be noted if we have to change something like that.

-- Scott