axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alick Buckley <Alick.Buck...@lansa.com.au>
Subject RE: WS Security with Axis 1.4
Date Thu, 08 Mar 2007 21:27:32 GMT

Hi Ken,

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

==============================================================

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_URI,
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.

==========================================================================

 
<deployment name="defaultClientConfig"
xmlns="http://xml.apache.org/axis/wsdd/"
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
 
 <globalConfiguration>
   <parameter name="disablePrettyXML" value="true"/>
   <parameter name="addressing.sendReplyTo" value="true"/>
   <parameter name="enableNamespacePrefixOptimization" value="false"/>
 </globalConfiguration>
 
 <service name="XXXXXXPort">
   <requestFlow>
     <handler
type="java:org.apache.axis.message.addressing.handler.AddressingHandler">
       <!-- Reference elements are added in the same order -->
       <parameter name="referencePropertyNames"
 
value="{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}Action;
 
{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}MessageID;
 
{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}ReplyTo;
 
{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}To;
 
{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}From"/>
     </handler>
     <handler type="java:org.apache.ws.axis.security.WSDoAllSender">
       <!-- action order is important, do Timestamp then Signature if
signing Timestamp -->
       <parameter name="action" value="Timestamp Signature"/>
       <parameter name="user" value="XXXX"/>
       <parameter name="passwordCallbackClass"
value="com.acme.security.PasswordCallback"/>
       <parameter name="signatureKeyIdentifier" value="DirectReference"/>
       <parameter name="signaturePropFile" value="security.properties"/>
       <parameter name="timeToLive" value="300"/>
       <parameter name="precisionInMilliseconds" value="false" />
       <!-- Reference elements are added in the same order -->
       <parameter name="signatureParts"
 
value="{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}Action;
 
{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}MessageID;
 
{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}ReplyTo;
 
{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}To;
 
{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}From;
 
{Element}{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity
-utility-1.0.xsd}Timestamp;
 
{Element}{http://schemas.xmlsoap.org/soap/envelope/}Body"/>
     </handler>
   </requestFlow>
 </service>
 
 <transport name="http"
pivot="java:org.apache.axis.transport.http.HTTPSender"/>
 <transport name="java"
pivot="java:org.apache.axis.transport.java.JavaSender"/>
 <transport name="local"
pivot="java:org.apache.axis.transport.local.LocalSender"/>
 
</deployment>

==========================================================================

-----Original Message-----
From: José 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é Ferreiro
EPFL Communication Systems engineer
ing.sys.com.dipl.EPFL 

==============================================================

-----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

Mime
View raw message