debug messages on shibtest, testing shib IdPv3 upgrade on our test IdP

[Michael Weyandt]

Hey all, the last post was derailed because of a misunderstanding so any help is appreciated. 

I’ve been in the process of upgrading my test IdP with the entityID of https://auth-test.uakron.edu/idp/shibboleth <https://auth-test.uakron.edu/idp/shibboleth> and get the 
following messages when on shibtest. I do not have any problems with my SPs but I figured I’d ask since I’m having an issue
with an outside SP (not using shib).

This is NOT my production IdP and is NOT in InCommon. This is NOT related to the IdP https://id.uakron.edu/idp/shibboleth <https://id.uakron.edu/idp/shibboleth> in any way. 
DEBUG XMLTooling.CredentialCriteria [1637]: key algorithm didn't match ('AES' != 'RSA')
DEBUG XMLTooling.KeyInfoResolver.Inline [1637]: resolving ds:X509Certificate
DEBUG XMLTooling.KeyInfoResolver.Inline [1637]: resolved 1 certificate(s)
DEBUG XMLTooling.CredentialCriteria [1637]: credential name(s) didn't overlap
DEBUG XMLTooling.CredentialCriteria [1637]: keys didn't match
and
DEBUG XMLTooling.KeyInfoResolver.Inline [1634]: resolving ds:X509Certificate
DEBUG XMLTooling.KeyInfoResolver.Inline [1634]: resolved 1 certificate(s)
DEBUG XMLTooling.KeyInfoResolver.Inline [1634]: resolved 0 CRL(s)
DEBUG XMLTooling.TrustEngine.ExplicitKey [1634]: attempting to match credentials from peer with end-entity certificate
DEBUG XMLTooling.TrustEngine.ExplicitKey [1634]: no keys within this peer's key information matched the given end-entity certificate
DEBUG XMLTooling.TrustEngine.PKIX [1634]: performing certificate path validation...
DEBUG XMLTooling.TrustEngine.PKIX [1634]: failed to validate certificate chain using supplied PKIX information
ERROR XMLTooling.SOAPTransport.CURL [1634]: supplied TrustEngine failed to validate SSL/TLS server certificate
any comments/suggestions on this would be great.
Thanks,
Mike Weyandt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160630/54b4258a/attachment-0001.html>