B
Brian K. Maher
Guest
Assuming I would be able to access the web service from here, send the certificate along with the sample code you are using. If I won’t be able to connect to the web service, take a look at this KB article ... http://knowledgebase.progress.com/articles/Article/Connection-failure-with-SSL-socket-to-secure-developer-server And use the curl commands shown to figure out what cipher(s) are acceptable to the web service. Also, be aware that having just “the certificate” may not be enough. We also need all of the certificates up the chain to be available in our certificate store (and I have seen some one service that had a chain where there were eleven certificates in the chain). You can get more details on that by using the sslc command (run from a proenv command prompt). The command would be something like the following: sslc s_client -host somehost -port someport showcerts -debug to save the output from this command you can add -sess_out somefilename
Continue reading...
Continue reading...