Key Manager Authenticate (Cert)

Authenticates the API caller on the key manager using the client certificate provided in the TLS session, returning a key manager token.

Authenticate.

post

Based on the SSL client certificate presented by the TLS layer, authenticate the API caller and return a session token.

Responses

200

OK.

application/json

400

Client error.

application/json

403

Forbidden: Certificate authentication is not allowed for the requested user.

application/json

500

Server error, see response body for further details.

application/json

post

/v1/authenticate

HTTPcURLJavaScriptPython

POST /keyauth/v1/authenticate HTTP/1.1
Host: yourkeymanagerURL-api.symphony.com
Accept: */*

{
  "name": "text",
  "token": "text",
  "authorizationToken": "text"
}

❗️ Key Manager Token Management

The token you receive is valid for the lifetime of a session that is defined by your pod's administration team. This ranges from 1 hour to 2 weeks.

You should keep using the same token until you receive a HTTP 401, at which you should re-authenticate and get a new token for a new session.

Datafeeds survive session expiration, you do not need to re-create your datafeed if your session expires.

🚧

Before calling the Pod endpoints, the caller must be authenticated with the pod (the dedicated Symphony cloud service) by calling the Session Authenticate endpoint, followed by this one.

To call the Key Manager Authenticate endpoint, you must provide a certificate where the Common Name of the certificate matches the username of an active Service User account on your pod.