SSL: couldn't set callback!
When you installed a SP under Windows 2003 using the binary installation provided by https://wayf.internet2.edu/shibboleth/win32/, you could receive the following error:
2005-09-12 08:58:37 DEBUG shibtarget.SessionCache [1] sessionGet: trying to query an AA... 2005-09-12 08:58:37 DEBUG SAML.SAMLSOAPHTTPBinding.CURLPool [1] sessionGet: getting connection handle to https://one.shib.be:8443/shibboleth-idp/AA 2005-09-12 08:58:37 DEBUG SAML.SAMLSOAPHTTPBinding.CURLPool [1] sessionGet: nothing free in pool, returning new connection handle 2005-09-12 08:58:37 INFO SAML.SAMLSOAPHTTPBinding [1] sessionGet: sending SOAP message to https://one.shib.be:8443/shibboleth-idp/AA 2005-09-12 08:58:37 DEBUG SAML.libcurl [1] sessionGet: About to connect() to one.shib.be port 8444 2005-09-12 08:58:37 DEBUG SAML.libcurl [1] sessionGet: Trying 10.33.20.36... 2005-09-12 08:58:37 DEBUG SAML.libcurl [1] sessionGet: connected 2005-09-12 08:58:37 DEBUG SAML.libcurl [1] sessionGet: Connected to one.shib.be (10.33.20.36) port 8443 2005-09-12 08:58:38 DEBUG SAML.libcurl [1] sessionGet: SSL: couldn't set callback! 2005-09-12 08:58:38 DEBUG SAML.libcurl [1] sessionGet: Closing connection #0 2005-09-12 08:58:38 <strong>ERROR SAML.SAMLSOAPHTTPBinding [1] sessionGet: failed while contacting SAML responder: SSL: couldn't set callback!</strong> 2005-09-12 08:58:38 ERROR shibtarget.SessionCache [1] sessionGet: caught SAML exception during SAML attribute query: SOAPHTTPBindingProvider::send()<br/> failed while contacting SAML responder: SSL: couldn't set callback! 2005-09-12 08:58:38 ERROR shibtarget.SessionCache [1] sessionGet: no response obtained 2005-09-12 08:58:38 DEBUG shibtarget.Listener [2] sessionGet: checking for session: _5ad0a14b7d547a262e824aea406d607d@10.33.20.36 2005-09-12 08:58:38 DEBUG shibtarget.Listener [2] sessionGet: application: default
This error is causes by a mismatch of libraries. You have to make sure that the version of OpenSSL matches the one used to build the binary package.
For example, we experienced the problem when we installed the binary distribution of OpenSSL v0.9.8. The dll,
c:\WINDOWS\system32\ssleay32.dll
was the one that caused the problem. When we used OpenSSL v0.9.7e the problem with the library was solved.