Authenticate with Deep Security Manager

Deep Security Manager uses API keys for authenticating HTTP requests. Each request that you make requires an api-secret-key header that contains a secret key, as in the following example request:

GET /api/policies HTTP/1.1
Host: localhost:4119
api-secret-key: 2:vJC6lckDygB6FYURIvR0WK2ZTAhIY8rb0Amy9UMn4mo=
api-version: v1

When using a client library, you obtain an instance of ApiClient and configure it to use your secret key. The configuration is global, so that all calls to the API thereafter are authenticated using the secret key. The GET and POST examples below show how to create and configure ApiClient.

The manager uses the secret to authenticate your request. Each API key is associated with a role that determines the actions that you can perform.

Create an API key

Create an API key to use for authenticating your requests with Deep Security Manager. When you create an API key, you provide a name, the role to associate with the key, and optionally an expiry date. For more information, see Create and Manage API Keys.

Note:

To create an API key, you require the access rights to create users.

Upon creation of an API key, you are provided a unique secret key that is associated with the API key. You include this secret key in the HTTP request for authenticating. You must store the secret key when it is provided because at no other time are you able to obtain it. If you lose the secret you must create a new API key (using the SDK or using a username and password) or create a new secret for the key.

Tip:
The Creating a Trend Micro Deep Security API Key video steps you through the process.
  1. In Deep Security Manager, click Administration > User Management > System API Keys.
  2. Click New and enter the property values for the key.
  3. Click Next. The secret is presented. This is the only time that you can obtain the secret.
  4. Copy the secret and securely store it.
  5. Click Close.