cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrei Shakirin <>
Subject RE: Information on using Interceptors in Service Side
Date Fri, 21 Feb 2014 10:31:27 GMT
Hi Santosh,

As I understood you are going to keep XWSS API on client and service sides, but would like
to reuse some CXF functionality for SAML processing on the service side (SAML validation,
holder of key check, etc).
So the aim is not to migrate service side to CXF completely, but just reuse some security
functionality from it.
Is my understanding correct?

I see three options here:

A)     Provide kind of CXF layer on the service side, that will receive messages from wire,
validate security and SAML and pass SOAP messages to XWSS API implementation. Vice versa for
outgoing chain: SOAP messages will be prepared in XWSS API service, CXF will be called with
prepared message, apply necessary security and send message. CXF layer will include complete
CXF interceptors chain and transport.

B)      Implement generic CXF gateway. CXF gateway will receive SOAP messages, validate them
and redirect to XWSS services. Vice versa for outgoing chain

C)      Try to reuse only specific CXF interceptors functionality directly from XWSS services.
Seems to be involved, because CXF security interceptors has some dependencies on CXF API and


From: Das, Santosh []
Sent: Donnerstag, 20. Februar 2014 10:48
To: Andrei Shakirin
Subject: FW: Information on using Interceptors in Service Side

Hi Andrei,

First of all many thanks for the help and support you have been providing.

This is in continuation to the discussion below regarding  CXF being used in server side.

As Renu already mentioned we have a custom implementation of soap services which is not JAX-WS
based , we are using XWSS API (a subproject of metro) and WSS4J directly for SAML processing.

Is there any direct API which CXF exposes which can be used in the service side to do ws-security
processing, saml validation , etc.

Basically we want to use the INInterceptors in the service side  and the engage the out interceptors
after generating the soap response. Typically the highlighted portion of the diagram.
We are not interested to publish the service either as we have our own implementation so cant
use the Enpoint api.

We are kind of stuck and wondering if CXF could be of any help Out of the box.

Please advise.


From: renu gupta []
Sent: Thursday, February 20, 2014 2:49 PM
To: Das, Santosh
Subject: Fwd: Information on using Interceptors in Service Side


---------- Forwarded message ----------
From: Andrei Shakirin <<>>
Date: Thu, Feb 20, 2014 at 1:52 PM
Subject: RE: Information on using Interceptors in Service Side
To: "<>" <<>>
Cc: renu gupta <<>>

If you will use ws-policy, it is enough to attach (embed) the policy into WSDL and configure
necessary security parameters like keystores and alias.
CXF will care about activation of necessary interceptors automatically.

I would recommend you to look in Glen Mazza blogs:

-          UsernameToken security using ws-policy

-          SAML using ws-policy:

Just make that step by step, you will have a filling how it works CXF.
If you like to understand internal ws-policy mechanisms in CXF, refer my blog:

I  hope it is helpful.


From: renu gupta [<>]
Sent: Donnerstag, 20. Februar 2014 06:09
To: Andrei Shakirin
Subject: Re: Information on using Interceptors in Service Side

The link which you have given talks about configuration at connector end but I want to know
how we can leverage the interceptors at services end. We are having our custom implementation
which takes care of invocation of service, publishing it and doing authentication and we uses
Metro for security feature, we want to use CXF instead of Metro and wss4j. So we don't want
to change the whole implementation of the Services we have now , but just want to hook in
CXF interceptors or API's if available to do the validation etc for the Security/ Addressing
and SAML case.


On Wed, Feb 19, 2014 at 9:50 PM, Andrei Shakirin <<>>

There are different ways to do that:

a)      using ws-policy - recommended way

b)      using features (WS-Addressing) and security actions configuration (security)

c)       configure interceptors in client/endpoint or bus level

d)      add interceptors dynamically for code

I would prefer alternative (a) for WSA and SAML (,
but final decision depends on your requirements.


From: renu gupta [<>]
Sent: Mittwoch, 19. Februar 2014 16:31
To:<>; Andrei Shakirin
Subject: Information on using Interceptors in Service Side

Hi ,

We are having our own custom service implementation which takes care of publishing the wsdl.
We were using the Metro for the security feature and wss4j for the SAML support. As we are
planning to leverage CXF. I have some doubts :
How can we use the interceptors to achieve the particular feature like WS Addressing , SAML
. Does CXF provides the API's directly which we can hook ?


  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message