mace-opensaml-users - Re: SAMLSoapBinding.response with exception
Subject: OpenSAML user discussion
List archive
- From: "Mike Ferraro" <>
- To: "Scott Cantor" <>, <>
- Subject: Re: SAMLSoapBinding.response with exception
- Date: Mon, 20 Sep 2004 15:42:21 -0400
> > // respond with SAMLSoapBinding.respond()
> > binding.respond(resp, samlResp, se);
>
> Note that the third parameter is for triggering a SOAP fault, not for
> passing back an error Status in a Response. Basically, you do one or the
> other. Why there aren't just separate methods, I haven't a clue at the
> moment. I don't know what I was thinking at the time.
Gotcha. I should have realized that from the source code. It works fine
now that I don't pass an exception, but I have to modify the status code and
message in my SAMLResponse by pulling out the DOM and manually changing the
status values. Is there another way to specify a response status other than
samlp:Success, or is manually changing it the only way?
>
> > [ERROR] [17 Sep 2004 12:33:05,609] send() received an invalid
> > content type
> > in the response (text/html), with the following content:
>
> Well, that means something must be failing and not catching the error, and
> it's probably sending back an HTML page with the error, if I had to guess.
I
> caught various errors as a failsafe, and triggered a servlet error
response
> in those cases.
>
> I'd suggest capturing the input and using a command line tool like curl to
> simulate the POST if you're not sure.
It looks like the error is coming from within the respond() method when it
tries to process the SAMLException. That's where the ServletException seems
to get thrown from. I didn't track down the error fully because I'm not
using that parameter in the respond() method anymore, but just figured that
I'd give a heads-up in case it's something actually wrong with that portion
of the code. Sorry I'm not more helpfull.
- OpenSAML on Websphere/Solaris, Sanga Viswanathan, 09/13/2004
- RE: OpenSAML on Websphere/Solaris, Scott Cantor, 09/13/2004
- RE: OpenSAML on Websphere/Solaris, Sanga Viswanathan, 09/13/2004
- RE: OpenSAML on Websphere/Solaris, Scott Cantor, 09/13/2004
- SAMLSoapBinding.response with exception, Mike Ferraro, 09/17/2004
- RE: SAMLSoapBinding.response with exception, Scott Cantor, 09/17/2004
- Re: SAMLSoapBinding.response with exception, Mike Ferraro, 09/20/2004
- RE: SAMLSoapBinding.response with exception, Scott Cantor, 09/20/2004
- Re: SAMLSoapBinding.response with exception, Mike Ferraro, 09/20/2004
- RE: SAMLSoapBinding.response with exception, Scott Cantor, 09/20/2004
- Re: SAMLSoapBinding.response with exception, Mike Ferraro, 09/20/2004
- RE: SAMLSoapBinding.response with exception, Scott Cantor, 09/17/2004
- SAMLSoapBinding.response with exception, Mike Ferraro, 09/17/2004
- org.xml.sax.SAXParseException: Content is not allowed in prolog, Jason Pedone, 09/20/2004
- Re: org.xml.sax.SAXParseException: Content is not allowed in prolog, Paul Devine, 09/20/2004
- RE: org.xml.sax.SAXParseException: Content is not allowed in prolog, Scott Cantor, 09/20/2004
- RE: OpenSAML on Websphere/Solaris, Scott Cantor, 09/13/2004
- RE: OpenSAML on Websphere/Solaris, Sanga Viswanathan, 09/13/2004
- RE: OpenSAML on Websphere/Solaris, Scott Cantor, 09/13/2004
Archive powered by MHonArc 2.6.16.