Hi Divakr, Looking at your client code I have some problems. In Your client why are you building the security header on your own? Because if you engage rampart/c it will do all the necessary things reguarding soap message security. IMHO following are things you need to do for your scenario.
1. Specify CA-Cert as you done in the client code. 2. Use the policy file as in the rampart_src_dir/samples/secpolicy/scenario2/policy.xml 3. put it into your client-repo 4. To set policy in your client code please refer to the client code at rampart_src_dir/samples/client/sec_echo/echo.c Thanks, -Manjula. On Tue, 2007-10-02 at 13:08 +0530, Dumindu Pallewela wrote: > Hi Divakar, > > I could not find why it didn't work for you, according to the logs. > If you can build Axis2/C from source, you can test if the SSL > transport (i.e., without any SOAP stuff) is working using the > test/core/transport/http/test_http_transport.c test case. > > Regards, > Dumindu. > > divakar wrote: > > Hi All, > > > > I am facing some problems with invoking a https based .Net > > webservice using the axis2c client. It is giving the error " Error code: > > 82 :: Input stream is NULL in msg_ctx" in the client log file. I am > > attaching the axis2.xml, client log file & sample program for your > > reference. Please check the same and let me know, if i am making any > > mistakes in my client program. > > > > > > Thanks & Regards, > > > > Murali Krishna K > > > > > > ------------------------------------------------------------------------ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
