shibd.log is blank when testing IdP at sp.testshib.org

[Nate Klingenstein]

The apparently blank shibd.log is generally just the disk filling up from too many testers causing the shell script that prints it to the webpage to choke.  I don't have time to investigate immediately, but Kevin may.  We really need to upsize that VM at this point.

The error indicates that your IdP is signing assertions with a key that is different than the one in your metadata as registered at TestShib.  That could be stale metadata at TestShib, two copies of metadata at TestShib, each of which is different, the wrong key in your IdP configuration, or some variant on that.

On Jun 11, 2015, at 7:50 PM, Khawer Masood <shehzada at gwu.edu<mailto:shehzada at gwu.edu>> wrote:

Upon testing an IdP at https://sp.testshib.org/, the exception below appears, but shibd.log is blank. Any ideas on what might be happening? The authentication succeeds, but not errors are logged on IdP side. Relevant versions are: Shib v 3.1.1, OEL 6.6, Jetty 9.2, Oracle JDK 1.8.0_45.

Thanks,

KM

Exception is:

I'm sorry this didn't work out just yet.

opensaml::FatalProfileException at (https://sp.testshib.org/Shibboleth.sso/SAML2/POST)

Unable to establish security of incoming assertion.

--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net<mailto:users-unsubscribe at shibboleth.net>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150612/0720104b/attachment.html>