What steps will reproduce the problem? 1. Trying to connect to a HTTPS SOAP webservice (like https://195.1.61.153/awsh/service.svc) and allow an app to use secure connection through HttpsTransportSE instead of HttpTransportSE.
What is the expected output? What do you see instead? Expected output is allowing app to connect to it. We are getting the issue hostname not verified
What version of the product are you using? On what operating system? Any product and any Android OS
Please provide any additional information below. As a workaround, I'm accepting all certificates, but it is not ok as the final solution
Comment #1
Posted on Oct 17, 2012 by Grumpy BearAny idea about how to solve it?
Comment #2
Posted on Oct 18, 2012 by Swift HippoHow is the server setup in terms of https? are you using a self signed certificate or a proper one?
Comment #3
Posted on Oct 18, 2012 by Grumpy BearA self signed certificate (find attached)
- usercert.pfx 2.36KB
Comment #4
Posted on Oct 18, 2012 by Swift HippoFor a self signed certificate I believe you have to follow the approach Bob is suggesting here http://blog.crazybob.org/2010/02/android-trusting-ssl-certificates.html
It essentially not related to ksoap2 but rather to the ssl stack of android itself..
Comment #5
Posted on Oct 18, 2012 by Grumpy BearBut, is there any possibility to do in a General way? I mean, I'm using my own self-signed certificate, but I would like to consider any server with any self-signed certificate o signed certificate (by CA authority).
Status: Invalid
Labels:
Type-Defect
Priority-Medium