TLS enabled DataServer
- Last Updated: March 18, 2026
- 2 minute read
- OpenEdge
- Version 13.1
- Documentation
Configuring the clent and server components of a remote DataServer connection with Transport Layer Security (TLS) communications is optional. Users can maintain both TLS-enabled and non-TLS instances of a DataServer broker environment. However a given instance supports only one type of connection, either secure or non-secure.
- Install a server private key and a public key certificate. OpenEdge provides built-in keys and certificates that are suitable for use on development or demonstration servers; for production machines, you should obtain server certificates from an internal or public Certificate Authority (CA).
- Specify the
keyAliasandkeyAliasPasswdparameters in theUBroker.OR.orabroker1section of the ubroker.properties file for access to the private key/digital certificate - Disable session caching of the orabroker using the
noSessionCacheparameter, or enable it with a specified timeout using the sessionTimeout parameter.
To connect to a TLS-enabled OE DataServer component, Client and Servers must have access to a digital (public key) certificate that can authenticate with the digital certificate used by the server, and the client must be configured to send TLS requests. All OpenEdge-managed TLS servers rely on a common OpenEdge key store to manage the private keys and server digital certificates required to support TLS connections from clients.
Most OpenEdge‑managed TLS clients and servers rely on a certificate store to manage trusted root CA certificates for establishing TLS connections. Starting with OpenEdge 13.1, the operating system trust store is the default source of these trusted root CA certificates for TLS trust validation. As an alternative, the native OpenEdge trust store can be explicitly configured to serve as the source of trusted root CA certificates instead of the OS trust store.