I received a similar error while deploying Shibboleth, reading
attributes from an openLDAP directory:

 ERROR shibd.Listener [29] sessionNew: caught exception while creating
session: SOAPHTTPBindingProvider::send() failed while contacting SAML
responder: error:1408F06B:SSL routines:SSL3_GET_RECORD:bad decompression

The cause of the error appears to be a '$' character in an LDAP
attribute postalAddress.

 

The attribute postalAddress uses $ as a line delimiter:

 

See
http://www.red-hat.com/docs/manuals/dir-server/deploy/7.1/schema.html
for example:


"The postalAddress attribute expects an attribute value in the form of a
multi-line string that uses dollar signs ($) as line delimiters. A
properly formatted directory entry appears as follows: 
postalAddress: 1206 Directory Drive$Pleasant View, MN$34200"



However inclusion of the '$' character causes a bad decompression error
(error doesn't occur when it is removed).

 

Neil Witheridge.

 

 

---  in response to:

Hi,

 

I get the following error message and I don't no the reason for that.

 

2007-06-12 12:21:56 INFO SAML.SAMLSOAPHTTPBinding [45] sessionGet:
sending

SOAP message to

https://kn.identity-provider.de:8443/shibboleth-idp/AA2007-06-12
12:21:56

ERROR SAML.SAMLSOAPHTTPBinding [45] sessionGet: failed while contacting

SAML responder: error:1408F06B:SSL routines:SSL3_GET_RECORD:bad

decompression

2007-06-12 12:21:56 ERROR shibtarget.SessionCache [45] sessionGet:
caught

SAML exception during SAML attribute query:

SOAPHTTPBindingProvider::send() failed while contacting SAML responder:

error:1408F06B:SSL routines:SSL3_GET_RECORD:bad decompression

2007-06-12 12:21:56 ERROR shibtarget.SessionCache [45] sessionGet: no

response obtained

 

I suppose there is a ssl problem regards with compatibility or it due to
a build or library compatibility issue?!? How I could solve my problem? 

 

Furthermore I don't the meaning of this error message:

 

"...error:1408F06B:SSL routines:SSL3_GET_RECORD:bad

decompression..."

 

 

Hope someone can help me.

 

Cheers,

tt

 

Reply via email to