You can make external calls to HTTP API endpoints in your DC/OS cluster. You must first obtain an authentication token and then include it in your HTTP request. Authentication tokens expire after five days. You can see the expiration time in the “exp” (Expiration Time) Claim of the JSON Web Token (JWT). Refresh your token by re-logging in to DC/OS.
Obtaining an authentication token
Obtain your authentication token using the DC/OS CLI. When you log into the DC/OS CLI, you paste an OpenID Connect ID token into your terminal prompt. This OpenID Connect ID token logs you into the DC/OS CLI, but does not allow you to access the HTTP API endpoints. You must obtain an authentication token to gain access to the HTTP API endpoints. Complete the following steps to obtain your authentication token.
Log in to the DC/OS CLI. Logging into the DC/OS CLI causes your authentication token to be written to a configuration file.
Use the following command to confirm that this write succeeded, and to view your authentication token.
dcos config show core.dcos_acs_token
Passing your authentication token to DC/OS endpoints
DC/OS endpoints expect to find your authentication token in the
Authorization field of your HTTP header as follows.
cURL, you can use command substitution to extract the token value from your configuration file. The following examples illustrate this syntax.
Sample Marathon request:
curl --header "Authorization: token=$(dcos config show core.dcos_acs_token)" http://<master-host-name>/service/marathon/v2/apps
Sample Mesos request:
curl --header "Authorization: token=$(dcos config show core.dcos_acs_token)" http://<master-host-name>/mesos/master/state.json