axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe" <>
Subject RE: WS-Security
Date Fri, 13 May 2005 03:13:31 GMT
Hi Pat,
            Looks like you just need username/password token support as
of now, and no encryption is required.
            Hence, to deal with this security header, you may be able to
develop a handler. Using the handler, you would be able to set the
required SOAP headers. This would be a workaround for the time being.
-----Original Message-----
From: Patrick Heffernan [] 
Sent: Friday, May 13, 2005 12:12 AM
To: 'Apache AXIS C User List'
Subject: RE: WS-Security
Hi Samisa, Dinesh, and John,
Thanks for taking on my WS-Security question.
I've got a Linux C++ application that I'm modifying to send web services
requests to a Microsoft WS server that is implementing the Web Services
Enhancements (WSE) package that includes WS-Security.  I have no choice
in the server as we are a third party developer that is integrating our
product into an existing system (and we're not a Microsoft shop to boot
-- so not taking on a MS WS client!).  I've had them turn off the
security stuff on the dev system we're testing against so I can continue
my application dev/testing but the WS-Security obviously needs to be in
place for us to go to production.
This is the format of soap messages I am required to support:
<?xml version="1.0" encoding="utf-16"?>
<soap:Envelope xmlns:soap=""
    <wsrp:path soap:actor=""
soap:mustUnderstand="1" xmlns:wsrp="">
      <wsrp:action wsu:Id="Id-d579335c-2dd7-456c-8858-7ef6942b5de1"
      <wsrp:to wsu:Id="Id-82b10467-2f1d-49ca-a473-51f5322ccba9"
      <wsrp:id wsu:Id="Id-ff1f9f68-3c2c-4241-9dde-13615792f440"
    <wsse:Security soap:mustUnderstand="1"
        <wsse:Password Type="wsse:PasswordText">aa</wsse:Password>
      <Signature xmlns="">
Algorithm="" />
Algorithm="" />
          <Reference URI="#Id-da5e3a0c-295a-4cb3-80cc-7d823fc48e3a">
Algorithm="" />
Algorithm="" />
          <Reference URI="#Id-d579335c-2dd7-456c-8858-7ef6942b5de1">
Algorithm="" />
Algorithm="" />
          <Reference URI="#Id-82b10467-2f1d-49ca-a473-51f5322ccba9">
Algorithm="" />
Algorithm="" />
          <Reference URI="#Id-ff1f9f68-3c2c-4241-9dde-13615792f440">
Algorithm="" />
Algorithm="" />
          <Reference URI="#Id-d76e05cc-0cfc-4bb4-b488-fbbab35f3f78">
Algorithm="" />
Algorithm="" />
          <Reference URI="#Id-0519fa62-4a7f-4c78-bfaf-770819003582">
Algorithm="" />
Algorithm="" />
URI="#SecurityToken-9d8ff073-b0ea-41a7-ae7f-c76f5b6558b0" />
  <soap:Body wsu:Id="Id-da5e3a0c-295a-4cb3-80cc-7d823fc48e3a"
      <accountNumber9 />
It sounds like you guys have done alot of good work on this.  What are
the chances of getting it completed in the near future?  Other than me
trying to hack something to make it work, do I have any other options?
Thanks again,
	-----Original Message-----
	From: John Hawkins [] 
	Sent: Thursday, May 12, 2005 3:30 AM
	To: Apache AXIS C User List
	Subject: Re: WS-Security
	So, it doesn't sound like we're that far off - if we just
implement the getSOAPBodyAsString() method then we would be able to have
ws-security on client-side (at least)? 
Din%$h <> 
12/05/2005 10:21 
Please respond to
"Apache AXIS C User List"
Apache AXIS C User List <> 
Re: WS-Security
	Hi John,
	    Let me breif what we tried to do.
	  When Client make a request ,  we get the Body from the
serializer and Encrypt it again set those encrypted Body to the message.
At the server end we got the encrypted message from the deserializer and
decrypted it. and get the original message. For the response flow also
scenario remains same. We hoped to do it using an handler.
	Since there was a method called getBodyAsString(), (as I
remember). We creadted DOM tree using that body. ( If we could get
Object Model that was easier). 
	giving soap message as a String I was able to Encrypt it and
Giving that Encrypt message I was able to got that  original message
	Since there wasn't a way to get acess to the Body(
getSoapBodyAsString ()  or any other method which can access body didn't
implemented at that time). We didn't able to integrate it with axis
using a handler.
	On 5/12/05, John Hawkins <> wrote: 
	Hi Dinesh, 
	Can I ask - how you wanted that soap body? 
	Would you need a byte stream or an object model? 
	Was this client or server side or both? 
	Was it on the outgoing or incoming message or both? 
Din%$h < <> > 
12/05/2005 08:07 
Please respond to
"Apache AXIS C User List"
Apache AXIS C User List <
<> > 
Re: WS-Security
	    Both Sameera and my self had worked on this (WSS4C). We
needed to get body of Soap Message through a handler.( from Serilizer).
But Unfortunately It was not implemented at that time.( It was commented
/* To do */). There were some threads discussing about those methods. 
	We were unable to get access to the Body of the Soap message
through a handler.So we 
	stopped at that point. ( Until those methods are implemented )
	I don't know whether some one is working on this Project now.
	On 5/12/05, Samisa Abeysinghe < > wrote: 
	There were some efforts and there were some improvements
proposed to the
	current engine to help implement WS-Security ,like opening up
the SOAP
	body in handlers. But we did not hear from anyone on this
	Is there anyone working on WS-Sec at the moment?
	-----Original Message-----
	From: Patrick Heffernan
[ ]
	Sent: Thursday, May 12, 2005 12:14 PM
	Subject: WS-Security
	I apologize if I've missed this in some publication.  What is
the plan 
	for Axis C++ support WS-Security?  I've got a project that
requires the
	WSE Username/Password token and I'm trying to determine what
options are
	available to me.
	Thanks, pat
	W.Dinesh Premalal
	W.Dinesh Premalal 

View raw message