Knowledge Base

Showing results for 
Search instead for 
Did you mean: 

How do I use Password Encryption with Extensions?

Most of our extensions support password encryption. In order to use this service, please follow these steps exactly as specified. Once done, you will have to uncomment the encryptionKey and encryptedPassword and update them with the ones that you generate in the config.yml file.


For this case we will take Cassandra Monitoring Extension as a sample.


  1. Navigate to your Machine Agent installation folder, and then head to the “monitors” folder.

      Screen Shot 2017-11-30 at 12.00.33 PM.png

  1. Now enter your Extension folder, or in our case, “CassandraMonitor” and copy the name of the jar file. In our case : “cassandra-monitoring-extension.jar

  1. Open your terminal and navigate to the CassandraMonitor Folder. 

    Screen Shot 2017-11-30 at 12.20.53 PM.png
  1. Once you are in the folder. Make sure the jar file is present. In our case cassandra-monitoring-extension.jar.

  2. Once you have verified all the details, run the following command. This command will give you your encrypted password.

    java -cp "cassandra-monitoring-extension.jar" com.appdynamics.extensions.crypto.Encryptor myKey myPassword

  3. The “myKey” in the command can be any random key that you would like to use to encrypt the password.

  4. The “myPassword” is going to be your actual password that you would use to log in to your product so as to get access. This is going to be that password that you are trying to encrypt.
    Screen Shot 2017-11-30 at 12.27.51 PM.png

  5. Save the values for your “encryptionKey” and "encryptedPassword" in a text editor so that you don’t lose them. The “Encrypted String” value will be your encrypted password.

  6. Add the values for "encryptionKey", "encryptedPassword" in the config.yml. The value for "encryptionKey" is the value substituted for "myKey" in the above command. The value for "encryptedPassword" is the result of the above command.

    Screen Shot 2017-11-30 at 12.33.31 PM.png 

  7. Once you complete all the steps listed above, your extension will be ready to use the newly generated encrypted password.

Version history
Revision #:
5 of 5
Last update:
‎10-04-2018 03:24 PM
Updated by:
Labels (1)

Found this article helpful? Click the Thumbs Up button.
Have an additional comment? Post it below.



I see that the tags include 4.3, 4.4 and 4.5. Can anyone confirm if password encryption is compatible with the machine agent?



Hi Todd,

This does work with older versions of the Machine Agent as well.



Hahaha not sure how I missed it - perhaps it wansn't in the particular extension doc before (it is now) but found the clues in the source code of ext :)


So I assume this applies to all "AppDynamics supported" extensions?

Do you have plans to make implementation of encryption mandatory for "vendor supported" as well?

Hi Konrad,


As of now, we don't have any plans to enforce encryption. But yes, since it is going to be part of our library, vendors can always use it. 



What do you do with the regular password field (where we provide clear text password)?


Do we comment/remove it from config.yml file or set it to empty/null/""


password: ""




remove it altogether.

Hi Manoj,


You can just comment it out if you have the encryptedPassword defined.