axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "George Stanchev" <>
Subject RE: setting actor in the outgoing wsse headers
Date Fri, 15 Dec 2006 16:24:00 GMT
Hi Ruchith,
I have related question though. Say I create my own
wsse header and inject it in the outgoing message alongside
with the wsse header created by rampart.
Would an axis2 rampart just ignore my custom wsse
header on the service side? If say I have UsernameToken action in the 
InflowConfiguration, and provide 2 wsse headers -
one being the "default" and the other targeted towards
a particular actor - would the service-side rampart
just ignore the "actor"-ed one?


From: Ruchith Fernando []
Sent: Thu 12/14/2006 4:49 PM
Subject: Re: setting actor in the outgoing wsse headers

This is not supported in Rampart right now... Please file a JIRA.

The new configuration is based on WS-SecurityPolicy and I'm not sure
how we can achieve this with policy. Maybe we should ask the WS-SX
folks about it.


On 12/15/06, George Stanchev <> wrote:
> Hi,
> Is there a way to set the actor of the outgoing security headers using
> rampart?
> I would like to create 2 security headers on an outgoing message - one with
> the
> default actor and another targeting a specific actor name.
> I am not able to find a way to do it via the (now deprecated) configuration
> methods
> using OutflowConfiguration() objects.
> Any suggestions?
> Thanks
> George Stanchev
> **********************************************************************
>  This email and any files transmitted with it are confidential and
>  intended solely for the use of the individual or entity to whom they
>  are addressed. Any unauthorized review, use, disclosure or distribution is
> prohibited. If you are not the intended recipient, please contact the sender
> by reply e-mail and destroy all copies of the original message.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message