Rotating cluster tokens via API

Regularly changing your Dynatrace API authentication tokens is a good security practice. You can use Dynatrace Cluster API to rotate cluster management tokens. With the Tokens API, you can also automate the rotation.

To access the Dynatrace Cluster API

Open the Cluster Management Console.
Go to the User menu in the upper-right corner.
Select Cluster API.

Token rotation

To rotate cluster management tokens using Tokens API

Get the ID of an old token.

You need the ID so you can revoke and then delete it. If you only know the token itself, you need to get the token's ID to revoke and subsequently delete it. To do so, issue a POST token lookup request with the token to be deleted as the payload. The request returns the metadata of the token, including its ID, which you will need later.
Create a new token.

To create a new token that will replace the outdated one, execute a POST a new token request. Since you create a token with same parameters on a regular basis, you might consider storing its configuration in a version control system.
Revoke the old token. (Don't delete it before you revoke it.)

To revoke the old token, execute PUT an existing token. You will need the token ID value you obtained in step 1.
A revoked token can't be used for authentication, but it still exists in your environment. We recommend that you wait a week before deleting a revoked token, in case there is an emergency need for it. Check your organization's security policies for the exact delay.
If you want to rotate the token you're currently using for authentication of API calls, replace it with the new token you created in step 2.
Delete the old token.

After the waiting period, with the old token disabled (revoked), delete it. To do so, execute DELETE an existing token. You will need the ID of the token you obtained in step 1.

Example of rotating a token

For this example, let's assume you want to rotate a token with the following parameters:

The name of the token is ClusterTokenManager.
The scope of the token includes Cluster token management permissions.
The current token is 0987654321jihgfedcba.

With the Tokens API, you can automate the rotation.

Get the ID of an old token

Create a new token

Revoke the old token

Delete the old token

Get the ID of an old token

You will need the ID so you can revoke and then delete it.

Send a POST request to https://<your-domain>/api/cluster/v1/tokens/lookup
Include this application/json payload, where 0987654321jihgfedcba is the token value:

{
  "token": "0987654321jihgfedcba"
}

The request returns the metadata of the token in the application/json payload:

{
  "id": "3cf7c26f-ab12-abc123-ab1a-9340a6cce9a5",
  "name": "ClusterTokenManager",
  "userId": "admin@mycluster.com",
  "revoked": false,
  "created": 1578902397474,
  "lastUse": 1582130541813,
  "scopes": [
    "ClusterTokenManagement"
  ]
}

Save the token's ID value (3cf7c26f-ab12-abc123-ab1a-9340a6cce9a5).
You will need it later to revoke and delete this token.

Create a new token

Send a POST request to https://<your-domain>/api/cluster/v1/tokens
Include this application/json payload:

{
  "name": "ClusterTokenManager",
  "scopes": [
    "ClusterTokenManagement"
  ],
  "expiresIn": {
    "value": 30,
    "unit": "DAYS"
  }
}

The request returns the new token in the application/json payload:

{
  "token": "jihgfedcba0987654321"
}

Revoke the old token (3cf7c26f-ab12-abc123-ab1a-9340a6cce9a5)

Saved ID (step 1) of the token to be revoked and then deleted is: 3cf7c26f-ab12-abc123-ab1a-9340a6cce9a5

Send a PUT request with the token to be revoked to https://<your-domain>/api/cluster/v1/tokens/3cf7c26f-ab12-abc123-ab1a-9340a6cce9a5
Include this application/json payload:

{
  "revoked": true
}

A successful request is indicated by the 204 response code. The response doesn't return any content.
The token with ID 3cf7c26f-ab12-abc123-ab1a-9340a6cce9a5 is now revoked.

Delete the old token (3cf7c26f-ab12-abc123-ab1a-9340a6cce9a5)

To delete the 3cf7c26f-ab12-abc123-ab1a-9340a6cce9a5 token, send the DELETE request with the revoked token ID to https://<your-domain>/api/cluster/v1/tokens/3cf7c26f-ab12-abc123-ab1a-9340a6cce9a5

A successful request is indicated by the 204 response code. The response doesn't return any content.
The token with ID 3cf7c26f-ab12-abc123-ab1a-9340a6cce9a5 is now deleted.