Most user interactions with TLS happen during configuration of TLS clients and servers. This includes the maintenance of TLS server identities and client root certificates, as well as the setting of any TLS session properties prior to running a given TLS client or server.

During an TLS session, users (especially on the client side) might not be aware that an TLS session is in progress, though in practice applications that use TLS generally provide messages that notify users of their security situation. A common example is in Web browser applications that advise users of Web sites that they might visit for which proper TLS authorization cannot be established. The Web browser usually offers the option to forego accessing any unauthorized Web sites.

In OpenEdge, if an TLS client fails to authenticate an TLS server, the connection fails and a message is returned for handling by the client, which at a minimum displays a message for the user. For more information on OpenEdge support for TLS, see TLS in OpenEdge.