Secrets API

About the Secrets API

The Secrets API allows you to manage secrets and perform some backend functions such as sealing and unsealing the Secret Store. It offers more functionality than the DC/OS GUI.

Request and response format

The API supports JSON only. You must include application/json as your Content-Type in the HTTP header, as shown below.

Content-Type: application/json

Host name and base path

The host name to use varies according to where your app is running.

If your app will run outside of the DC/OS cluster, you should use the cluster URL. To obtain the cluster URL, launch the DC/OS GUI and copy the domain name from the browser. In a production environment, this should be the path to the load balancer that sits in front of your masters.

If your app will run inside of the cluster, use master.mesos.

Append /secrets/v1/<api_endpoint> to the host name, as shown below.

https://<host-name-or-ip>/secrets/v1/<api_endpoint>

Authentication and authorization

About authentication and authorization

All Secrets API endpoints require an authentication token.

Obtaining an authentication token

Via the IAM API

To get an authentication token, pass the user name and password of a superuser in the body of a request to the /auth/login endpoint of the Identity and Access Management Service API. It returns an authentication token as shown below.

Via curl as a DC/OS CLI variable

Refreshing the authentication token

Authentication tokens expire after five days by default. If your program needs to run longer than five days, you will need a service account. Please see Provisioning custom services for more information.

API reference

Logging

While the API returns informative error messages, you may also find it useful to check the logs of the service. Refer to Service and Task Logging for instructions