Try OpenEdge Now
skip to main content
Getting Started
Setting Up Secure Communications : Getting started: using the demo certificate : Identifying trusted clients
 

Identifying trusted clients

As you update the configuration of either the Web server (or the OpenEdge Management Trend Database, if available in your configuration), you can optionally identify one or more trusted clients who are allowed to connect to the OpenEdge Management or OpenEdge Explorer instance using the designated protocol. If you want to list more than one trusted client, separate each entry by a comma.
You can use the trusted clients feature to allow a few well-known clients (or even an entire subnet) to connect unsecured to OpenEdge Management for convenience and possible performance reasons, while requiring all other clients to use a secured connection. For example, you might want to establish that you use the HTTP protocol for intranet connections and the HTTPS protocol for any Internet connections (for example, coming through a firewall).
You can identify a trusted client by using any of the following formats:
*DNS name (for example, pcjoe)
*A dot-formatted address string (for example, 123.123.123.123)
*A wildcard dot-formatted address string (for example, 123.123.123.*)
Independent of how you configure trusted clients, you are always able to connect from the local host. If you leave the trusted clients list empty, any client can connect.