Re: Re : Re : Re : basic auth on the standalone server
On Thu, Mar 5, 2009 at 9:49 PM, Sihem stfle...@yahoo.fr wrote: anyway is there a way to add HTTP authentication support in the standalone directly in the code ? I'm afraid, this might require quite some work in transport code. HTTP authentication is not provided in the server. So if you want it in simple axis server you have to implement it yourself. Thanks, Dumindu.
Re: Re : Re : basic auth on the standalone server
Hi Sihem, We don't currently support HTTP Auth with simple_axis_server. Nor do we have any plans for that as of yet. If you need authentication you'll have to deploy axis2/c module in apache httpd, and configure authentication there. This is the recommended way of deploying axis2/c server. Our client side of course support HTTP Auth. That's where the authentication parameters in trasportSender applies. Thanks, Dumindu. On Thu, Mar 5, 2009 at 8:07 PM, Sihem stfle...@yahoo.fr wrote: Hello! finally I found some documentations about HTTP authentication which seems to be easy to set up. I modified the axis2.xml file as followed: transportSender name=http class=axis2_http_sender parameter name=PROTOCOL locked=falseHTTP/1.1/parameter parameter name=xml-declaration insert=false/ parameter name=HTTP-Authentication username=sihem password=sihem locked=true/ /transportSender and I use the echo_blocking_auth application (located in axis2c-src-1.5.0/samples/user_guide/clients) But the function axis2_svc_client_get_http_auth_required(svc_client, env) returns false which indicates that the server does not wait for credentials. So is there something else to configure ? Thanks by advance sihem De : Sihem stfle...@yahoo.fr À : Apache AXIS C User List axis-c-user@ws.apache.org Envoyé le : Jeudi, 5 Mars 2009, 13h17mn 15s Objet : Re : basic auth on the standalone server I finally found that I have to to change http_sender.c to add an http level authentication mechanism. is there any documentation or sample giving some explanations ? Thanks! sihem De : Sihem stfle...@yahoo.fr À : axis-c-user@ws.apache.org Envoyé le : Jeudi, 5 Mars 2009, 11h52mn 41s Objet : basic auth on the standalone server Hello! I would like to know whether the standalone server supports a basic HTTP authentication because I found nothing on the newsgroup about that. Thanks by advance sihem
Re: special character escaping in adb requests
Does AXIOM support CDATA sections? If so I think this can simply be solved by using a CDATA section. Thanks, Dumindu. On Fri, Jan 30, 2009 at 9:20 AM, Dimuthu Gamage dimut...@gmail.com wrote: Unfortunately we don't have such a function in the axutil yet. But it is trival to implement. I just did a google and found this, [1]. We can use the algorithm for the parse data. [1] http://www.hdfgroup.org/HDF5/XML/xml_escape_chars.htm Thanks Dimuthu On Thu, Jan 29, 2009 at 10:48 PM, Haszlakiewicz, Eric ehas...@transunion.com wrote: hmm... well that sucks. Is there an axis function to do this easily, or do I need to find one somewhere else? Also, how do I know what kind of escaping to do? It's possible to have axis send the request as a soap doc, or as a json message, so I can't use the same escaping for each, right? eric -Original Message- From: Dimuthu Gamage [mailto:dimut...@gmail.com] Sent: Wednesday, January 28, 2009 9:01 PM To: Apache AXIS C User List Subject: Re: special character escaping in adb requests Hi Eric, Unfortunately You have to set the texts after escaping these characters at least for now. It is apparently a bug. (we should do it inside). Can you please raise a JIRA issue on that. Thanks Dimuthu On Thu, Jan 29, 2009 at 12:48 AM, Haszlakiewicz, Eric ehas...@transunion.com wrote: I have an app that uses adb to construct messages to send to a web service. Everything works fine, unless my data contains characters like '', in which case axis fails to escape the characters and generates invalid xml (I'm using xml messages). I'm doing things like: axis2_stub_t *my_service = axis2_stub_create_MyService(env, client_home, url); adb_foo_t *myreq = adb_foo_create(env); adb_foo_set_myfield(myreq, env, abcxyz); adb_fooresp_t *response = axis2_stub_op_MyService_myOp(an_service, env, myreq); The adb code was generated from a wsdl (and xsd) that has elements defined like: xs:element name=foo type=xs:string/ and the command used was: axis2.sh org.apache.axis2.wsdl.WSDL2C -uri myservice.wsdl -d adb -u -o generated Is there some extra step I need to take to make this work right? Or, is there some bug that might be fixed in a more recent version? eric -- Thanks, Dimuthu Gamage http://www.dimuthu.org http://www.wso2.org -- Thanks, Dimuthu Gamage http://www.dimuthu.org http://www.wso2.org
Re: ver 1.6
Hi, I have started on the XPath integration. I sent a separate email regarding that. It will take some time to get it properly tested. Regards, Dumindu. On Wed, Oct 8, 2008 at 5:24 PM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Uthaiyashankar wrote: Nandika Jayawardana wrote: The code developed under for the two GSOC projects are also there. XPath support is still not integrated. We have to integrate and test it. We are currently working on that. I think, it will take some time. The other one was CGI, is that complete as well? Thanks, Samisa... Regards, Shankar. Thanks Nandika On Wed, Oct 8, 2008 at 3:25 PM, Manjula Peiris [EMAIL PROTECTED]mailto: [EMAIL PROTECTED] wrote: On Wed, 2008-10-08 at 14:11 +0530, Samisa Abeysinghe wrote: Subra Aswathanarayanan wrote: Hello, Do you guys know when you are going to release Axis2/C ver 1.6? We have not got any major features to be released as 1.6 right now. In fact, the developer community has not discussed any plans for post 1.5 releases as of now. May be it should be 1.5.1. http://1.5.1./ We have MTOM caching support. This enhanced the functionality of MTOM to send very large attachments with a very low memory usage. Devs, any thoughts... Thanks, Samisa... - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- http://nandikajayawardana.blogspot.com/ WSO2 Inc: http://www.wso2.com No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.7.6/1714 - Release Date: 10/8/2008 7:01 AM -- Samisa Abeysinghe Director, Engineering; WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dumindu Pallewela Cinergix - Share, Reuse, Innovate cinergix.com
Re: axis2c installation with and without SSL
You can use a single client for both http and https, if you provide the ssl configuration in axis2.xml. Regards, Dumindu. On Tue, Sep 23, 2008 at 10:15 PM, Raghu Udupa [EMAIL PROTECTED] wrote: I am writing a web service client that could connect either to a HTTP or HTTPS client. I installed axis2c with and without SSL support. When I see the axis2c/lib directory for with and without SSL support, the shared object files have same names. I need to set the LD_LIBRARY_PATH to point to the correct library path before I run the client. If I set the LD_LIBRARY_PATH to include both SSL and non-SSL paths, at run time, the first path that has required shared object library file will be used. That is, if I specify library path that has SSL library files first, then these files will be used for a non-SSL client as well. Is there a simple way I can resolve this conflict? Or do I need 2 separate clients, one built with SSL axis2c library and the other with regular (non-SSL library)? Thanks, Raghu
Re: User-id/password authentication while using https
Yes the same API can be used for either http or https transports, if you don't use libcurl. Regards, Dumindu. On Fri, Sep 12, 2008 at 12:35 AM, Raghu Udupa [EMAIL PROTECTED] wrote: Thanks Hatim. I am not using libcurl. I wanted to make sure I can use the same API call with https transport as well. Thanks, Raghu -- *From:* Hatim Daginawala [mailto:[EMAIL PROTECTED] *Sent:* Thursday, September 11, 2008 3:00 PM *To:* Apache AXIS C User List *Subject:* RE: User-id/password authentication while using https I think this same call also works for https if you are not using libcurl. If you are using libcurl, I have a patch to get this to work. I can give it to you. -- *From:* Raghu Udupa [mailto:[EMAIL PROTECTED] *Sent:* Thursday, September 11, 2008 1:52 PM *To:* axis-c-user@ws.apache.org *Subject:* User-id/password authentication while using https In axis2c user manual and API documentation, user-id and password authentication appears to be provided only for HTTP protocol as shown in the call below axis2_options_set_http_auth_info( axis2_options_t * options, const axutil_env_t * env, const axis2_char_t * username, const axis2_char_t * password, const axis2_char_t * auth_type); Could you let me know how to do similar validation on https transport? Thanks, Raghu -- --- Confidentiality Notice: This electronic mail transmission is confidential, may be privileged and should be read or retained only by the intended recipient. If you have received this transmission in error, please immediately notify the sender and delete it from your system. -- Dumindu Pallewela Creately.com
Re: SSL Client Authentication Failure
Hi Andy, snip I am having trouble using an SSL Client with AXIS2C - basically, authentication appears to fail. [Thu Jul 3 13:12:57 2008] [debug] http_transport_sender.c(246) ctx_epr: https://localhost:7547/services/ConfigurationServer [Thu Jul 3 13:12:57 2008] [debug] http_transport_sender.c(768) using axis2 native http sender. [Thu Jul 3 13:12:57 2008] [debug] http_sender.c(415) msg_ctx_id:484e90ce-4923-1dd1-20df-00145eecc23a [Thu Jul 3 13:12:57 2008] [info] [ssl client] Client certificate chain filenot specified [Thu Jul 3 13:12:57 2008] [debug] ssl/ssl_utils.c(190) [ssl client] SSL certificate verified against peer [Thu Jul 3 13:12:57 2008] [info] [ssl client] Client certificate chain filenot specified [Thu Jul 3 13:12:57 2008] [debug] ssl/ssl_utils.c(190) [ssl client] SSL certificate verified against peer [Thu Jul 3 13:12:57 2008] [error] http_sender.c(1293) HTTP Authentication failed [Thu Jul 3 13:12:57 2008] [error] http_sender.c(1399) Error occurred in transport [Thu Jul 3 13:12:57 2008] [error] engine.c(179) Transport sender invoke failed snip The debug message SSL certificate verified against peer means that the SSL connection had successfully been established. However, the trouble you are having is about HTTP Authentication. Try pointing your browser to the URL provided, it should ask you for a username/password. That is a HTTP protocol level authentication mechanism which is different from SSL. You can provide HTTP authentication parameters as described in Axis2 Manual [1]. HTH. Dumindu. [1] http://ws.apache.org/axis2/c/docs/axis2c_manual.html#http_auth -- Dumindu Pallewela Cinergix - Share, Reuse, Innovate cinergix.com
Re: How to support HTTPS
Hi Steve, On Fri, May 9, 2008 at 5:18 AM, Steven Zhang [EMAIL PROTECTED] wrote: 1. In util\src\url.c, within axutil_url_parse_string(), the server protocol is compared with http, ftp and smtp. Since there is no https, the port is -1, which cause the server cannot be connected. I have to change the port to 80 manually. Which version of axis2/c are you using? axutil_url_parse_string() doesn't compare the protocol. All it does is to create a axutil_url_t structure corresponding to the string url passed. 2. Even with the socket opened, call for SSL_connect() will be blocked forever, which is called in transport\http\sender\ssl\ssl_utils.c. Could you please explain a bit more? I couldn't understand why this would be so... Btw, have you followed the axis2 manual properly[1]? We have tested the https transport and it works properly. Please go through the manual and send us your error log, so that we will be able to get some insight in to what's going wrong in your setting. Regards, Dumindu. [1] http://ws.apache.org/axis2/c/docs/axis2c_manual.html#ssl_client - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to support HTTPS
On Mon, May 5, 2008 at 11:47 PM, Steven Zhang [EMAIL PROTECTED] wrote: Hi: How to let Axis2c client support HTTPS? There are two ways. You can either provide the parameters in axis2.xml or you can add the relavent properties to the service client. In either case you should un-comment the https transport receiver and https transport sender sections in the axis2.xml You have to provide the CA certificate that was used to sign the server's certificate for the SERVER_CERT parameter. Alternatively if you talk only to a single server you can obtain it's certificate and provide it for the SERVER_CERT parameter. Please refer to the relevant section of axis2 manual [1] for further details. HTH, Dumindu. [1] http://ws.apache.org/axis2/c/docs/axis2c_manual.html#ssl_client -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | Oxygenating the Web Service Platform | http://wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2/C 1.2 breaks my webservice
On Wed, Feb 27, 2008 at 5:50 AM, Subra A Narayanan [EMAIL PROTECTED] wrote: I am running some other tests to see if I can get any further. I will report my findings soon. In the meantime, if you guys can think of ways to track down the problem, please let me know. If you can provide a gdb trace, it would help to figure out where exactly the things go wrong. -Dumindu. -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | Oxygenating the Web Service Platform | http://wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2C] mod_axis2 service shutdown problem
Hi Ben, On Feb 20, 2008 1:40 AM, Ben Wyckoff [EMAIL PROTECTED] wrote: snip Has anyone else run into this issue? Is anyone trying to allocate resources that have to be freed? (In particular, I'm opening a database, and I need to properly close it - I can't just rely on the OS to free memory or close file handles.) /snip This seems to be a problem with mod_axis2. Although the memory allocated with apr_pools will get free'd eventually without free functions being called, in order to free up other resources, we need to register relevant free functions to pool cleanup of a pool which has resource's lifetime. Please add a jira issue. The attached patch should solve this issue when shared memory is not used. I'm not sure if it works when shared memory is used. Hope that someone familiar with axis2c shared memory implementation will look further into it. Regards, Dumindu. -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | Oxygenating the Web Service Platform | http://wso2.com mod_axis2_cleanup_diff Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: version incompatibilities
On Jan 24, 2008 10:37 PM, Samisa Abeysinghe [EMAIL PROTECTED] wrote: Oops! That is a glitch :( We should add this to our check list in the release process Wiki. Devs, should we do a patch release fixing this? I think we should. +1 -Dumindu. -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | Oxygenating the Web Service Platform | http://wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2C] Get peer ip addresswith Apache server
On Jan 19, 2008 12:53 AM, Senaka Fernando [EMAIL PROTECTED] wrote: Sébastien Mougey wrote: How can I get this address with Apache server ? Is it possible ? I think it should be possible, however, I need to look into the code to give you a definite answer. I will have a look and let you know. Yes, indeed it is possible. We need to use ap_get_remote_host(). However, I'm not quite sure what other methods, data are required to call this method, and how we could access them. Looking into that. ap_get_remote_host() tries to lookup the remote server's DNS name. Only if that fails will it return the ip address. You can however get the ip address of the remote host at the axis2_handler as follows: char* remote_ip = req-connection-remote_ip; Regards, Dumindu. -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | Oxygenating the Web Service Platform | http://wso2.com
Re: new line \n is interpreted as AXIOM_TEXT
In addition, IIUC, when mixed content xml is used, this is the proper way to handle it. Regards, Dumindu. On Nov 26, 2007 2:46 PM, Kaushalye Kapuruge [EMAIL PROTECTED] wrote: Hi Atanacio, It is necessary to consider \n as an AXIOM TEXT node. For example, in order to canonicalize an XML node, the new line is required to be considered in that way. Do you have a strong reason to claim this behavior is wrong? Cheers, Kaushalye Atanacio Reyes wrote: Hello: If a message like bellow is send to axis2 server, all '\n' (new line) are interpreted as AXIOM_TEXT node. I think this is wrong. param150/param1 param220/param2 /ns1:add example: param150/param1 is AXIOM_ELEMENT AXIOM_TEXT AXIOM_TEXT param120/param1 is AXIOM_ELEMENT AXIOM_TEXT AXIOM_TEXT Get easy, one-click access to your favorites. Make Yahoo! your homepage. http://www.yahoo.com/r/hs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://blog.kaushalye.org/ http://wso2.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | Oxygenating the Web Service Platform | http://wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] SSL and certificate support
Subra A Narayanan wrote: But when I was reading rampart documentation, it talks about soap body encryption using SSL certs. How is that different from using apache for SSL? To add to my previous reply, *SSL certificate* seems a misnomer when talking about Rampart, and SOAP body encryption. Shouldn't it rather be *x509 certificate*? Any thoughts? -Dumindu. -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform signature.asc Description: OpenPGP digital signature
Re: [Axis2] SSL and certificate support
Subra A Narayanan wrote: Hey Dumindu, Just want to make sure I understand this correctly. So if I just want to run my axis2 webserices in SSL mode, I dont need rampart. I can just use apache for that, right? YES, Absolutely! But when I was reading rampart documentation, it talks about soap body encryption using SSL certs. How is that different from using apache for SSL? SSL/TLS only concerns about the *transport* security. That is Eve in the middle of the channel cannot eavesdrop Bob's private conversation with Alice. :) However if you need more, like message level security, you need WS-Sec. Say you need to store your SOAP message and later consume it. WS-Sec can provide security while it is being stored, whereas SSL/TLS fails to provide that. You can find some more insight to it from Alternatives section of [1] My second question is, lets assume I want to use client authentication for my webservice. I have to set the following 2 variables in the httpd.conf file SSLVerifyClient require SSLVerifyDepth 1 I understand that this will force the client to send a cert with every request. But after receives the client cert, what does it do with it? does it check against a list of certs thats allowed to access the service? Is this feature built-in to axis2 or do we hv to implement it ourselves? Axis2/C does nothing with the client's certificate at the server side. It is up to the user to configure their Apache2 server to accept/reject the clients based on the certificates provided _if_ they need such functionality. Note that Apache2 works as yet another transport and hence we shouldn't be messing around with the transport implementation details at the Axis2/C module level. If for some reason you need to do it in Axis2 code, my guess is that you need a really ugly hack, making it better left with Apache2 (Assuming that you are not considering the situation where you would write the SSL transport support for the server code, i.e., for simple_axis_server). HTH, Dumindu. [1] http://en.wikipedia.org/wiki/Web_Services_Security -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform signature.asc Description: OpenPGP digital signature
Re: issue 731 - please have a look
Kaushalye Kapuruge wrote: Samisa Abeysinghe wrote: Mark Nüßler wrote: hello users, on 26.09.2007 Royston Day found an issue, i just correct my svn-code localy. Can someone have a look - 4 me Royston is right. https://issues.apache.org/jira/browse/AXIS2C-731 I think Rampart folks uses base64 encoding. Can someone using rampart please verify that the proposed code it correct. I tried with the new code and it worked fine for all the scenarios in Rampart/C. But I'm concerned about the interoperability. So it's too early to say that new implementation is correct unless it is inter-operable with other implementations. I'll update on that later. axutil_base64_decode_len() is the same implementation as that of the apr_base64_decode_len() found in libapr. AFAIK, this does not returns the exact decoded length of the encoded string, but returns at least as many number of bytes that is necessary. Exact length is anyway returned by the [axutil/apr]_base64_decode(). Thus, if the length returned from the proposed code is correct, there should be no problems with interoperability. -Dumindu. -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform signature.asc Description: OpenPGP digital signature
Re: Problem with invoking a https based service
Hi Divakar, You don't have to set a userName parameter for https transport to work. If you have encrypted the server key using a password it should be given in the SSL_PASSPHRASE parameter. In addition, AFAIK, userName and password parameters are not at all used in axis2/c. HTH -Dumindu. divakar wrote: Hi All, I am facing some problems with invoking a https based .Net webservice using the axis2c client. I am getting Error code 2. It is giving error cannot find the password for user pbsgridworks\\administrator. How can i set the password to this. I am sending axis.xml ,my .c file and client_policy.xml file. Please check and give reply. Thanks Divakar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform signature.asc Description: OpenPGP digital signature
Re: Axis2/C - USERNAME and PASSWORD
Michael Mole wrote: Yes, that would be much appreciated. Also, is it possible for me to submit these directly? I was looking at the issue tracker, but couldn't find a way to do it. You need to create an account in order to report issues in jira. HTH, Dumindu. -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform signature.asc Description: OpenPGP digital signature
Re: Problem with invoking a https based service
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] -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform signature.asc Description: OpenPGP digital signature
Re: Problem with invoking a https based service
Manjula Peiris wrote: Hi Divakar, You have not set the ca-cert in the axis2.xml. You need to set the following parameter in the axis2.xml. parameter name=SERVER_CERT/path/to/ca/certificate/parameter This is not necessary as the SERVER_CERT has been set in the client code. -Dumindu. signature.asc Description: OpenPGP digital signature
Re: Axis2/C - USERNAME and PASSWORD
Hi Mole, Currently the auth header is sent only if the server requests for it. So if your server sends a WWW-Authenticate: header when authentication failed at the first request, Axis2 will send another with the required header. However, I think we should have allowed the user to send the auth header without waiting for a failed response in the first place, because it is only an additional overhead, if the user already *knows* that the server requires basic auth, Somehow we missed it from 1.1 release :( Regards, Dumindu. Michael Mole wrote: I tried to run echo.c using the Axis2C 1.1 release, but I'm not seeing the basic http authorization in the http headers. I'm expecting to see something like Authorization: Basic YJKLa35. I'm using tcp monitor to check the outgoing message (shown below). Is there something else I have to do to get this to work? *This is my command:* C:\axis2c-src-1.1.0\build\deploy\bin\samplesecho.exe -auth user pass *This is the outgoing message:* POST /axis2/services/echo HTTP/1.1 User-Agent: Axis2/C Content-Length: 512 Content-Type: application/soap+xml;charset=UTF-8 Host: localhost:9090 soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header xmlns:wsa=http://www.w3.org/2005/08/addressing; wsa:Tohttp://localhost:9091/axis2/services/echo/wsa:To wsa:Actionhttp://ws.apache.org/axis2/c/samples/echoString/wsa:Action wsa:MessageID4ecf636a-5637-4be9-afe4-80e80f0e3117/wsa:MessageID /soapenv:Header soapenv:Body ns1:echoString xmlns:ns1=http://ws.apache.org/axis2/services/echo; textHello World!/text /ns1:echoString /soapenv:Body/soapenv:Envelope Thanks, Mike Michael J Molé Software Engineer IBM Software Group - Rational (781)676-2710 *Dumindu Pallewela [EMAIL PROTECTED]* 08/13/2007 07:38 AM Please respond to Apache AXIS C User List axis-c-user@ws.apache.org To Apache AXIS C User List axis-c-user@ws.apache.org cc Michael Mole/Lexington/[EMAIL PROTECTED] Subject Re: Axis2/C - USERNAME and PASSWORD Michael Mole wrote: I'm looking for more information about AXIS2_USER_NAME and AXIS2_PASSWORD in axis2_const.h. What are they used for, and how are they used? I'm still trying to solve my issue of using Basic http Authentication with my web services, and these look like they may be the key. Any help is greatly appreciated. We have added HTTP basic authentication support for axis2/c client. All you have to do is to set the two properties HTTP_AUTH_USERNAME and HTTP_AUTH_PASSWD in your client code. Please refer to echo.c [1] for a sample of its usage. I propose that we remove the AXIS2_USER_NAME and AXIS2_PASSWORD declarations as they are not being used. HTTP authentication related declarations can be found in axis2_http_transport.h. Regards, Dumindu. [1] http://svn.apache.org/viewvc/webservices/axis2/trunk/c/samples/client/echo/echo.c?view=markup - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform signature.asc Description: OpenPGP digital signature
Re: Problem with SVC client send_receieve method
Hi Murali, This doesn't seem to me as a problem with ssl client. It rather is something to do with your rampart configuration. AFAIK, it is not correct to set the user name in axis2.xml. It has to be done with security policy. HTH, Dumindu. Murali Konnipati wrote: Hi Dumindu, Thank you very much for your reply. As per your email, i enabled https transportsender in my axis2.xml. Even then, i am facing the same problem.. I am attaching the log file configuration file for your reference. Please check the same and let me know, if i am making any mistake in the configuration. Thanks Regards, Murali Krishna K -Original Message- From: Dumindu Pallewela To: Apache AXIS C User List Sent: 9/25/07 4:58 PM Subject: Re: Problem with SVC client send_receieve method Murali Konnipati wrote: But in the code, i have set the SERVER_CERT parameter. Do i need to set in the axis2.xml configuration file as well .. No you don't :) But you need to have the following: transportSender name=https class=axis2_http_sender parameter name=PROTOCOL locked=falseHTTP/1.1/parameter /transportSender Regards, Dumindu. SMIME.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] signature.asc Description: OpenPGP digital signature
Re: How to develop a HTTPs-based webservice client
Hi Murali, If you want to set the properties required for HTTPS transport, in your client code, please do the following: axutil_property_t *prop_sc = axutil_property_create(env); axutil_property_set_value(prop_sc, env, axutil_strdup(env, /path/to/server/cert)); axis2_options_set_property(options, env, SERVER_CERT, prop_sc); where *options* is the *axis2_options_t* structure that you set to the service client using *axis2_svc_client_set_options* function, or to the operation client using *axis2_op_client_set_options* function. Refer to the echo sample client's http authentication section for a sample on similar code fragment [echo.c lines 115-125]. Note that it does not depend on whether the service client or operation client is used to send the request. Other properties, if necessary, can be set in an identical manner. Property names are KEY_FILE and SSL_PASSPHRASE as described in axis2c manual [1]. HTH, -Dumindu. [1] http://ws.apache.org/axis2/c/docs/axis2c_manual.html#ssl_client Murali Konnipati wrote: Thank you Dinesh. I will try to submit a small job and let you know, if i face any issues. Thanks Regards, Murali Krishna K -Original Message- From: Dinesh Premalal To: axis-c-user@ws.apache.org Cc: Dinesh Premalal ; Dinesh Premalal Sent: 9/23/07 1:32 AM Subject: Re: How to develop a HTTPs-based webservice client Murali, Murali Konnipati [EMAIL PROTECTED] writes: As i have to modify the SOAP envelope, i am planning to use the Operation Client instead of Service Client. Can you please send me any document with some examples on https web service client, which can provide some useful information. It doesn't matter whether you use svc_client or op_client to send your request. HTTPS handled by Axis2/C transport layer which is independent from the client api that you use. I'm afraid that I don't have any examples in my hand. I think axis2c manual's description is descriptive enough. thanks, Dinesh -- Dinesh Premalal http://xydinesh.wordpress.com/ GPG ID : A255955C GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] signature.asc Description: OpenPGP digital signature
Re: [Axis2] 1.1.0 Feature list
Http Authentication does work, however, with known performance issues. Thus, I think we should not add it as a new feature yet. -Dumindu. Manjula Peiris wrote: Basic Http Authentication support can be added to it. Other than that the list is ok to me. Thanks. -Manjula. On Thu, 2007-08-30 at 14:31 +0600, Samisa Abeysinghe wrote: I have updated the wiki: http://wiki.apache.org/ws/FrontPage/Axis2C/releases/1.1.0 Please look into that and see if I have missed anything, specially new features. Thanks, Samisa... - 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]
Re: Regarding use of Proxy and error thereof
When I use the axis2C as dlls from another process, It's not clear to me what you mean by as dlls. and use proxy, I get the following error: Input stream is NULL in msg_ctx This is most likely due to the proxy setting in your axis2.xml being incorrect. Have you added the proxy parameter under the transportSender element in axis2.xml? If not, please refer to the axis2 manual [1]. HTH -Dumindu. [1] http://ws.apache.org/axis2/c/docs/axis2c_manual.html#proxy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axiom Questions
Subra A Narayanan wrote: Hey Kaushalye, I noticed that ip_stream is of type axis2_byte_t. Looking at the definition of axis2_byte_t in axutil_utils_defines.h, I realized that it is nothing but a char. I am wondering if I read a part of a binary file from disk using pread and store the read data in void *buffer and then type cast the buffer in to a axis2_byte_t, if that will cause a problem? It should not. Because you give the length of the buffer alongside the buffer itself. FYI, the axiom_data_handler_set_binary_data function signature is as follows: axiom_data_handler_set_binary_data( axiom_data_handler_t *data_handler, const axutil_env_t *env, axis2_byte_t* input_stream, int input_stream_len) BTW, you could try this out and see for yourself ;) -Dumindu. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2/C - USERNAME and PASSWORD
We have not released Axis2/C after HTTP Authentication was added. You may use the current svn trunk [1] if you prefer. -Dumindu. [1] https://svn.apache.org/repos/asf/webservices/axis2/trunk/c Michael Mole wrote: That's great news! Is there a version where I should be able to pick up those changes? Thanks, Mike Michael J Molé Software Engineer IBM Software Group - Rational (781)676-2710 *Dumindu Pallewela [EMAIL PROTECTED]* 08/13/2007 07:38 AM Please respond to Apache AXIS C User List axis-c-user@ws.apache.org To Apache AXIS C User List axis-c-user@ws.apache.org cc Michael Mole/Lexington/[EMAIL PROTECTED] Subject Re: Axis2/C - USERNAME and PASSWORD Michael Mole wrote: I'm looking for more information about AXIS2_USER_NAME and AXIS2_PASSWORD in axis2_const.h. What are they used for, and how are they used? I'm still trying to solve my issue of using Basic http Authentication with my web services, and these look like they may be the key. Any help is greatly appreciated. We have added HTTP basic authentication support for axis2/c client. All you have to do is to set the two properties HTTP_AUTH_USERNAME and HTTP_AUTH_PASSWD in your client code. Please refer to echo.c [1] for a sample of its usage. I propose that we remove the AXIS2_USER_NAME and AXIS2_PASSWORD declarations as they are not being used. HTTP authentication related declarations can be found in axis2_http_transport.h. Regards, Dumindu. [1] http://svn.apache.org/viewvc/webservices/axis2/trunk/c/samples/client/echo/echo.c?view=markup - 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]
Re: Axis2/C - USERNAME and PASSWORD
Samisa Abeysinghe wrote: Dumindu Pallewela wrote: We have not released Axis2/C after HTTP Authentication was added. You may use the current svn trunk [1] if you prefer. Lets pack a nightly build so that they could pick up the source. I can even do an RC1 of 1.1 today. +1 -Dumindu. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using AXIS2C from scripting environment
Yuvaraj Athur Raghuvir wrote: Can you also tell me the location from where I can download the following? a) libapr-1.lib apr-1.lib libhttpd.lib associated dlls These libs are in the lib/ directory of your apache installation. DLLs can be found inside bin/ directory. You can download apache win32 binaries from: http://www.apache.org/dist/httpd/binaries/win32/ b) libcurl_imp.lib associated dlls [should I choose with SSL or without?] We don't have SSL support for libcurl transport yet. :( However, we do have our own client SSL transport. Anyway you can find the libs in the directory you extracted libcurl package, if you downloaded it from the official site. Whether to build with SSL or without, is up to you and depends on your requirement. c) httpd.lib associated dlls Same as in a). d) ssl ( I have got the installation from Shining Light Productions - is this ok)? As far as it contains the necessary libs, it is fine :) Regards, Dumindu. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTTP headers
Samisa Abeysinghe wrote: AXIOM_SOAP12 is defined as a member of enum with value 2. AXIOM_SOAP_12 is defined as a constant with value 1 This was the root cause of the problem. We cannot just delete the constant AXIOM_SOAP_12 and AXIOM_SOAP_11, rather deprecate it in the next release and then remove those later. Till then we can fix the problem by changing the value to represent the correct value and also fixing the doc. Shouldn't axis2_options_get_soap_version() ideally be returning an axiom_soap_version? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTTP headers
Stefano Pettini wrote: 2) What I think is a bug in the Win32 makefile. I had to compile Axis since I needed HTTPS support. Official binaries worked well, but mine not. I compiled with DEBUG=1 and I noticed the makefile didn't specify which C Runtime to use. This caused the single-threading C runtime to be implicitly linked, generating random crashes during calls of C runtime functions from more than one thread. I solved the problem replacing part of the code of the makefile with the following: This is probably because you are using Visual Studio 6 as you have mentioned elsewhere. /MLd option, which instructs the compiler to use single threaded debug c runtime, libcd.lib, is the default for VS6. /ML and /MLd options are no longer available in VS2005 [1]. C runtimes shipped with VS2005 are all multi threaded. That should be the reason why dist binaries worked fine. (Our dist is compiled using VS2005) debug symbols !if $(DEBUG) == 1 CFLAGS = $(CFLAGS) /D _DEBUG /Od /Z7 /MDd LDFLAGS = $(LDFLAGS) /DEBUG !else CFLAGS = $(CFLAGS) /D NDEBUG /O2 /MD LDFLAGS = $(LDFLAGS) !endif The DEBUG=1 case must specify the /MDd parameter, to link to MSVCRTD.dll in multithreading mode. The ignore library parameter of the linker is removed too. I modified also the DEBUG=0 case, replacing /MT with /MD to link to MSVCRT.dll. /MTd and /MT could be used instead of /MDd and /MD to link the runtime library statically, but I suggest dynamic linking, since it's used as default by VS6 and by libxml2, zlib, iconv and openssl. May you include these modifications in 1.1? Pathed makefile is attached. I think we should add this. It is good to have our build working properly with older versions of VS compilers too. -Dumindu. [1] http://msdn2.microsoft.com/en-us/library/ms235505(VS.80).aspx - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to create a SSL client to support https
Hi Kelvin, Find my comments inline. Kelvin Lin wrote: Hi all, But it failed in my environment, because I can't find some apis and variable name at all, like axis2_property_t and AXIS2_OPTIONS_SET_PROPERTY. Those instructions were intended for v0.96. Since v1.0 the util declarations were renamed with a axutil_ prefix and the macros were dropped. Hence these should be axutil_property_t and axis2_options_set_property respectively. I used official version axis2c-src-1.0.0 and changed axis2.xml like: transportSender name=https class=axis2_http_sender parameter name=PROTOCOL locked=falseHTTP/1.1/parameter /transportSender parameter name=SERVER_CERT/path/to/ca/certificate/parameter !--parameter name=KEY_FILE/path/to/client/certificate/chain/file/parameter parameter name=SSL_PASSPHRASEpassphrase/parameter -- This is all you need in order to get ssl working, usually. :) At the same time, I called following apis in my program: axis2_options_set_soap_version(options, env, AXIOM_SOAP12); axis2_options_set_transport_in_protocol(options, env, AXIS2_TRANSPORT_ENUM_HTTPS); Axis2 engine should set the appropriate protocols according to the epr that you use. For example for a https endpoint, axis2 engine would look at the https:// uri and understand that the protocol that should be used is https. In particular, setting transport_in protocol is not useful if you are not using different ports to send and receive messages (dual client). But the server I built by myself didn't have any response and get error code 82, Input stream is NULL in msg_ctx. That is because our simple_axis_server is not capable of handling ssl. Please refer to the axis2 manual [1] for more information on deploying axis2 in apache2 server. Make sure to have mod_ssl installed. What apis should I call to support https and how to config axis2.xml to specify pem file both under needing authentication and no needing authentication? There are three properties that are related to ssl transport, SERVER_CERT, KEY_FILE and SSL_PASSPHRASE. Please refer to [2] for more information on each. This is how you set the SERVER_CERT for expample: axutil_property_t ssl_ca_file = axutil_property_create(env); axutil_property_set_value(ssl_ca_file, env, axutil_strdup(env, /home/dumindu/dummyCA/demoCA/cacert.pem)); axis2_options_set_property(options, env, SERVER_CERT, ssl_ca_file); You can set the other three properties accordingly, too. These properties however, are *not needed* to be set in the code, if you can set them in axis2.xml. Tutorial [2] was written a while back, so there can be a few errors. Please let me know if you find any :) Regards, Dumindu. [1] http://ws.apache.org/axis2/c/docs/axis2c_manual.html#mod_axis2 [2] http://people.apache.org/~dumindu/HowToConfigureSSL.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2 c help : problem
Hi Samitha, Find my comments inline. -Dumindu. samitha kumara wrote: axis2c installation guide states that it needs to download the Microsoft VSExpress2005 edition and Platform SDK. There the VSExpress2005 edition is a pack of : visual c#, visual web developer,visual c++. it makes the downloading quite confusing. any suggestions for this. If you have Visual Studio 2005 (not the express edition) you don't need to download the platform sdk. because axis2c requires only single bat file (vsvars32.bat) as it states. It is not the case, vsvars32.bat only sets the environment needed in order nmake to work properly. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Does Axis2/C client has the ability to set the session management?
Hi Wang, My understanding is that it does not, but facilitates such implementation. Please refer to the following thread [1]. Regards, Dumindu. [1] http://marc.info/?l=axis-c-userm=118224624421829w=2 Wang, Hailong (NIH/CIT) [C] wrote: Hi, I have a web service written in Java and use the soapsession management. Right now I want to create a client using Axis2/C. Is Axis2/C client able to mange session? Thanks in advance. **Hailong Wang** National Database for Autism Research(NDAR) NIH/CIT/DECA (MOM CONTRACTOR) 9000 Rockville Pike, Bld 12A/Room 2027 Bethesda, MD 20892 Phone: 301-402-3045 Fax: 301-480-0028 Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] URL: http://ndar.nih.gov - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2C]: How to implement business logic in C++?
Yingwei Yang wrote: Hi Dumindu, After several tries, I found out the segmentation error is because I updated the libhello.so file but didn't restart the axis2_http_server. It is not a permission issue. That's good news :) Thanks for the feedback. -Dumindu. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2C]: How to implement business logic in C++?
Yingwei Yang wrote: Hi Dinesh, Thank you very much for the reply. I just realized that I didn't run the axis2_http_server with the correct permission, which caused the error I mentioned above. and no log files been written because of the lack of permission. Hi Yang and Dinesh, I don't think that the axis2_http_server should seg fault on a permissions issue. When I try to run the server without write permissions for log file, it instead is written to the standard output. I guess that this _might_ possibly be a bug. If you could please provide more details on how the seg fault could be recreated. -Dumindu. Now it runs fine. :) Thanks. On 6/11/07, *Dinesh Premalal* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi Yingwei, Yingwei Yang [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] writes: then I got the Segmentation fault at the Invoke the handler context_handler within the phase PostDispatch phase. what did I do wrong? is it possible to implement the service skeleton code in C++? I think it is possible, in order to determine what has happened in your case we need some more details. 1. Are you sure about your service.xml ? What is the directory name that you use to put your service? 2. Can you provide us your axis2.log , Please make sure to run server in debug mode. 3. It would be great if you could send us gdb backtrace. thanks, Dinesh -- Dinesh Premalal http://xydinesh.wordpress.com GPG ID : A255955C GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- Yingwei Yang - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] SSL and certificate support
Greg Denton wrote: Note that ssl transport is not a feature of rampart, but of Axis2/C itself. Just to confirm, the documentation seems to imply that SSL transport is not a part of Axis2/C server-side (I guess this would be the simple axis server) only client. For server-side, apache must be used, correct? Yes, simple_axis_server is incapable of handling SSL requests. What I meant by saying that the SSL transport is a feature of Axis2/C is that Rampart has nothing to do with the SSL transport (yet). Sorry if it was misleading. I found the client certificate info in the new docs, thanks. IIRC, SSL Client authentication is a post-0.96 feature. It will be updated in the site with the next release. Regards, Dumindu. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] SSL and certificate support
Please use the correct prefix... Dumindu. Greg Denton wrote: Sorry if this is in some documentation somewhere (I’ve tried and not found if). A cursory glance at the rampart code shows a lot of references to ssl and certificates. Some specific questions: Is SSL supported on server side? Client? Are client side certificates (i.e. server-requested client authentication via certificates) supported on the server side? Client? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: about https supports
Hi Kixiong, Are you using the 0.96 sources? IIRC, those files were not included in that release. Please try the axis2 1.0 RC2. You can get it from http://people.apache.org/~samisa/release/1.0.0/RC2/ FYI: Yes Axis2/C supports both client and server ssl transports. For server side ssl transport however, you need to deploy axis2 as a module in apache2. Regards, Dumindu. 黄启雄 wrote: Hello, every body! When I try to compile the Axis2C with parameter --enable-openssl=yes , I found that the source of Axis2C is less of ssl_stream.h.The compile error message like this : http_client.c:29:28: ssl/ssl_stream.h: No such file or directory. My question is that : Dose Axis2C supports https ? If yes, when it will support https completely, here completely I mean it should include server side and client side supports? Thanks a lot Kixiong 4/18/2007 - 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]
Re: about https supports
黄启雄 wrote: Thanks to apply. I have checked my compile environment, I am sure I have installed the openssl. But in the path(/usr/include/openssl) , I can't find the file ssl_stream.h. Dose the file ssl_stream.h belong to openssl or Axis2C ? Will Axis2C consider to be a https stand-alone server rather than to be a module of apache server? ssl_stream.h belongs to Axis2/C. please refer to my previous message. Dumindu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
