Skip to main content

Login as Trusted Application

Create a token for a trusted application, which can then be passed to other web services.

POST https://instance.securid.com/aveksa/command.submit?cmd=loginTrustedApp

info

The Client Id, Client Secret, and Auth URL are found on the Admin > Web Services > Trusted Application page.

Session Limit

Each call to loginTrustedApp creates a new concurrent session. The server enforces a per-application session limit. If the limit is exceeded, the server returns:

Concurrent session limit exceeded for this trusted application

There is no explicit logout command for trusted application tokens. Sessions expire automatically after the configured timeout. To avoid hitting the limit, reuse tokens across requests within a session instead of calling loginTrustedApp before each request.

Request

Parameters

loginTrustedApp
formatproperties - (Default) Returns the response as key=value pairs.

json - Returns the response as JSON.

Headers

The client ID of the trusted application
The client secret of the trusted application
Acceptapplication/json
Content-Typeapplication/json

Response

Parameters

tokenThe security token for this trusted application. Pass as Authorization: Bearer in subsequent requests.

Examples

Request

curl -K -X POST \
"https://instance.securid.com/aveksa/command.submit?cmd=loginTrustedApp&format=json" \
-H "ClientId: <client-id>" \
-H "ClientSecret: <client-secret>" \
-H "Content-Type: application/json"

Response

The token is returned at the top level, not nested inside a data object.

{
"token": "ta31012485e36e3be2c9:-28aff589:18a2295240d:-7bcd"
}

Verified with RSA Governance & Lifecycle version 8.0.0.188886 P10_HF01.