This is not a bug ,but mostly related on how you configure your web server for SSL.
First make sure you have configured your web server for SSL .if you didn't yet configured your server to use SSL see how to do that in this tutorial : http://onlamp.com/pub/a/onlamp/2008/03/04/step-by-step-configuring-ssl-under-apache.html
Now if you use a trusted CA you will be able to connect to sugarcrm soap service through https without problem.
However if you use a self-signed certificate , your Java JRE will need to know about your private self-signed ssl certificate. the trick is to add your Self-signed certificate to your JDK keystore. this tutorial explains how you can do this :http://brian.pontarelli.com/2008/07/26/java-ssl-and-self-signed-certificates/
Currently this is the workaround for enabling https connection with self-signed SSL certificates..we are planning to add more smart SSL connection functionality in future..but it will take some time.
Regards.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is not a bug ,but mostly related on how you configure your web server for SSL.
First make sure you have configured your web server for SSL .if you didn't yet configured your server to use SSL see how to do that in this tutorial : http://onlamp.com/pub/a/onlamp/2008/03/04/step-by-step-configuring-ssl-under-apache.html
Now if you use a trusted CA you will be able to connect to sugarcrm soap service through https without problem.
However if you use a self-signed certificate , your Java JRE will need to know about your private self-signed ssl certificate. the trick is to add your Self-signed certificate to your JDK keystore. this tutorial explains how you can do this :http://brian.pontarelli.com/2008/07/26/java-ssl-and-self-signed-certificates/
Currently this is the workaround for enabling https connection with self-signed SSL certificates..we are planning to add more smart SSL connection functionality in future..but it will take some time.
Regards.