We have developed a Single Sign-On Gateway URL web service using java axis, with stubs generated from the wsdl you provide on Salesforce. I have no problems running this using HTTP. When I turn on HTTPS, it says that the authentication service is down. I use a trusted real cert from thawte.
Single Sign-On Gateway URL's set for my demo company: HTTP: http://www.nordicedge.se:82/salesforce/services/AuthenticationService
Both URL's use the same webservice and are accesible from the Internet. Any idéas? Do I need to change something in the webservice itself to support HTTPS? I earlier used a self-signed cert, could that be cached somehow on Salesforce? Is it the port numbers?
We have developed a Single Sign-On Gateway URL web service using java axis, with stubs generated from the wsdl you provide on Salesforce. I have no problems running this using HTTP. When I turn on HTTPS, it says that the authentication service is down. I use a trusted real cert from thawte.
Single Sign-On Gateway URL's set for my demo company: HTTP: http://www.nordicedge.se:82/salesforce/services/AuthenticationService
Both URL's use the same webservice and are accesible from the Internet. Any idéas? Do I need to change something in the webservice itself to support HTTPS? I earlier used a self-signed cert, could that be cached somehow on Salesforce? Is it the port numbers?
