OpenEdge-managed TLS client connection points indicate TLS clients specifically supported by OpenEdge. These clients can be accessing OpenEdge servers using TLS, either indirectly on the Internet (using HTTPS) or directly on an intranet, depending on the server involved in the connection. OpenEdge-managed TLS server connection points indicate TLS servers specifically supported by OpenEdge for direct access on an intranet without the need for an intervening Internet connection.

Note: OpenEdge databases configured for OpenEdge Replication may run as TLS clients or servers, depending on their role in the replication set.

For more information, see How OpenEdge Replication works with Transport Layer Security.

All OpenEdge-managed TLS servers rely on a common OpenEdge keystore to manage the private keys and server digital certificates required to support TLS connections from clients. These OpenEdge-managed TLS servers include the OpenEdge Database, PAS for OpenEdge, and ABL socket servers.

To complete PKI certificate‑chain validation for server certificates, the trusted root CA certificate was required to be available in this trust store. Starting with OpenEdge 13.1, the operating system trust store is the default source of trusted root CA certificates for TLS trust validation. This change affects only how trusted CA certificates are located. The existing keystore configuration for server certificates and private keys remains unchanged. When the native OpenEdge trust store is explicitly configured in place of the OS trust store, it serves as the source of trusted root CA certificates instead. In that case, the OpenEdge-managed TLS clients and servers in ABL include database clients, socket clients, web service clients, and the SQL clients (JDBC and ODBC) use the native OpenEdge trust store. The .NET and Java Open Clients are exceptions; they rely on their own certificate store mechanisms provided by the Open Client Toolkit.

For more information on OpenEdge support for managing key and certificate stores, see Manage TLS server identity.

The OpenEdge TLS client and server connections shown within (or between) ABL applications indicate ABL applications acting as TLS clients, TLS servers, or both using ABL socket connections. Using sockets, ABL applications running on different ABL client machines can communicate securely with each other using the same TLS infrastructure as any OpenEdge TLS client and server (such as an ABL client and PAS for OpenEdge). Note, also, that ABL sessions can be socket servers for non-ABL socket clients and can be socket clients for non-ABL socket servers.

Note: An ABL session running in a PAS for OpenEdge instance can function as a TLS socket client only (not as a socket server).