Update the Agent Configuration

For Java agents:
- Import the CA or server certificate into your Java agent's trust store by following the steps in Enable SSL for the Java Agent.
- For general details on Java agent configuration, see Install the Java Agent.
  Warning:
  Certain features of Cisco Secure Application are currently not available when using Java Development Kit (JDK) versions 23 and 24. This is due to the removal of the security manager in these versions. As a result, the following runtime eventing features are impacted:
  - Remote Command Execution
  - Listening Server Sockets
  - Outbound Web API Connections
  - File Access (including reading, writing, creating, and deleting)
  We are committed to resolving this issue and are actively working on a permanent solution to ensure full compatibility with JDK versions 23 and above. Thank you for your understanding and patience as we enhance our product to support these newer Java versions.
For .NET agents on Linux hosts:
- For general details on .NET agent configuration, see Install the .NET Agent for Linux.
- In the agent configuration, specify the location of the certificate you extracted above. You can specify this location in your agent's configuration file or with the APPDYNAMICS_CONTROLLER_SSL_CERTFILE environment variable (see Configuring SSL Variables for .NET Agents):
```
{
"controller": {
"host": "ec2-18-236-232-10.us-west-2.compute.amazonaws.com",
"port": 443,
"ssl": true,
"certfile": "_path_to_single_certificate_file_"
}
}
```
For .NET agents on Windows hosts:
- In the agent configuration, specify the location of the certificate you extracted above. You can specify this location in your agent's configuration file or with the APPDYNAMICS_CONTROLLER_SSL_CERTFILE environment variable (see Configuring SSL Variables for .NET Agents):
```
<controller host="ec2-18-236-232-10.us-west-2.compute.amazonaws.com" port="443" ssl="true" enable_tls12="true" ssl-certificate-file="_path_to_single_certificate_file_" >
...
</controller>
```

For Node.js agents:

Confirm that the Node.js agent version is at least 24.9.0.

Add this to the require statement in its configuration file. For details see Vulnerability Reporting on Node.js Agent:

require("appdynamics").profile({
controllerHostName: '<controllerHost>',
controllerPort: 443,
controllerSslEnabled: true,
accountName: '<accountName>',
accountAccessKey: '<accessKey>',
applicationName: '<appName>',
tierName: '<tierName>,
nodeName: '<nodeName>',
secureAppEnabled: true,
certificateFile: '_path_to_single_certificate_file_'
})

Documentation

Update the Agent Configuration