You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Sriram Vaidyanathan <Sr...@Copart.Com> on 2007/01/18 02:06:30 UTC
Configuration in Rampart 1.1
Hi,
I am currently trying to upgrade to Rampart 1.1 from Rampart 1.0 and using Rampart 1.0 we could talk to multiple services from a single client by programmatically configuring the parameters using the OutflowConfiguration class.
>From previous posts in the forum it looks like these are deprecated with the 1.1 releases. Is there an alternative way we can dynamically configure the parameters in 1.1? Any help on this would be appreciated.
Thanks and Regards
Sriram Vaidyanathan
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Configuration in Rampart 1.1
Posted by Ruchith Fernando <ru...@gmail.com>.
Hi Sriram,
Note that you must use Rampart policy[1] in configuring rampart along
with the standard WS-SecurityPolicy.
The WS-SecPolicy stuff are not really straight forward. Therefore I
believe we will be maintaining the rampart-1.0 configuration for a few
more versions :-). However the rampart-1.0 configuration causes a few
issues when we try to interop with other implementations. For example
if the endpoint policy requires a signed Timestamp with "strict"
header layout, the rampart-1.0 configuration fails to satisfy those
requirements. Therefore the best option
Thanks,
Ruchith
[1] http://ws.apache.org/axis2/modules/rampart/1_1/sec-conf/rampart-config.xsd
On 1/18/07, Dimuthu Leelaratne <di...@gmail.com> wrote:
> Hi Sriram,
>
> As I understand your single client can tallk to multiple services but
> with different security requirements. For configurations now we
> encourage using Policy file according to WS Security Policy
> specification (http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf).
>
> Since your services require different security settings, we may have
> to create different Policy.xml files. After that according to the
> service the client is going to invoke you can load the relevant
> Policy file as follows.
>
> StAXOMBuilder builder = new StAXOMBuilder(pathToPolicyfile);
> Policy clientPolicy =
> PolicyEngine.getPolicy(builder.getDocumentElement());
> //setting the object
> Options options = new Options();
> options.setProperty(RampartMessageData.KEY_RAMPART_POLICY,
> clientPolicy);
>
>
> Schemas are available at,
> http://ws.apache.org/axis2/modules/rampart/1_1/security-module.html
>
> Cheers,
> Dimuthu
>
>
>
> On 1/18/07, Sriram Vaidyanathan <Sr...@copart.com> wrote:
> > Hi,
> > I am currently trying to upgrade to Rampart 1.1 from Rampart 1.0 and using Rampart 1.0 we could talk to multiple services from a single client by programmatically configuring the parameters using the OutflowConfiguration class.
> >
> > From previous posts in the forum it looks like these are deprecated with the 1.1 releases. Is there an alternative way we can dynamically configure the parameters in 1.1? Any help on this would be appreciated.
> >
> > Thanks and Regards
> > Sriram Vaidyanathan
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
www.ruchith.org
www.wso2.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Configuration in Rampart 1.1
Posted by Dimuthu Leelaratne <di...@gmail.com>.
Hi Sriram,
As I understand your single client can tallk to multiple services but
with different security requirements. For configurations now we
encourage using Policy file according to WS Security Policy
specification (http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf).
Since your services require different security settings, we may have
to create different Policy.xml files. After that according to the
service the client is going to invoke you can load the relevant
Policy file as follows.
StAXOMBuilder builder = new StAXOMBuilder(pathToPolicyfile);
Policy clientPolicy =
PolicyEngine.getPolicy(builder.getDocumentElement());
//setting the object
Options options = new Options();
options.setProperty(RampartMessageData.KEY_RAMPART_POLICY,
clientPolicy);
Schemas are available at,
http://ws.apache.org/axis2/modules/rampart/1_1/security-module.html
Cheers,
Dimuthu
On 1/18/07, Sriram Vaidyanathan <Sr...@copart.com> wrote:
> Hi,
> I am currently trying to upgrade to Rampart 1.1 from Rampart 1.0 and using Rampart 1.0 we could talk to multiple services from a single client by programmatically configuring the parameters using the OutflowConfiguration class.
>
> From previous posts in the forum it looks like these are deprecated with the 1.1 releases. Is there an alternative way we can dynamically configure the parameters in 1.1? Any help on this would be appreciated.
>
> Thanks and Regards
> Sriram Vaidyanathan
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org