Debugging authn/Duo IdP3.3.0

[O'Dowd, Josh]

Thanks I'll file the bug now.

Josh

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Wednesday, November 30, 2016 10:50 AM
To: Shib Users <users at shibboleth.net>
Subject: Re: Debugging authn/Duo IdP3.3.0

On 11/30/16, 12:39 PM, "users on behalf of O'Dowd, Josh" <users-bounces at shibboleth.net on behalf of Josh.O'Dowd at mso.umt.edu> wrote:

> I have a working Duo SP-Driven opt-in implementation for our IdP 
> 3.2.x, using the Unicon method, and I verified that our duo.properties are correct.

I'm not concerned with correctness, I don't think they're being correctly fed in. The only cases where the token signing method fails are a null username or one of the other Duo settings being null, and almost all of the obvious things would cause an NPE. I can't imagine how it could happen, which is why the logging is insufficient.

>  Would the supported principals in the "authn/Duo" cause this kind of issue?

No.

Even if the username were null, that would trigger a null pointer crash, that was a bug I patched after the release. (But this bug means it won't get logged adequately either.) That's the only plausible thing a deployer could get wrong.

Without a debugger there's nothing to go on. The exception has to be dumped. If you file the bug, I'll get around to patching the flow to log the exception, and then you can just pull in the patch to the flow definition easily enough.

-- Scott


--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net