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 keith chapman <ke...@gmail.com> on 2008/09/01 19:05:20 UTC
Re: Rampart Configuration
This can be done but I beleive rampart is moving towards policy now.
Previously configurating rampart via parameters was the way to go. For
e.g If you wanted to enforce UT on a service you could add the
follwoing to the services.xml
<parameter name="InflowSecurity">
<action>
<items>UsernameToken</items>
<passwordCallbackClass>MyPasswordCallbackHandler</passwordCallbackClass>
</action>
</parameter>
Thanks,
Keith.
On Thu, Aug 28, 2008 at 7:42 PM, Shah, Sumit <su...@cgi.com> wrote:
> Is there a way to configure Rampart in Axis2 using parameters rather than a
> Policy file?
>
>
>
> Thanks
>
> Sumit
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Rampart Configuration
Posted by keith chapman <ke...@gmail.com>.
Although you specify the rampart config within the policy we do not display
it in the WSDL. So its safe for you to specify the rampart config in the
policy.
Thanks,
Keith.
On Tue, Sep 9, 2008 at 3:21 AM, Shah, Sumit <su...@cgi.com> wrote:
> I take that back. I was able to run the Sample 01 correctly. But
> removing the Rampart Config from the policy failed for Sample 04.
>
> I am wondering how this would work in an InterOp scenario. Any ideas?
>
> Thanks
> Sumit
>
> -----Original Message-----
> From: Shah, Sumit [mailto:sumit.shah@cgi.com]
> Sent: Monday, September 08, 2008 5:17 PM
> To: axis-user@ws.apache.org
> Subject: RE: Rampart Configuration
>
> Thanks Keith. I did try out the samples. As you mentioned Rampart 1.0
> used parameters, but it seems like Rampart 1.1 uses Policy. I did
> encounter an issue where the Rampart samples have Rampart Config inside
> the Policy. This may become an issue where you are exposing the security
> configurations inside the policy and eventually ends up in the wsdl.
>
> FYI...I was able to remove the Rampart Config from the policy and put it
> outside the <wsp>... </wsp> and it does work.
>
> Thanks
> Sumit
>
>
>
> -----Original Message-----
> From: keith chapman [mailto:keithgchapman@gmail.com]
> Sent: Monday, September 01, 2008 1:05 PM
> To: axis-user@ws.apache.org
> Subject: Re: Rampart Configuration
>
> This can be done but I beleive rampart is moving towards policy now.
> Previously configurating rampart via parameters was the way to go. For
> e.g If you wanted to enforce UT on a service you could add the
> follwoing to the services.xml
>
> <parameter name="InflowSecurity">
> <action>
> <items>UsernameToken</items>
>
> <passwordCallbackClass>MyPasswordCallbackHandler</passwordCallbackClass>
> </action>
> </parameter>
>
> Thanks,
> Keith.
>
> On Thu, Aug 28, 2008 at 7:42 PM, Shah, Sumit <su...@cgi.com> wrote:
> > Is there a way to configure Rampart in Axis2 using parameters rather
> than a
> > Policy file?
> >
> >
> >
> > Thanks
> >
> > Sumit
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
> ---------------------------------------------------------------------
> 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
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
RE: Rampart Configuration
Posted by "Shah, Sumit" <su...@cgi.com>.
I take that back. I was able to run the Sample 01 correctly. But
removing the Rampart Config from the policy failed for Sample 04.
I am wondering how this would work in an InterOp scenario. Any ideas?
Thanks
Sumit
-----Original Message-----
From: Shah, Sumit [mailto:sumit.shah@cgi.com]
Sent: Monday, September 08, 2008 5:17 PM
To: axis-user@ws.apache.org
Subject: RE: Rampart Configuration
Thanks Keith. I did try out the samples. As you mentioned Rampart 1.0
used parameters, but it seems like Rampart 1.1 uses Policy. I did
encounter an issue where the Rampart samples have Rampart Config inside
the Policy. This may become an issue where you are exposing the security
configurations inside the policy and eventually ends up in the wsdl.
FYI...I was able to remove the Rampart Config from the policy and put it
outside the <wsp>... </wsp> and it does work.
Thanks
Sumit
-----Original Message-----
From: keith chapman [mailto:keithgchapman@gmail.com]
Sent: Monday, September 01, 2008 1:05 PM
To: axis-user@ws.apache.org
Subject: Re: Rampart Configuration
This can be done but I beleive rampart is moving towards policy now.
Previously configurating rampart via parameters was the way to go. For
e.g If you wanted to enforce UT on a service you could add the
follwoing to the services.xml
<parameter name="InflowSecurity">
<action>
<items>UsernameToken</items>
<passwordCallbackClass>MyPasswordCallbackHandler</passwordCallbackClass>
</action>
</parameter>
Thanks,
Keith.
On Thu, Aug 28, 2008 at 7:42 PM, Shah, Sumit <su...@cgi.com> wrote:
> Is there a way to configure Rampart in Axis2 using parameters rather
than a
> Policy file?
>
>
>
> Thanks
>
> Sumit
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: Rampart Configuration
Posted by "Shah, Sumit" <su...@cgi.com>.
Thanks Keith. I did try out the samples. As you mentioned Rampart 1.0
used parameters, but it seems like Rampart 1.1 uses Policy. I did
encounter an issue where the Rampart samples have Rampart Config inside
the Policy. This may become an issue where you are exposing the security
configurations inside the policy and eventually ends up in the wsdl.
FYI...I was able to remove the Rampart Config from the policy and put it
outside the <wsp>... </wsp> and it does work.
Thanks
Sumit
-----Original Message-----
From: keith chapman [mailto:keithgchapman@gmail.com]
Sent: Monday, September 01, 2008 1:05 PM
To: axis-user@ws.apache.org
Subject: Re: Rampart Configuration
This can be done but I beleive rampart is moving towards policy now.
Previously configurating rampart via parameters was the way to go. For
e.g If you wanted to enforce UT on a service you could add the
follwoing to the services.xml
<parameter name="InflowSecurity">
<action>
<items>UsernameToken</items>
<passwordCallbackClass>MyPasswordCallbackHandler</passwordCallbackClass>
</action>
</parameter>
Thanks,
Keith.
On Thu, Aug 28, 2008 at 7:42 PM, Shah, Sumit <su...@cgi.com> wrote:
> Is there a way to configure Rampart in Axis2 using parameters rather
than a
> Policy file?
>
>
>
> Thanks
>
> Sumit
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
---------------------------------------------------------------------
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