Skip to Content.
Sympa Menu

mace-opensaml-users - Re: [OpenSAML] HttpPostEncoder and HttpPostDecoder

Subject: OpenSAML user discussion

List archive

Re: [OpenSAML] HttpPostEncoder and HttpPostDecoder


Chronological Thread 
  • From: Brent Putman <>
  • To:
  • Subject: Re: [OpenSAML] HttpPostEncoder and HttpPostDecoder
  • Date: Tue, 18 May 2010 18:15:04 -0400


On 5/17/10 8:37 PM, rangeli nepal wrote:
> I was under similar impression. But two things proved me wrong:



Well, I don't know what else to suggest to you. The form that you are
posting to the decoder does not contain those HTTP form parameters in
the form expected. Either the form is corrupted or malformed in some
way, or else you are not actually posting what you think you are to the
actual decoder endpoint.

Could there be a redirect in there somewhere such that the form POST is
getting turned into a redirected GET, and losing the form data in the
process?

Or if you constructed your own template (you never answered my original
question) perhaps the form that's being submitted doesn't actually
contain the fields themselves (e.g. perhaps there are multiple <form>
elements and you are submitting the wrong one).



>
> 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-"....."
>


I'm assuming that's just a casual typo, but if the form literally has
"SAMLRequest-" (dash on the end) as the hidden <input> name, that is the
source of your problems, b/c that's not the correct field name, it's
"SAMLRequest".

Also, you should be able to validate this on the recipient side (where
the form is posted and the decoder runs) by simply calling:

HttpServletRequest#getParameter("SAMLRequest")

If that returns null, or empty, then that should prove that something is
wrong with the posted data.



Archive powered by MHonArc 2.6.16.

Top of Page