Protect network traffic by using HTTPS where possible.
HTTP connections that are not protected by SSL/TLS use cleartext messages. When you permit insecure connections, you cannot prevent client applications from sending sensitive data. For example, a client could send unprotected credentials in an HTTP Authorization header. Even if the server were to reject the request, the credentials would already be leaked to any eavesdroppers.
Always use HTTPS for connections up to a load-balancer or proxy in front of the web application or server.
Use HTTPS for secure connections. Follow industry-standard TLS recommendations for Security/Server Side TLS.
When using an HTTP connection handler, use HTTPS to protect client connections.
Some client applications require a higher level of trust, such as clients with additional privileges or access. Client application deployers might find it easier to manage public keys as credentials than to manage username/password credentials. Client applications can use SSL client authentication.
Common Audit event handlers
Configure ForgeRock Common Audit event handlers to use HTTPS when connecting to external log services.
Server protocols such as HTTP, LDAP, and JMX rely on TLS to protect connections. To enforce secure communication, refer to Configure SSL communication between the agent and AM.
Communication between the agent and clients is managed by the web server in which the agent runs. For information about how to secure connections, refer to the web server documentation.