DuoOIDC

[Cantor, Scott]

> Any ideas how to resolve?

Something's very wrong, that's basically not possible. Those aren't easy to solve, other than to say there's absolutely no way that's the running system. There's something more going on, such as the module command reporting against a different system state than the running IdP reporting that error.

The plugin self-registers all of its machinery, including the thing it can't find, so it simply can't be there no matter what it's reporting.

As a starting point, I would suggest you look at the jar set that's inside the deployed warfile, and I would also suggest you look at the container log, which sometimes catches problems that happen much earlier than the IdP logging can report.

To the first point, the command line tools report against the unpacked and scattered sets of libraries, whereas the runtime only sees what's in the war. Checking the status page to see what it says about the modules and plugins might help.

-- Scott