M
Michael Jacobs
Guest
Based on your list of options, you may not be using the correct ones. Your list of options tells the CONNECT operation to retrieve the WSDL document without using either HTTP BASIC or TLS client certificate authentication, and then try to call the Web Service using TLS client certificate authentication using the default key-file and password. Did you make sure the default key-file is present in DLC/keys and has the expected password? The CONNECT has two sets of TLS client certificate configuration options: a) retrieve the WSDL: -WSDL -WSDLAuth ssl -WSDLKeyFile -WSDLKeyPwd b) call the Web Service: -SSLAuth ssl -SSLKeyFile -SSLKeyPwd ... If your options list is correct, and the default key-file is accessible, you would have to turn on the debug options for SSL/TLS connections in the ABL and see exactly why the connection was rejected. The debug output is pretty detailed, but generally provides better information for TLS connection problems than the SOAP error detail. Hope this helps
Continue reading...
Continue reading...