Configure and run TLS sessions
- Last Updated:Jan 25, 2023
- 2 minute read
- OpenEdge
- Version 12.2
- Documentation
When an TLS server and client have access to authenticating keys and certificates they can engage in TLS communications, which occur in the context of an TLS session. Before starting them, you have to configure, code, or otherwise specify to the client and server that they must communicate using TLS as directed by certain TLS session properties. The mechanisms for doing this differ depending on the server and client type, but the functional and manageable properties of an TLS session are the same among all OpenEdge server types and among most OpenEdge client types. During an TLS session, clients that you program (ABL and Open Clients) can also access the identity of the TLS server they are talking with.
The following sections describe these TLS session properties:
- Configure TLS server sessions
- Configure TLS client sessions
- Access an TLS server's X.500 Subject Name
Each TLS session property has a functional name that differs slightly, depending on the component you are configuring and how you configure it. The possible mechanisms for specifying these properties include the:
- Startup parameters (or switches) on the command line or in scripts
- Unified Broker framework component property editors or component properties in the ubroker.properties file
- Connection parameters, object properties, and other appropriate internal code for TLS client or server components that you program yourself
The following sections describe the function of these TLS session properties using generic names and phrases and specify the mechanism that you can use to set them for each TLS server and client component.