Shibboleth 3 SAML Response Debugging

[McKean, Brandon Scott - mckeanbs]

Thanks for the tip Scott.
So I used this method to check the signing key and certificate:
openssl x509 -noout -modulus -in idp-signing.crt | openssl md5
openssl rsa -noout -modulus -in idp-signing.key | openssl md5
Hashes match in that case. Also, idp-signing.crt's contents match up in
idp-metadata.xml
idp-signing.crt and idp-signing.key were migrated from idp.crt and
idp.key, respectively, from our V2 installation. idp-metadata.xml was
also copied from the V2 environment.
I hope I'm on the right track with this? 
Thanks,

-- 
Brandon McKean
IT / Systems
Linux Administrator
(540)568-4235
On Wed, 2015-07-15 at 18:11 +0000, Cantor, Scott wrote:
> On 7/15/15, 2:04 PM, "users on behalf of McKean, Brandon Scott -
> mckeanbs" <users-bounces at shibboleth.net on behalf of mckeanbs at jmu.edu
> > wrote:
> 
> > The most meaningful data I could find stated the error was:
> > Security of SAML 1.x SSO POST response not established, this was
> > from the SP.
> 
> Well, that's a signature issue, nothing to do with endpoints.
> 
> > I have Shibboleth running with debug logging on, and quite a bit
> > seems to happen up to the point of failure, though I'm not sure
> > what I should be looking for to troubleshoot.
> 
> Your signing key's wrong or your metadata is, there's nothing else
> really to debug, but the IdP log can dump the SAML, as can the SP
> log.
> 
> -- Scott
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150715/68eb67b8/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5673 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/users/attachments/20150715/68eb67b8/attachment-0001.bin>