Debugging in CXF security (WSS4JInInterceptor/WSS4JOutInterceptor), returning exceptions through service

[martin <sk...@gmail.com>]

Hello. I am currently having a problem with WS security currently being
handled in a different message string.

I have a related question that is different enough to merit its own subject.

I keep getting a soap fault (presumably from the WSS4JInInterceptor in the
service, when calling with a client:
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Client</faultcode><faultstring>Security
processing failed.</faultstring></soap:Fault></soap:Body></soap:Envelope>

This is not all that informative.
Is there any way to configure the interceptors to relay whatever exception
caused them to fail back through the soap:Fault message so you can actually
see the parent exception in writing?

Is this already being logged somewhere else? I haven't been able to find it.

Come to think of it. I have yet to find a comprehensive list of
configuration options for these interceptors. Does anyone know where to find
one?

-Thank you
-Martin

--
View this message in context: http://cxf.547215.n5.nabble.com/Debugging-in-CXF-security-WSS4JInInterceptor-WSS4JOutInterceptor-returning-exceptions-through-service-tp5534346p5534346.html
Sent from the cxf-user mailing list archive at Nabble.com.

Re: Debugging in CXF security (WSS4JInInterceptor/WSS4JOutInterceptor), returning exceptions through service

[Glen Mazza <gm...@talend.com>]

Server-side messages back to the client by necessity need to be vague so 
Bad Guy doesn't get tips while he's trying to hack the service.  If 
you're running the web service provider in Tomcat (and probably most 
other Java containers), you should see much more informative exceptions 
in the servlet container log files.  If you have to, another option is 
to debug the web service provider in Eclipse 
(http://www.jroller.com/gmazza/entry/eclipse_debug_web_services) so you 
can see where the precise failure occurred and why.

HTH,
Glen


On 03/03/2012 03:53 PM, martin wrote:
> Hello. I am currently having a problem with WS security currently being
> handled in a different message string.
>
> I have a related question that is different enough to merit its own subject.
>
> I keep getting a soap fault (presumably from the WSS4JInInterceptor in the
> service, when calling with a client:
> <soap:Envelope
> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Client</faultcode><faultstring>Security
> processing failed.</faultstring></soap:Fault></soap:Body></soap:Envelope>
>
> This is not all that informative.
> Is there any way to configure the interceptors to relay whatever exception
> caused them to fail back through the soap:Fault message so you can actually
> see the parent exception in writing?
>
> Is this already being logged somewhere else? I haven't been able to find it.
>
> Come to think of it. I have yet to find a comprehensive list of
> configuration options for these interceptors. Does anyone know where to find
> one?
>
> -Thank you
> -Martin
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/Debugging-in-CXF-security-WSS4JInInterceptor-WSS4JOutInterceptor-returning-exceptions-through-service-tp5534346p5534346.html
> Sent from the cxf-user mailing list archive at Nabble.com.


-- 
Glen Mazza
Talend Community Coders
coders.talend.com
blog: www.jroller.com/gmazza