I don't believe so--the WSS4J interceptor approach predated our support
for WS-SecurityPolicy, at the time primarily concerned with supporting
the UsernameToken and X.509 WS-SecurityProfiles. BST support would have
come in later, after WS-SecPol support was already available. Of
course, if you know what you're doing you can manually create whatever
headers desired using your own interceptors
(http://www.jroller.com/gmazza/entry/jaxwshandlers_to_cxfinterceptors),
but otherwise my other suggestion of manually altering a local copy of
your WSDL to activate WS-SecurityPolicy and following Colm's earlier
advice
(http://cxf.547215.n5.nabble.com/x-509-security-token-td5150380.html#a5151124)
might be the best route for you.
Glen
On 02/06/2012 09:55 AM, blicket wrote:
I've actually been studying both your posts on interceptor and ws-pol
approach. Btw, great posts. Thanks you.
But, the interceptor example seem to only create
<wsse:SecurityTokenReference><ds:X509Data> elements. Is there a way to
insert the<wsse:BinarySecurityToken> by using the interceptor approach?
--
View this message in context:
http://cxf.547215.n5.nabble.com/x-509-security-token-tp5150380p5460253.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
