Re: How to create a SSL client to support https
Hi Dumindu, As per your suggestions if client won't need any authentication, only SERVER_CERT is required. I am not sure why SERVER_CERT also required. Here server certificate may expire and so on. Is it easy to make changes in src\core\transport\http\sender\ssl\ssl_utils.c for SSL_VERIFY_NONE?? I don't want any type of validation for client. Thanks in Advance. Thanks, Ashok Dumindu Pallewela wrote: Hi Kelvin, If you didn't know this already: You do *not* have to set ssl parameters *both* in axis2.xml and in your client code. We have given the user the option to choose which he prefers. Please further comments inline. Regards, Dumindu. In short, I configure axis2.xml as: transportSender name=https class=axis2_http_sender parameter name=PROTOCOL locked=falseHTTP/1.1/parameter /transportSender !--parameter name=SERVER_CERTE:/Project/VS8/Axis2_prototype/debug/TrustList.pem/parameter-- !--parameter name=KEY_FILEE:\Project\VS8\Axis2_prototype\debug\TrustList.pem/parameter parameter name=SSL_PASSPHRASEpassphrase/parameter-- !-- -- tag in XML makes whatever it encloses a comment. Thus, in the above, SERVER_CERT parameter is not set. Only the client key's pass phrase, which you don't need, is set from the above configuration. Since you have mentioned that you don't need client authentication, please remove the last two lines, so that you don't have unnecessary stuff: transportSender name=https class=axis2_http_sender parameter name=PROTOCOL locked=falseHTTP/1.1/parameter /transportSender parameter name=SERVER_CERTE:/Project/VS8/Axis2_prototype/debug/TrustList.pem/parameter Then run your axis client making sure that the AXIS2C_HOME is set to the directory where the now edited axis2.xml resides. Also your epr should start with https:// If this doesn't work, there is no point in trying setting these parameters in client code. And I create TrustList.pem file following the manual of Axis2/C: For testing purposes, you can use the server's certificate instead of the CA certificate. You can obtain this by running the command |openssl s_client -connect servername:port| and copying the portion of the output bounded by and including: -BEGIN CERTIFICATE- -END CERTIFICATE- Get the content of this file is: -BEGIN CERTIFICATE- MIIB7TCCAVagAwIBAgIEPygs+DANBgkqhkiG9w0BAQQFADA7MQswCQYDVQQGEwJV UzEMMAoGA1UEChMDSUJNMQwwCgYDVQQLEwNTV0cxEDAOBgNVBAMTB2pzZXJ2ZXIw HhcNMDMwNzMwMjAzOTIwWhcNMjExMDEzMjAzOTIwWjA7MQswCQYDVQQGEwJVUzEM MAoGA1UEChMDSUJNMQwwCgYDVQQLEwNTV0cxEDAOBgNVBAMTB2pzZXJ2ZXIwgZ8w DQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAIQhMysAHrupK8YLnu54xipwbYfJw1ac xMSNQPphN2ZQEznGNp1E8tONwN4RJ4nCW/5mQRFkErOUJW3ZQKP/gwK37HwKz1+V OVOlQ9fitArsnEZTeqzdmBLa+vx7B7bZ8bIRPzI0CeWgQiYZZjSCsZz8JcQZxLM6 ob9mKE28VeZvAgMBAAEwDQYJKoZIhvcNAQEEBQADgYEAEPCRwEUBxz6+9A5/AoPB LiYInrowLfY+w3xJyDCie+GneLnirL+1HXRBbNOJYQTCpzN00Cgq2M/LU6tUeeZQ 3gwidiqFUculi2Z+8wd60q8vy6qdJ1kvg9atwMdQV2LFf7TPNccmULD9/LV9h3AV oBbsFukZAroF0ZvO+/4vrIk= -END CERTIFICATE- This is fine. My colleague once tried to send soap message created by gsoap, although the message itself is wrong. But he still get some error message back and in the console of the server, there are some error messages like I mentioned before. can you send those error messages? even if that is not axis2 we may be able to get an idea about what's going wrong. - To unsubscribe, e-mail: axis-c-user-unsubscr...@ws.apache.org For additional commands, e-mail: axis-c-user-h...@ws.apache.org -- View this message in context: http://old.nabble.com/How-to-create-a-SSL-client-to-support-https-tp11441745p27621164.html Sent from the Axis - C++ - User mailing list archive at Nabble.com.
Re: RE : Need suggestions on Axis/c client stub
Thanks to all for suggestions and inputs. Any suggestions on point-1 - data type mapping? for example if you check typemap.dat in case of gsoap which gives us a easy way to map data types. I am planning to take a look on code generation source code. Will it work if I change for data types? I will update on point 5 and 6 as I started investigations on it. /// Ashok Nadir Amra wrote: Axis-C++ client-side is not broken or buggy. It is perfectly functional and in some cases much easier to use than axis2/C. Nadir Amra Olivier Mengué omen...@oxymel.com wrote on 02/10/2010 04:41:51 AM: [image removed] RE : Need suggestions on Axis/c client stub Olivier Mengué to: Apache AXIS C User List 02/10/2010 04:42 AM Please respond to Apache AXIS C User List Hi I'm a recent Axis2/C user. I don't know about Axis-C/C++. Ashok P wrote: . . . 7) Axis-C++ is not recommended for production use. Does I need to test client generated (stub) for stability considering the recommendation? Any suggestions on axis-c++ clients to be used on production? Otherwise I need go with axis-c only. The recommandation is to use Axis2/C (which is not axis-c). I understood it as Axis-C++ is buggy and is broken by design, we choose to rewrite everything as Axis2/C. Is it really the case? I don't know. That is just the feeling I got by reading the site. Olivier Mengué -- View this message in context: http://old.nabble.com/Need-suggestions-on-Axis-c-client-stub-tp27518586p27542741.html Sent from the Axis - C++ - User mailing list archive at Nabble.com.
Need suggestions on Axis/c client stub
I want to clear my understandings about axis-c/c++. I got few answers in email archives and like to understand thoroughly. Newbie to Axis-c.. :) I apologize for any repeated questions. 1) Can I provide custom mappings for C/C++ data types for code generation tool? Wsdl2c/wsd2ws generates the code for xs:string as “char* (axis-char)” and “std::string” respectively. Is there any way to mention mapping like “wchar*” or std::wstring (c++) to toolkit considering Unicode enabled project? Does char* processing problematic in case of Unicode string? 2) My requirement is to generate the clients for non-axis web services like .net, JBOSS-WS, etc. So Is there any limitations for such clients? I believe all web services can easily consumed with axis/c client considering they adhere with WSDL specifications. 3) As per the documentation, axis-c supports “ADB” binding for client code generations and “none” option for raw xml in/out. Is ADB is efficient to consume non-axis web services? 4) As per analysis, wsdl2c can generate client code for RPC/document literal styles only. Am I correct? Is there any support available for RPC-encoded style in near feature? 5) Does it mandatory to use axis2.xml? I like all these settings through code by settings the options – like settings the protocol “http” or https (ssl), port , ssl certificate, client timeout and more. Does such provision is available in both C/C++ client generated code? 6) From the other posting on forum, it’s not clear that “AXIS2C_HOME” deplorer folder is mandatory or not for client side. Can anybody confirm this? I agree few Dlls are required for client distribution. I like my client application (along with client stub) should have small footprint for distribution, so can I build stub statically for depended libraries like axiom.dll, axis2_http_sender.dll etc? 7) Axis-C++ is not recommended for production use. Does I need to test client generated (stub) for stability considering the recommendation? Any suggestions on axis-c++ clients to be used on production? Otherwise I need go with axis-c only. Thanks in advance and appreciate your help. -- View this message in context: http://old.nabble.com/Need-suggestions-on-Axis-c-client-stub-tp27518586p27518586.html Sent from the Axis - C++ - User mailing list archive at Nabble.com.
Re: Need suggestions on Axis/c client stub
Thanks Nadir and Paul for your quick response and valuable inputs.Now I have got confidence to go ahead... I got my sample clients working with axis/c and c++ on windows. I believe that I will get answers for my other questions also. Nadir Amra wrote: As far as the Axis-C++ client, it is recommended for production useas long as you build the client from the latest code in SVN. But ensure that it supports what you need supported, which is WSDL 1.1 and SOAP 1.1. Nadir Amra Ashok P ashvit...@gmail.com wrote on 02/09/2010 11:09:09 AM: [image removed] Need suggestions on Axis/c client stub Ashok P to: axis-c-user 02/09/2010 11:09 AM Please respond to Apache AXIS C User List I want to clear my understandings about axis-c/c++. I got few answers in email archives and like to understand thoroughly. Newbie to Axis-c.. :) I apologize for any repeated questions. 1) Can I provide custom mappings for C/C++ data types for code generation tool? Wsdl2c/wsd2ws generates the code for xs:string as ?char* (axis-char)? and ?std::string? respectively. Is there any way to mention mapping like ?wchar*? or std::wstring (c++) to toolkit considering Unicode enabled project? Does char* processing problematic in case of Unicode string? 2) My requirement is to generate the clients for non-axis web services like .net, JBOSS-WS, etc. So Is there any limitations for such clients? I believe all web services can easily consumed with axis/c client considering they adhere with WSDL specifications. 3) As per the documentation, axis-c supports ?ADB? binding for client code generations and ?none? option for raw xml in/out. Is ADB is efficient to consume non-axis web services? 4) As per analysis, wsdl2c can generate client code for RPC/document literal styles only. Am I correct? Is there any support available for RPC-encoded style in near feature? 5) Does it mandatory to use axis2.xml? I like all these settings through code by settings the options ? like settings the protocol ?http? or https (ssl), port , ssl certificate, client timeout and more. Does such provision is available in both C/C++ client generated code? 6) From the other posting on forum, it?s not clear that ?AXIS2C_HOME? deplorer folder is mandatory or not for client side. Can anybody confirm this? I agree few Dlls are required for client distribution. I like my client application (along with client stub) should have small footprint for distribution, so can I build stub statically for depended libraries like axiom.dll, axis2_http_sender.dll etc? 7) Axis-C++ is not recommended for production use. Does I need to test client generated (stub) for stability considering the recommendation? Any suggestions on axis-c++ clients to be used on production? Otherwise I need go with axis-c only. Thanks in advance and appreciate your help. -- View this message in context: http://old.nabble.com/Need- suggestions-on-Axis-c-client-stub-tp27518586p27518586.html Sent from the Axis - C++ - User mailing list archive at Nabble.com. -- View this message in context: http://old.nabble.com/Need-suggestions-on-Axis-c-client-stub-tp27518586p27526468.html Sent from the Axis - C++ - User mailing list archive at Nabble.com.
