Feedback
 
Did this article resolve your question/issue?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025

 


Article

OpenEdge Secure Socket connection fails with error 9318

« Go Back

Information

 
Article Number000011557
EnvironmentProduct: OpenEdge
Version 10.1x, 11.x
Product: Progress
Version: 9.x
OS: All supported platforms
Question/Problem Description
OpenEdge Secure Socket connection fails to connect using HTTPS. An error message is generated with OpenEdge error 9318 (SSL failure) and internal error code -54 (unable to get local issuer certificate).
 
Steps to Reproduce
Clarifying Information
Using ABL statement:
 
CONNECT "-ssl -H <HTTPS URL> -S <port>"
 
Socket can be accessed via Web Browser and certificate is used with no errors
Error MessageSecure Socket Layer (SSL) failure. error code <err_number>: <ssl_error_message> (9318)
Secure Socket Layer (SSL) failure. error code -54: unable to get local issuer certificate <Certificate Name> from <DLC>\certs (9318)
Defect/Enhancement Number
Cause
Root certificate has not been imported to OpenEdge
Resolution
1 - Go to Control Panel -> Internet Options -> Content folder -> "Certificates" button ->Trusted Root certification Authorities -> Choose required certificate and click on "Export" button.

2 - Export as DER encoded binary X.509 (.CER)

3 - Import to OpenEdge using the following command from PROENV:

certutil -format DER -import exportedfilename.cer
Workaround
Notes
This error can occur for any missing certificate, not only the root certificate. If a lower-level certificate has not been imported, the socket may not be accessible through a browser.
Attachment 
Last Modified Date12/29/2014 12:22 PM