Troubleshooting the "Unable to decode" (IdP 3.3)

[Brent Putman]

On 8/30/17 11:13 AM, O'Dowd, Josh wrote:
>
>  
>
> ERROR [org.opensaml.profile.action.impl.DecodeMessage:73] - Profile
> Action DecodeMessage: Unable to decode
>
> incoming
> requestorg.opensaml.messaging.decoder.MessageDecodingException: Error
> unmarshalling message from input stream
>
>         at
> org.opensaml.messaging.decoder.servlet.BaseHttpServletRequestXMLMessageDecoder.unmarshallMessage(BaseHttpServletRequestXML
>
> MessageDecoder.java:158)
>
> Caused by:
> net.shibboleth.utilities.java.support.xml.XMLParserException: Unable
> to read data from input stream
>
>         at
> net.shibboleth.utilities.java.support.xml.BasicParserPool.parse(BasicParserPool.java:251)
>
> Caused by: java.util.zip.ZipException: invalid bit length repeat
>
>         at
> java.util.zip.InflaterInputStream.read(InflaterInputStream.java:164)
>
>  
>


That root cause error (ZipException) is almost certainly an issue with
the lack of DEFLATE on the message, which is what I speculated.



>  
>
> The GET component of HTTPRequest from the httpd-access.log which
> caused the above error:
>

I'll spend a few minutes investigating this and let you know what I find.



>  
>
> The SAMLRequest parameter value from the above HTTPRequest which
> caused the above error.  This was decoded using the
> http://rnd.feide.no/ SAML2 debugger tool:
>


That almost certainly confirms the DEFLATE issue, since the FEIDE tool
is lax about that.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170830/839f593b/attachment.html>