<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks for that. Will have a go at your suggestions even if it is not very promising.</div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Rachid</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Cantor, Scott <cantor.2@osu.edu><br>
<b>Sent:</b> 13 March 2024 14:09<br>
<b>To:</b> Shib Users <users@shibboleth.net><br>
<b>Cc:</b> Chalabi, Rachid <R.Chalabi@liverpool.ac.uk><br>
<b>Subject:</b> Re: DuoOIDC</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Caution: This email originated from outside of the University. Do not click links or open attachments unless you recognise the source of this email and know the content is safe. Check sender address, hover over URLs and don't open suspicious
email attachments.<br>
<br>
> Any ideas how to resolve?<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
-- Scott<br>
<br>
<br>
</div>
</span></font></div>
</body>
</html>