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 "Jones, Alan R" <al...@boeing.com> on 2006/08/09 22:18:26 UTC
[AXIS2] OutflowSecurity configuration
Assuming there are several services deployed to the same axis2
deployment (Tomcat) and they all need to talk to each other with secured
messages...
Each service is also a client of one or more other services. Therefore,
each service will need its own axis2.xml in order to config its keystore
alias/user, the sec.properties, etc. via OutflowSecurity entry. This
implies a separate axis2 "client" repository for each provider/consumer,
which in turn requires a certain directory structure (repos/conf,
repos/modules, etc) since axis throws errors when the structure is
absent. This is not desirable. Soooo...
Is it possible to instead dynamically set the OutflowSecurity parameters
inside each service, as it begins to make its call to an external
service, eliminating the need for a static config file and all its
attendant other stuff?
Thanks,
aj
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: [AXIS2] OutflowSecurity configuration
Posted by "Jones, Alan R" <al...@boeing.com>.
OK, thanks, I will give it a shot!
Thanks,
Alan J
--------------------------------------------
Alan R Jones
Software Engineering
Boeing S&IS Mission Systems
Denver Engineering Center (BDEC)
-----Original Message-----
From: Ruchith Fernando [mailto:ruchith.fernando@gmail.com]
Sent: Thursday, August 10, 2006 9:51 AM
To: axis-user@ws.apache.org
Subject: Re: [AXIS2] OutflowSecurity configuration
If you are using Axis2-1.0 and Rampart-1.0 then there's only one
difference:
The package of InflowConiguration and OutflowConfiguration are :
"org.apache.axis2.security.handler.config"
The usage is the same.
Thanks,
Ruchith
On 8/10/06, Jones, Alan R <al...@boeing.com> wrote:
> ...what if I am not using nightly build? I still am using axis2 1.0
> "orginal" release, after attempting to switch over it seems to be
> several degrees of added complexity to use the nightly, since I am
> using the Java2WSDL/WSDL2Java tool for code/doc gen, etc (cannot get
> cmd line WSDL2Java going correctly).
>
>
> Thanks,
>
> Alan J
>
>
> --------------------------------------------
> Alan R Jones
> Software Engineering
> Boeing S&IS Mission Systems
> Denver Engineering Center (BDEC)
>
> -----Original Message-----
> From: Ruchith Fernando [mailto:ruchith.fernando@gmail.com]
> Sent: Wednesday, August 09, 2006 8:17 PM
> To: axis-user@ws.apache.org
> Subject: Re: [AXIS2] OutflowSecurity configuration
>
> Hi aj,
>
> Yes its possible to set the configuration dynamically within the
> service (for the service client).
>
> If you are using the nightly build then you can use
> org.apache.rampart.handler.config.OutflowConfiguration and
> org.apache.rampart.handler.config.InflowConfiguration for this. You
> can create instances of the above classes and set different config
> parameters using the available setter methods (See [1]
> getOutflowConfiguration() and getInflowConfiguration()). Then you can
> obtain an Axis2 parameter form each of the above instances by calling
> getProerty(). This parameter instance can be set in the options object
> of the ServiceClient (See here [2] invokeWithGivenConfig()).
>
> Thanks,
> Ruchith
>
> [1]
> https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/
> in
> tegration/test/org/apache/axis2/security/AddressingMTOMSecurityTest.ja
> va
> [2]
> https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/
> se curity/interop/org/apache/axis2/security/InteropScenarioClient.java
> On 8/10/06, Jones, Alan R <al...@boeing.com> wrote:
> >
> > Assuming there are several services deployed to the same axis2
> > deployment (Tomcat) and they all need to talk to each other with
> > secured messages...
> >
> > Each service is also a client of one or more other services.
> > Therefore, each service will need its own axis2.xml in order to
> > config
>
> > its keystore alias/user, the sec.properties, etc. via
> > OutflowSecurity entry. This implies a separate axis2 "client"
> > repository for each provider/consumer, which in turn requires a
> > certain directory structure (repos/conf, repos/modules, etc) since
> > axis throws errors when the structure is absent. This is not
desirable. Soooo...
> >
> > Is it possible to instead dynamically set the OutflowSecurity
> > parameters inside each service, as it begins to make its call to an
> > external service, eliminating the need for a static config file and
> > all its attendant other stuff?
> >
> >
> >
> > Thanks,
> >
> > aj
> >
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
> --
> www.ruchith.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
>
>
--
www.ruchith.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: [AXIS2] OutflowSecurity configuration
Posted by Ruchith Fernando <ru...@gmail.com>.
If you are using Axis2-1.0 and Rampart-1.0 then there's only one difference:
The package of InflowConiguration and OutflowConfiguration are :
"org.apache.axis2.security.handler.config"
The usage is the same.
Thanks,
Ruchith
On 8/10/06, Jones, Alan R <al...@boeing.com> wrote:
> ...what if I am not using nightly build? I still am using axis2 1.0
> "orginal" release, after attempting to switch over it seems to be
> several degrees of added complexity to use the nightly, since I am using
> the Java2WSDL/WSDL2Java tool for code/doc gen, etc (cannot get cmd line
> WSDL2Java going correctly).
>
>
> Thanks,
>
> Alan J
>
>
> --------------------------------------------
> Alan R Jones
> Software Engineering
> Boeing S&IS Mission Systems
> Denver Engineering Center (BDEC)
>
> -----Original Message-----
> From: Ruchith Fernando [mailto:ruchith.fernando@gmail.com]
> Sent: Wednesday, August 09, 2006 8:17 PM
> To: axis-user@ws.apache.org
> Subject: Re: [AXIS2] OutflowSecurity configuration
>
> Hi aj,
>
> Yes its possible to set the configuration dynamically within the service
> (for the service client).
>
> If you are using the nightly build then you can use
> org.apache.rampart.handler.config.OutflowConfiguration and
> org.apache.rampart.handler.config.InflowConfiguration for this. You can
> create instances of the above classes and set different config
> parameters using the available setter methods (See [1]
> getOutflowConfiguration() and getInflowConfiguration()). Then you can
> obtain an Axis2 parameter form each of the above instances by calling
> getProerty(). This parameter instance can be set in the options object
> of the ServiceClient (See here [2] invokeWithGivenConfig()).
>
> Thanks,
> Ruchith
>
> [1]
> https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/in
> tegration/test/org/apache/axis2/security/AddressingMTOMSecurityTest.java
> [2]
> https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/se
> curity/interop/org/apache/axis2/security/InteropScenarioClient.java
> On 8/10/06, Jones, Alan R <al...@boeing.com> wrote:
> >
> > Assuming there are several services deployed to the same axis2
> > deployment (Tomcat) and they all need to talk to each other with
> > secured messages...
> >
> > Each service is also a client of one or more other services.
> > Therefore, each service will need its own axis2.xml in order to config
>
> > its keystore alias/user, the sec.properties, etc. via OutflowSecurity
> > entry. This implies a separate axis2 "client" repository for each
> > provider/consumer, which in turn requires a certain directory
> > structure (repos/conf, repos/modules, etc) since axis throws errors
> > when the structure is absent. This is not desirable. Soooo...
> >
> > Is it possible to instead dynamically set the OutflowSecurity
> > parameters inside each service, as it begins to make its call to an
> > external service, eliminating the need for a static config file and
> > all its attendant other stuff?
> >
> >
> >
> > Thanks,
> >
> > aj
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
> --
> www.ruchith.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
>
>
--
www.ruchith.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: [AXIS2] OutflowSecurity configuration
Posted by "Jones, Alan R" <al...@boeing.com>.
...what if I am not using nightly build? I still am using axis2 1.0
"orginal" release, after attempting to switch over it seems to be
several degrees of added complexity to use the nightly, since I am using
the Java2WSDL/WSDL2Java tool for code/doc gen, etc (cannot get cmd line
WSDL2Java going correctly).
Thanks,
Alan J
--------------------------------------------
Alan R Jones
Software Engineering
Boeing S&IS Mission Systems
Denver Engineering Center (BDEC)
-----Original Message-----
From: Ruchith Fernando [mailto:ruchith.fernando@gmail.com]
Sent: Wednesday, August 09, 2006 8:17 PM
To: axis-user@ws.apache.org
Subject: Re: [AXIS2] OutflowSecurity configuration
Hi aj,
Yes its possible to set the configuration dynamically within the service
(for the service client).
If you are using the nightly build then you can use
org.apache.rampart.handler.config.OutflowConfiguration and
org.apache.rampart.handler.config.InflowConfiguration for this. You can
create instances of the above classes and set different config
parameters using the available setter methods (See [1]
getOutflowConfiguration() and getInflowConfiguration()). Then you can
obtain an Axis2 parameter form each of the above instances by calling
getProerty(). This parameter instance can be set in the options object
of the ServiceClient (See here [2] invokeWithGivenConfig()).
Thanks,
Ruchith
[1]
https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/in
tegration/test/org/apache/axis2/security/AddressingMTOMSecurityTest.java
[2]
https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/se
curity/interop/org/apache/axis2/security/InteropScenarioClient.java
On 8/10/06, Jones, Alan R <al...@boeing.com> wrote:
>
> Assuming there are several services deployed to the same axis2
> deployment (Tomcat) and they all need to talk to each other with
> secured messages...
>
> Each service is also a client of one or more other services.
> Therefore, each service will need its own axis2.xml in order to config
> its keystore alias/user, the sec.properties, etc. via OutflowSecurity
> entry. This implies a separate axis2 "client" repository for each
> provider/consumer, which in turn requires a certain directory
> structure (repos/conf, repos/modules, etc) since axis throws errors
> when the structure is absent. This is not desirable. Soooo...
>
> Is it possible to instead dynamically set the OutflowSecurity
> parameters inside each service, as it begins to make its call to an
> external service, eliminating the need for a static config file and
> all its attendant other stuff?
>
>
>
> Thanks,
>
> aj
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
www.ruchith.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: [AXIS2] OutflowSecurity configuration
Posted by Ruchith Fernando <ru...@gmail.com>.
Hi aj,
Yes its possible to set the configuration dynamically within the
service (for the service client).
If you are using the nightly build then you can use
org.apache.rampart.handler.config.OutflowConfiguration and
org.apache.rampart.handler.config.InflowConfiguration for this. You
can create instances of the above classes and set different config
parameters using the available setter methods (See [1]
getOutflowConfiguration() and getInflowConfiguration()). Then you can
obtain an Axis2 parameter form each of the above instances by calling
getProerty(). This parameter instance can be set in the options object
of the ServiceClient (See here [2] invokeWithGivenConfig()).
Thanks,
Ruchith
[1] https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/security/AddressingMTOMSecurityTest.java
[2] https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/security/interop/org/apache/axis2/security/InteropScenarioClient.java
On 8/10/06, Jones, Alan R <al...@boeing.com> wrote:
>
> Assuming there are several services deployed to the same axis2
> deployment (Tomcat) and they all need to talk to each other with secured
> messages...
>
> Each service is also a client of one or more other services. Therefore,
> each service will need its own axis2.xml in order to config its keystore
> alias/user, the sec.properties, etc. via OutflowSecurity entry. This
> implies a separate axis2 "client" repository for each provider/consumer,
> which in turn requires a certain directory structure (repos/conf,
> repos/modules, etc) since axis throws errors when the structure is
> absent. This is not desirable. Soooo...
>
> Is it possible to instead dynamically set the OutflowSecurity parameters
> inside each service, as it begins to make its call to an external
> service, eliminating the need for a static config file and all its
> attendant other stuff?
>
>
>
> Thanks,
>
> aj
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
www.ruchith.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org