OpenSAML user discussion

[rangeli nepal <>]

I was under similar impression. But two things proved me wrong:

 

1. I could see the post data in firefox plugin.

2. If I take Inputstream of httpRequestservlet and convert to string I was able to get SAMLRequest-"....."

 

On Mon, May 17, 2010 at 6:13 PM, Brent Putman <> wrote:

On 5/17/10 5:43 PM, rangeli nepal wrote:
>  When Message is sent as httppost it does URL encoding. so if I do url
> decode  and then feed to base64 decoding It starts to work.
>

Based on the error msg from the decoder, the problem is that there is
literally no HTTP form parameter named either 'SAMLRequest' or
'SAMLResponse'.

The code that performs this check is pretty simple:

String encodedMessage = transport.getParameterValue("SAMLRequest");
if (DatatypeHelper.isEmpty(encodedMessage)) {
   encodedMessage = transport.getParameterValue("SAMLResponse");
}

if (DatatypeHelper.isEmpty(encodedMessage)) {
   log.error("Request did not contain either a SAMLRequest or "

           + "SAMLResponse paramter.  Invalid request for SAML 2 HTTP

              POST binding.");
   throw new MessageDecodingException("No SAML message present in
                    request");
}





So it sounds like something about the form as produced by the encoder
and posted to the decoder endpoint is screwed up.  What does the encoded
form look like?

This encoder/decoder code is known to work correctly, so something must
be off in the variable inputs that you are supplying on one side or the
other.