Connecting an TLS client to an TLS server
- Last Updated: January 17, 2024
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
When you connect an ABL socket object to an TLS server socket, you must specify the connection as an TLS connection. Your connecting client must be able to authenticate itself to the TLS server, and you can optionally require the server to authenticate itself to your TLS client.
To connect an ABL socket object to an TLS server socket, include the TLS
parameters shown in the following table as part of the connection parameters string that you
pass to the socket object CONNECT() method. For additional
information, see Implementing an ABL socket client.
| Connection parameter | Description |
|---|---|
-ssl
|
Directs that the connection to the server socket use TLS tunneling. |
-nosessionreuse
|
If specified, the connection does not reuse the TLS session ID when reconnecting to the same TLS server. |
-nohostverify
|
If specified, turns off host verification for an
TLS connection. Without this parameter specified, the client compares the host name
by the -H parameter with the Common Name specified
in the server digital certificate, and raises an error if they do not match. With
this parameter specified, the client never raises the error. |
For more information on OpenEdge TLS support and connecting an TLS client to an TLS server, see Introduction to Security and Auditing.