Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 94238 invoked from network); 8 Mar 2007 21:28:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Mar 2007 21:28:18 -0000 Received: (qmail 21502 invoked by uid 500); 8 Mar 2007 21:28:16 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 21489 invoked by uid 500); 8 Mar 2007 21:28:15 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 21478 invoked by uid 99); 8 Mar 2007 21:28:15 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Mar 2007 13:28:15 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [61.88.115.245] (HELO SYD3.lansa.com.au) (61.88.115.245) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Mar 2007 13:28:04 -0800 Message-ID: <817522051E65D511A2740001028074C402EEB1CD@EX1> From: Alick Buckley To: axis-user@ws.apache.org Subject: RE: WS Security with Axis 1.4 Date: Fri, 9 Mar 2007 08:27:32 +1100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C761C8.94C59A40" X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C761C8.94C59A40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Ken, This question has been asked before on this mailing list - RE: [Axis = 1.4 & WSS4J] - WS-Addressing =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RE: [Axis 1.4 & WSS4J] - WS-Addressing Hi Jose, =20 I have used WS-Addressing and WS-Security with Axis 1.4 as an Agent to = talk to a .NET server. =20 I used WSSJ4 1.5.1, XMLSecurity 1.4 and the addressing-SNAPSHOT.jar = from Sandesha 1.0 =20 WS-Addressing is using the 2004/08 namespace and .NET expects the older 2004/03 namespace, so use the following to change it. stub._setProperty ( org.apache.axis.message.addressing.Constants.ENV_ADDRESSING_NAMESPACE_UR= I, org.apache.axis.message.addressing.Constants.NS_URI_ADDRESSING_2004_03 = ) ; The biggest headache is the SOAP message failing the .NET policy checks = and .NET not telling you what it is complaining about. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D =20 =20 =20 =20 =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D -----Original Message----- From: Jos=E9 Ferreiro [mailto:jose.ferreiro@gmail.com] Sent: Thursday, 15 February 2007 7:22 AM To: axis-user@ws.apache.org; wss4j-dev@ws.apache.org Subject: [Axis 1.4 & WSS4J] - WS-Addressing Hello, =20 Did someone try to implement WS-addressing using Axis 1.4 and WSS4J? I am working in a prototype for interoperability ( C#, .net 2.0, and = WSE 3.0 ). =20 Any coments, suggestions are welcome. =20 Regards --=20 Jos=E9 Ferreiro EPFL Communication Systems engineer ing.sys.com.dipl.EPFL=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D -----Original Message----- From: Anne Thomas Manes [mailto:atmanes@gmail.com] Sent: Friday, 9 March 2007 4:54 AM To: axis-user@ws.apache.org; kentam@proteustech.com Subject: Re: WS Security with Axis 1.4 WSS4J is the right way to go. On 3/8/07, Ken Tam wrote: > Hi all, > > I am using Axis 1.4 on a standalone Java client to invoke a web = service. > This is working fine but the same web service has enabled WSE 3.0 security. > I have the client and server certificates. How do I apply WS = Security? Is > WSS4J the right way to go? Any sample code would be helpful. > > Thanks, > Ken > > > > > --------------------------------------------------------------------- > 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 ------_=_NextPart_001_01C761C8.94C59A40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: WS Security with Axis 1.4

Hi Ken,

This question has been asked before on this mailing = list - RE: [Axis 1.4 & WSS4J] - WS-Addressing

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

RE: [Axis 1.4 & WSS4J] - WS-Addressing

Hi Jose,
 
I have used WS-Addressing and WS-Security with Axis = 1.4 as an Agent to talk to a .NET server.
 
I used WSSJ4 1.5.1, XMLSecurity 1.4 and the = addressing-SNAPSHOT.jar from Sandesha 1.0
 
WS-Addressing is using the 2004/08 namespace and = .NET expects the older 2004/03 namespace, so use the following to = change it.

stub._setProperty ( = org.apache.axis.message.addressing.Constants.ENV_ADDRESSING_NAMESPACE_UR= I, = org.apache.axis.message.addressing.Constants.NS_URI_ADDRESSING_2004_03 = ) ;

