ws-rampart-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raymond Zhou <raywang...@yahoo.com>
Subject Re: rampart/c test cases response NOT decrypted, and another soapFault problem
Date Thu, 19 Mar 2009 21:11:10 GMT
Just to close the loop, I checked out source code from the trunk for both rampart/c and axis2/c,
I see quality is much better. I got far less access violation, and most importantly, most
rampart/c test cases are working for me. Still, test case senarios 14, 20 and 24 do not work.
 
Thanks!
Ray 

--- On Wed, 3/18/09, Raymond Zhou <raywang999@yahoo.com> wrote:


From: Raymond Zhou <raywang999@yahoo.com>
Subject: Re: rampart/c test cases response NOT decrypted, and another soapFault problem
To: rampart-c-dev@ws.apache.org
Date: Wednesday, March 18, 2009, 12:16 AM


Hi All,
 
Still regarding this issue, now I can re-produce the same issue just by running the same service
and sample client. I am using policy files from senario 3 and the only modification I did
was the paths to point to the right certificate, call back module et cetera. This means that
the problem should not be in my client application code. It could still be in the libraries
I built.
 
I am trying to debug the library code, any suggestions what I should pay attention to? Again,
I am using axis2/c 1.5, rampart/c 1.2 and openSSL 0.9.8.h (excluded IDEA, MDC2 and RC5 by
using ./config no-idea no-mdc2 no-rc5).
 
Thanks in advance!
Ray

--- On Sun, 3/15/09, Uthaiyashankar <shankar@wso2.com> wrote:


From: Uthaiyashankar <shankar@wso2.com>
Subject: Re: rampart/c test cases response NOT decrypted, and another soapFault problem
To: rampart-c-dev@ws.apache.org
Date: Sunday, March 15, 2009, 2:55 AM


Hi,

Can you attach the client code, service.xml and client policy. The problem
is, it saves rampart context in the out path and then uses it in the inpath...
It could not find the rampart context saved in the outpath. It might be a
problem in your client code.

Regards,
Shankar

On Sat, Mar 14, 2009 at 5:43 AM, Raymond Zhou <raywang999@yahoo.com> wrote:

> Hi All,
>
> I have been testing my web service client application using axis2/c and
> rampart/c (built my myself, axis2/c version 1.5 and rampart/c version 1.2).
> Now I have two problems left:
>
> (1) I went through the rampart/c test cases, senario 1 and 2 works fine to
> me (time to live, username/password), for the rest cases, the response from
> the server is not decrypted, and there is an error message in the log as the
> following:
>
> ======
> ......
> [Fri Mar 13 16:59:39 2009] [debug] ..\..\axiom\src\soap\soap_builder.c(895)
> Identified soap version is soap11
> [Fri Mar 13 16:59:39 2009] [debug] ..\..\src\core\engine\phase.c(210)
> Invoke the handler request_uri_based_dispatcher within the phase Transport
> [Fri Mar 13 16:59:39 2009] [debug] ..\..\src\core\engine\phase.c(210)
> Invoke the handler AddressingInHandler within the phase Transport
> [Fri Mar 13 16:59:39 2009] [info]  Starting addressing in handler
> [Fri Mar 13 16:59:39 2009] [info]
> ..\..\src\modules\mod_addr\addr_in_handler.c
> [Fri Mar 13 16:59:39 2009] [debug] ..\..\src\core\engine\phase.c(210)
> Invoke the handler addressing_based_dispatcher within the phase Transport
> [Fri Mar 13 16:59:39 2009] [debug] ..\..\src\core\engine\phase.c(210)
> Invoke the handler RampartInHandler within the phase PreDispatch
> [Fri Mar 13 16:59:39 2009] [debug] ..\..\src\omxmlsec\axiom.c(111)
> [rampart][axiom] Checking node Body for Subcode
> [Fri Mar 13 16:59:39 2009] [debug] ..\..\src\omxmlsec\axiom.c(111)
> [rampart][axiom] Checking node Fault for Subcode
> [Fri Mar 13 16:59:39 2009] [debug] ..\..\src\omxmlsec\axiom.c(111)
> [rampart][axiom] Checking node Code for Subcode
> [Fri Mar 13 16:59:39 2009] [debug] ..\..\src\omxmlsec\axiom.c(111)
> [rampart][axiom] Checking node Value for Subcode
> [Fri Mar 13 16:59:39 2009] [debug] ..\..\src\omxmlsec\axiom.c(111)
> [rampart][axiom] Checking node Subcode for Subcode
> [Fri Mar 13 16:59:39 2009] [error] ..\..\src\util\rampart_engine.c(122)
> [rampart][rampart_engine] Cannot get saved rampart_context
> [Fri Mar 13 16:59:39 2009] [error]
> ..\..\src\handlers\rampart_in_handler.c(114) [rampart][rampart_in_handler]
> rampart_context creation failed.
> [Fri Mar 13 16:59:39 2009] [error] ..\..\src\core\engine\phase.c(216)
> Handler RampartInHandler invoke failed within phase PreDispatch
> [Fri Mar 13 16:59:39 2009] [error] ..\..\src\core\engine\engine.c(696)
> Invoking phase PreDispatch failed
> [Fri Mar 13 16:59:39 2009] [info]  [rampart][rampart_mod] rampart_mod
> shutdown
> ==============
>
> I wonder what might be the problem. Given the fact that I am able to get
> the first two senario working(I manually created WSDL from the test cases
> and import into my application, then use the configuration files in the test
> senarios), I guess my configuration is OK.
>
> (2) I noticed that the soapFault returned from the simple server is not
> well formed if the soap version is 1.1, which is what I am using. Can this
> be fixed?
>
> Thanks!
> Ray
>
>
>




-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"



      


      
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message