Secure the Connection

The .NET Agent uses the settings in the container to negotiate the SSL protocol with the Controller. Normally you do not need to configure the security protocol for the .NET Agent.

For the Java Agent, see the Agent and Controller Tenant Compatibility for a list of the default security protocols for different versions of the Java Agent.

If the default security protocol for your version of the Java Agent is incompatible with the Controller or an intervening proxy, pass the ‑Dappdynamics.agent.ssl.protocol system property to set the protocol to one of these security protocols:

  • SSL
  • TLS
  • TLSv1.2
  • TLSv1.1
Important: Effective December 31, 2023, Splunk AppDynamics will no longer accept network connections utilizing TLS 1.0 and 1.1 protocols. See End of Support Notice: Disabling TLS 1.0 and 1.1.

Use the following format:

java -javaagent:<agent_home>/javaagent.jar ... -Dappdynamics.agent.ssl.protocol <protocol> ...

Splunk AppDynamics SaaS Controller Secure Connections

SaaS Controllers require the use of SSL. Therefore, you only need to enable SSL in the configuration settings for your agents and connect them to the secure Controller port, 443. See App Agent Security and Machine Agent Security.

App Agent Security

To configure your agents for SSL, set these SSL-related properties:

  • Set controller-ssl-enabled to true.
  • Set the controller-port to the correct value for either on-premises or SaaS Controller.

In multi-tenant and SaaS environments, App Agents authenticate themselves to the Controller using the required account name and account access key values set in the connection properties configuration file.

Machine Agent Security

For information on the security settings related to the Machine Agent connection to the Controller, see Machine Agent Configuration Properties.