OpenSAML user discussion

[Chad La Joie <>]

Paul, I have seen this error before when I mistakenly encoded the actual
file I was pulling my SAML from in one manner and then had a different
encoding specified in the XML prolog.  I think for me I did something
like encode with UTF-8 and then mistakenly put US-ASCII as the encoding.
 So, when I looked at the file and the hex it all looked fine but the
parser was thinking it was something totally different.

Paul Hethmon wrote:
> Ok, so I had this working a few weeks ago and can't figure out what has
> changed. I've got a snapshot of the opensaml2 libraries as of about
> March 23rd that builds (mostly, at least I didn't change much). I'm
> creating an AuthnRequest in one application and passing it to my Idp.
> When the Idp goes to decode the incoming HTTP form post, it is throwing
> the exception:
> 
>  
> 
>  org.xml.sax.SAXParseException: Content is not allowed in prolog.
> 
>  
> 
> So I went back to opensaml2 code and added another logging statement to
> actually print out the base64 decoded value from SAMLRequest. I don't
> see anything wrong with it, looking at the plain text or flipping the
> view to hex to make sure there are no "unprintable" characters. From my
> code, I'm calling HTTPPostDecoder.decode().
> 
>  
> 
> So the code snippet looks like:
> 
>  
> 
> HTTPPostDecoder decode = new HTTPPostDecoder();
> 
> decode.setParserPool( new ParserPool() );
> 
> decode.setRequest( request );
> 
> decode.decode();
> 
>  
> 
> Any thoughts on where to look next?
> 
>  
> 
> thanks,
> 
>  
> 
> Paul
> 
>  
> 
> Paul Hethmon
> 
> 
> 
> www.clareitysecurity.com
> 
> cell: 865.250.3517
> 
> work: 865.769.0456
> 
>  
> 

-- 
Chad La Joie             2052-C Harris Bldg
OIS-Middleware           202.687.0124