No Session Reuse (-nosessionreuse)

Use No Session Reuse (-nosessionreuse) when you do not want to reuse a Transport Layer Security (TLS) session ID to reconnect to the same TLS-enabled database server.

Operating system and syntax UNIX / Windows -nosessionreuse
Use with Maximum value Minimum value Single-user default Multi-user default
Client Connection 1 0 — 0

While your database connection may or may not be running with TLS enabled for communication to its remote clients, the communication to the Authentication Gateway STS Server is always run with TLS enabled.

If the database is running with TLS enabled, No Session Reuse (-nosessionreuse) is set the same for both the OpenEdge Server TLS communication as well as for the STS Server communication.

The No Session Reuse (-nosessionreuse) parameter may be modified while your database is online using PROMON or through the _DbParams VST. This change will take effect on any newly spawned servers.

For more information, see Learn about Security and Auditing.

Note: OpenEdge TLS turns on TLS session reuse by default. So, after the initial connection to a given host (-H) and port (-S), each subsequent connection to the same host and port restarts the TLS session and ignores any different connection parameters that are specified for the subsequent connection, including -nosessionreuse. If you want to change TLS socket options (such as -nohostverify) for each subsequent connection to a given host and port, be sure to specify the -nosessionreuse parameter on the initial TLS socket connection to that same host and port.