OpenEdge TLS client components require access to trusted Certificate Authority (CA) root certificates for validating the identity of TLS servers during a connection handshake.

From OpenEdge 13.1 onwards, this process has been significantly simplified: OpenEdge now uses the operating system (OS) trust store by default, eliminating the need to maintain a separate, OpenEdge-specific certificate store in most deployment scenarios.

In releases prior to 13.1, OpenEdge maintained its native certificate store for TLS trust validation, located in OpenEdge-install-dir\certs on Windows or $DLC/certs on UNIX or Linux. In addition, certain OpenEdge components relied on the JDK or OS trust store for certificate validation. This architecture required every OpenEdge installation to carry its own set of CA certificates, independent from the certificates managed at the OS level. As enterprises adopted a growing number of CA certificates and scaled OpenEdge deployments across multiple servers, maintaining a dedicated certificate store per installation became a significant operational burden. Whenever a CA certificate would be added, renewed, or revoked at the OS level, administrators had to manually replicate that change across every OpenEdge-specific certificate store in every installation.

Now, OpenEdge reads the CA certificates that are already managed and maintained by the OS and uses them directly for the TLS certificate chain validation. When a certificate is added, updated, or revoked in the OS trust store, OpenEdge automatically reflects that change, without requiring manual synchronization.

OpenEdge also retains the flexibility to use native trust store, when required. This behavior is controlled by the TLS trust store policy file, $DLC/properties/TLSPolicy.cnf. This file provides administrative control to configure which trust store—OS or OpenEdge native—is used for certificate validation. For more information about the policy file and its configurable parameters, see Trust store policy file.