Shibboleth Developers

[Scott Cantor <>]

This belongs on the -users list, please direct any follow up there.

On Sep 4, 2010, at 8:56 AM, Pankaj <> wrote:

shibd.log is

2010-09-04 12:42:46 ERROR Shibboleth.AttributeResolver.Query [10]: exception during SAML query to https://idp.gluu.org:8011/idp/profile/SAML2/SOAP/AttributeQuery: CURLSOAPTransport failed while contacting SOAP endpoint (https://idp.gluu.org:8011/idp/profile/SAML2/SOAP/AttributeQuery): Unknown cipher in list: ALL:!aNULL:!LOW:!EXPORT:!SSLv2
2010-09-04 12:42:46 ERROR Shibboleth.AttributeResolver.Query [10]: unable to obtain a SAML response from attribute authority
2010-09-04 12:42:46 INFO Shibboleth.SessionCache [10]: new session created: ID (_9fc74d8d01536298d4f2db6a869605c7) IdP (https://idp.gluu.org/idp/shibboleth) Protocol(urn:oasis:names:tc:SAML:2.0:protocol) Address (122.163.66.109)
2010-09-04 12:45:06 ERROR Shibboleth.SSO.SAML2 [13]: Unable to resolve any key decryption keys.

Those are two unrelated errors on two unrelated transactions. The first I've never seen and you should provide all necessary version information about the build. It also implies the IdP is improperly advertising a query endpoint and causing wasted queries when no attributes are pushed.

The second means what it says, you have the wrong key in your metadata or locally and they don't match.

-- Scott