Use No Host Verify (-nohostverify) to turn off host verification for a Transport Layer Security (TLS) connection to a database server or to the OpenEdge Authentication Gateway server.
Operating system and syntax UNIX / Windows 
-nohostverify
Use with Maximum value Minimum value Single-user default Multi-user default
Client Connection, Authentication Gateway server 1 0 – 0

Without this parameter specified, the Web service compares the host name of the connecting AppServer with the Common Name specified in the server digital certificate, and raises a Web service error if they do not match. With this parameter specified, the Web service never raises the error.

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

If the database is running with TLS enabled, No Host Verify (-nohostverify) is set the same for both the OpenEdge Server TLS communication as well as for the OpenEdge Authentication Gateway server communication.

While the database is running, you may change this parameter using PROMON or through the _DbParams VST. This change only affects the primary broker and any newly spawned servers. Changes to existing secondary brokers while the database is running require a restart.

For more information, see OpenEdge Getting Started: Core Business Services - Security and Auditing.