There are no secrets that time doesn’t reveal—how to use the token management API to rotate your secrets!

Remember the saying that “there are no secrets that time doesn’t reveal”? Well, this statement also holds true when it comes to data security—despite all the technological improvements that have been made over the past decade. We all know “a “friend” who accidentally pushed a secret token into a public Github repository.

Managing your secrets and API tokens can be cumbersome and an error-prone process. Today’s microservices and cloud ecosystems require DevOps teams to handle a huge number of distributed API and access secrets. Without a dedicated strategy, you quickly lose control of all the secrets you’re depending on across your environment. One result can be an ever-increasing number of secrets as everyone becomes reluctant to delete old secrets for fear of breaking dependencies. Another more serious outcome can be the exposure of your secrets to the outside world and the introduction of business-critical security leaks.

A well-known strategy for addressing these challenges is the introduction of centralized and secure management of all your secrets along with the regular rotation of secrets that are used for automation tasks. Vault by HashiCorp is one such tool that can help you organize your secrets and make them available for your automation scripts.

With the release of Dynatrace version 1.169, we’ve introduced a new API endpoint for token management that enables the implementation of an API token rotation strategy that helps your DevOps teams to further secure their monitoring environments.

This blog post provides an example of how to use the Dynatrace token management API endpoint to implement a rotation strategy using a HashiCorp Vault server.

Create a token secret in a HashiCorp Vault server

Create a token secret in your vault server. Secret fields are customizable. We’ll store this example Dynatrace API token secret in a field called token, as shown below:

vault kv put secret/dynatrace/automation_script1 token=w_u5xy97RK-gaPKwFaadu

Create a secret in Vault

Retrieve a secret for an automation script

Whenever you need to use this secret in one of your automation scripts, use the get command in the Vault command line interface, as shown below:

vault kv get secret/dynatrace/automation_script1

Retrive a secret from Vault

In a shell script, it is, of course, more convenient to receive the only the secret itself instead of all the metdata about the secret. This can be done using the field selector with the Vault get command:

vault kv get -field=token secret/dynatrace/automation_script1

Directly retrieve secret value

Create a Dynatrace master token to rotate an API token

Now that we can create, update, and retrieve a secret through the Vault server, let’s take a look at how we can automatically rotate API token secrets using the Dynatrace token management API endpoint.

First, let’s create a Dynatrace master token with the Token management permission enabled, which allows us to rotate all Dynatrace API tokens in one place:

Create a master Dynatrace API token with the Token management permission

Then, save the master token in your Vault server as shown below. This master token will be used by the rotation shell script to automatically rotate this automation client API token:

vault kv put secret/dynatrace/master token=nyjtIaZ8R_-Lw8-kpgp7D

Store the master API token in Vault

Create a Python script for rotating a token

Now let’s create a quick and dirty Python script that automatically rotates all given Dynatrace tokens and updates the respective secret in the Vault server.

The newly released token management API endpoint allows you to automate the management of all your API tokens. Please refer to the Dynatrace API Explorer for details about each available token management operation:

Token management operations in API Explorer

Rotation of Dynatrace tokens involves the following steps

  1. Use a Dynatrace master token to receive the information of a given API token.
  2. Create a new API token with the same permissions.
  3. Update the API token within the password vault.
  4. Delete the old API token.

To create the new API token using the Dynatrace token management API and the Dynatrace master token:

curl -X POST "" -H "accept: application/json; charset=utf-8" -H "Authorization: Api-Token nyjtIaZ8R_-Lw8-kpgp7D" -H "Content-Type: application/json; charset=utf-8" -d "{ \"name\": \"My Tenant Token\", \"scopes\": [ \"ReadConfig\" ]}"

Next, to update the API token within the password vault:

curl -i -X POST \

-H "X-Vault-Token:s.aWf0evg0WSwOKKxBdweuQsqU" \

-H "Content-Type:application/json" \

-d \

'{ "data" : { "token" : "nyjtIaZ8R_-Lw8-kpgp7D" } }' \


To delete the now outdated token in Dynatrace:

curl -X DELETE "" -H "accept: application/json; charset=utf-8"

The following Python script automates all the steps above. The script is also capable of rotating an array of multiple secrets in a single run.

It’s pretty simple to automate the rotation of your Dynatrace API tokens once a day or week by registering the Python script as a regular cron job in one of your trusted servers.

See the Python script below:

Python script to rotate API tokens

This script is also available in our Github repository.

The token management API can be used to automate all kinds of use cases related to API tokens in Dynatrace. The example discussed in this blog post demonstrated one of the most important use cases, rotating your tokens on a regular schedule to avoid security issues. Other use cases could be automatically checking all tokens and deleting those that are no longer used or that relate to a given user.

Stay updated