The StartBodyInterceptor might help:
https://github.com/apache/cxf/blob/master/rt/bindings/soap/src/main/java/org/apache/cxf/binding/soap/interceptor/StartBodyInterceptor.java
On Wed, Aug 9, 2017 at 4:18 PM, Isuranga Perera
wrote:
> I'm using CXF security policy enforcement without CXF transpor
I'm using CXF security policy enforcement without CXF transport. I convert
the policy file to a Neethi object and used PolicyInInterceptor to get
required interceptors to process the security header. I managed to verify
security successfully with stream security enabled.
But now I can't extract th
What exactly are you trying to do with the streaming security interceptors?
Colm.
On Tue, Aug 8, 2017 at 4:53 PM, Isuranga Perera
wrote:
> Hi Colm
>
> Thanks for the immediate response. I managed to add stream security
> interceptors and process security headers. But I found out that they chang
Hi Colm
Thanks for the immediate response. I managed to add stream security
interceptors and process security headers. But I found out that they change
message.getContent(StreamReader.class). So can you suggest a way to extract
SOAPBody from the content?
Best Regards
On Tue, Aug 8, 2017 at 7:52
It's not something that you should need to configure. It's used by the
streaming WS-Security code inside WSS4J to retrieve security "events" from
either inbound or outbound processing. For example, on an inbound request
you might decrypt a key which you might then need to use to secure the
message
Hi
I'm using CXF security processing with stream security. There I was able to
find
List requestSecurityEvents =
(List)
soapMessage.getExchange().get(SecurityEvent.class.getName() + ".out");
Appreciate if you can explain how to set this SecurityEvent extension
manually and the p
