App Authentication

Authenticates an OBO app using the application saved RSA public key.

Authenticate an App with public key

post

Based on an authentication request token signed by the application's RSA private key, authenticate the API caller and return a session token.

A HTTP 401 Unauthorized error is returned on errors during authentication (e.g. invalid app, malformed authentication token, app's public key not imported in the pod, invalid token signature etc.).

Body

application/json

Request body for pubkey authentication

tokenstringOptional

a JWT containing the caller's username or application appGroupId and an expiration date, signed by the caller's private key.

Responses

200

OK.

application/json

namestringOptional

The name of the header in which the token should be presented on subsequent API calls.

tokenstringOptional

Authentication token that should be passed as header in each API rest calls. This should be considered opaque data by the client. It is not intended to contain any data interpretable by the client. The format is secret and subject to change without notice.

authorizationTokenstringOptional

(Beta) Short lived access token built from a user session. This field is still on Beta, please continue using the returned "token" instead.

401

Client is unauthorized to access this resource

application/json

403

Forbidden to access this endpoint .

application/json

500

Server error, see response body for further details.

application/json

post

/pubkey/app/authenticate

HTTPcURLJavaScriptPython

POST /login/pubkey/app/authenticate HTTP/1.1
Host: yourpodURL.symphony.com
Content-Type: application/json
Accept: */*
Content-Length: 16

{
  "token": "text"
}

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

📘 Requirements

This authentication requires the app to be enabled and to have at least one RSA Public key registered. For more information, refer to Create an RSA Key Pair.