The following table describes the TLS session properties that you can set for an OpenEdge TLS client.

Table 1. OpenEdge client TLS session properties
Property Default setting Description
Use SSL to connect No Specifies if the client connection uses TLS tunneling.
Reuse a disconnected SSL session Yes Specifies if the connection reuses a previously established and disconnected TLS session when the client connects to an TLS server.
Verify the SSL server host name Yes Indicates if the client compares the host name of the TLS server with the Common Name specified in the server digital certificate, and raises an error if they do not match. If this property is set to No, the client never raises the error. This can be a useful setting if TLS server identity is likely to be moved from one physical machine to another and you do not want this to interfere with making the connection.
Certificate store location (Java Open Client only)1 None Specifies the location of the root certificate store used by the client for TLS connections.

The following table describes the mechanisms for setting TLS session properties for OpenEdge TLS clients and indicates where you can find more information about them.

Table 2. Mechanisms for setting OpenEdge TLS client session properties
This TLS client component: Relies on this mechanism: To set its TLS properties as described in:
ABL database client Startup and connection parameters
  • Startup Command and Parameter Reference
  • OpenEdge Programming Interfaces
  • ABL Reference
ABL AppServer client Connection parameters (for the Internet using the AIA or an intranet)
  • ABL Reference
ABL client of industry Web services2 Connection parameters
  • Develop Web Services for OpenEdge
  • ABL Reference
ABL client of the SonicMQ BrokerConnect2 Connection parameters (for the Internet using the AIA or an intranet)
  • Use OpenEdge Adapter for Sonic ESB
  • OpenEdge Application Server: Developing AppServer Applications (for URL formats and usage)
ABL socket client2 Connection parameters
  • OpenEdge Programming Interfaces
  • ABL Reference
.NET Open Clients of the AppServer Connection parameters and run-time properties (for the Internet using the AIA or an intranet)
  • Use the Open Client Toolkit
  • .NET Open Clients
Java Open Clients of the AppServer Connection parameters and run-time properties (for the Internet using the AIA or an intranet)
  • Use the Open Client Toolkit
  • Java Open Clients
JDBC or ODBC SQL database clients Switches on the client connection string
  • Develop SQL for OpenEdge (sections on SQL-ABL interoperability)
OpenEdge Replication plugins acting as TLS clients Replication properties file Set Up OpenEdge Replication
AppServer Internet Adapter (AIA) The Unified Broker framework
  • OpenEdge Management online help
Sonic ESB Adapter Sonic ESB tools for managing OpenEdge services
  • Sonic ESB documentation
WebSpeed Messenger The Unified Broker framework
  • OpenEdge Management online help

Other client platforms potentially involved with OpenEdge TLS servers, including Web service clients of OpenEdge Web services (managed by the WSA) and Web browser clients of WebSpeed, provide their own mechanisms for making TLS connections using HTTPS. For more information, see the relevant platform documentation.

1 The certificate store for all OpenEdge-managed TLS clients, except the Java and .NET Open clients, is installed in the same location under the OpenEdge installation path for each OpenEdge TLS client. For Java Open Clients, there is no standard location for the certificate store, so you must manage it using the tools provided with the Open Client Toolkit and specify its location to configure Java Open Client TLS connections. For .NET Open Clients, you must locate and manage the certificate store as provided by the tools available with Microsoft .NET.
2 ABL code in WebClient applications can also perform any of these TLS client functions in a user-downloadable application environment. However, note that the WebClient does not support access to any OpenEdge relational data source, including the OpenEdge RDBMS. The WebClient relies on the AppServer for all access to OpenEdge relational data sources. OpenEdge provides separate support for securely downloading and updating the WebClient and its application code over the Internet or an intranet. For more information, see Develop Web Clients.