The biggest headache is the SOAP message failing the = .NET policy checks and .NET not telling you what it is complaining = about.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D

 
<deployment = name=3D"defaultClientConfig" xmlns=3D"http://xml.apache.org/axis/wsdd/" = xmlns:java=3D"http://xml.apache.org/axis/wsdd/providers/java&quo= t;>

 
 <globalConfiguration>
   <parameter = name=3D"disablePrettyXML" = value=3D"true"/>
   <parameter = name=3D"addressing.sendReplyTo" = value=3D"true"/>
   <parameter = name=3D"enableNamespacePrefixOptimization" = value=3D"false"/>
 </globalConfiguration>
 
 <service = name=3D"XXXXXXPort">
   <requestFlow>
     <handler = type=3D"java:org.apache.axis.message.addressing.handler.AddressingH= andler">
       <!-- = Reference elements are added in the same order -->
       <parameter = name=3D"referencePropertyNames"
          &nb= sp;       value=3D"{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}A= ction;
          &nb= sp;           &nb= sp;  {Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}M= essageID;
          &nb= sp;           &nb= sp;  {Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}R= eplyTo;
          &nb= sp;           &nb= sp;  {Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}T= o;
          &nb= sp;           &nb= sp;  {Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}F= rom"/>
     </handler>
     <handler = type=3D"java:org.apache.ws.axis.security.WSDoAllSender">
       <!-- action = order is important, do Timestamp then Signature if signing Timestamp = -->
       <parameter = name=3D"action" value=3D"Timestamp = Signature"/>
       <parameter = name=3D"user" value=3D"XXXX"/>
       <parameter = name=3D"passwordCallbackClass" = value=3D"com.acme.security.PasswordCallback"/>
       <parameter = name=3D"signatureKeyIdentifier" = value=3D"DirectReference"/>
       <parameter = name=3D"signaturePropFile" = value=3D"security.properties"/>
       <parameter = name=3D"timeToLive" value=3D"300"/>
       <parameter = name=3D"precisionInMilliseconds" value=3D"false" = />
       <!-- = Reference elements are added in the same order -->
       <parameter = name=3D"signatureParts"
          &nb= sp;       value=3D"{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}A= ction;
          &nb= sp;           &nb= sp;  {Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}M= essageID;
          &nb= sp;           &nb= sp;  {Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}R= eplyTo;
          &nb= sp;           &nb= sp;  {Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}T= o;
          &nb= sp;           &nb= sp;  {Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}F= rom;
          &nb= sp;           &nb= sp;  {Element}{http://docs.oasis-open.org/wss/2004/01/oasis-200401-ws= s-wssecurity-utility-1.0.xsd}Timestamp;

          &nb= sp;           &nb= sp;  {Element}{http://schemas.xmlsoap.org/soap/envelope/}Body&quo= t;/>
     </handler>
   </requestFlow>
 </service>
 
 <transport name=3D"http" = pivot=3D"java:org.apache.axis.transport.http.HTTPSender"/><= /FONT>
 <transport name=3D"java" = pivot=3D"java:org.apache.axis.transport.java.JavaSender"/><= /FONT>
 <transport name=3D"local" = pivot=3D"java:org.apache.axis.transport.local.LocalSender"/>= ;
 
</deployment>

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D

-----Original Message-----
From: Jos=E9 Ferreiro [mailto:jose.ferreiro@gmail.com]
Sent: Thursday, 15 February 2007 7:22 AM
To: axis-user@ws.apache.org; = wss4j-dev@ws.apache.org
Subject: [Axis 1.4 & WSS4J] - = WS-Addressing


Hello,
 
Did someone try to implement WS-addressing using = Axis 1.4 and WSS4J?
I am working in a prototype for interoperability ( = C#, .net 2.0, and WSE 3.0 ).
 
Any coments, suggestions are welcome.
 
Regards

--
Jos=E9 Ferreiro
EPFL Communication Systems engineer
ing.sys.com.dipl.EPFL

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

-----Original Message-----
From: Anne Thomas Manes [mailto:atmanes@gmail.com]
Sent: Friday, 9 March 2007 4:54 AM
To: axis-user@ws.apache.org; = kentam@proteustech.com
Subject: Re: WS Security with Axis 1.4


WSS4J is the right way to go.

On 3/8/07, Ken Tam <kentam@proteustech.com> = wrote:
> Hi all,
>
> I am using Axis 1.4 on a standalone Java client = to invoke a web service.
> This is working fine but the same web service = has enabled WSE 3.0 security.
> I have the client and server certificates. How = do I apply WS Security? Is
> WSS4J the right way to go? Any sample code = would be helpful.
>
> Thanks,
> Ken
>
>
>
>
> = ---------------------------------------------------------------------
> 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

------_=_NextPart_001_01C761C8.94C59A40--