GET Permissions/Refresh

Reloads the Web SDK caller's permissions without having to re-authenticate and get a new bearer token.

Workflow tickets are the most common case where the Web SDK caller's permissions may require a refresh after ticket creation. When you create a workflow ticket, Trust Protection Platform automatically grants the approvers as defined by the Workflow object. A WebSDK user with an active session will not be able to see a new ticket assigned to them unless they refresh their permissions.

Requirements

  • Permissions: The caller must have Access permission to the REST API. For more information, see Confirming service status.
  • Token scope:  Any valid scope, such as Agent, Certificate, or SSH

Headers

  • Content type: Content-Type:application/json.

  • Token: The bearer access token that you received. For example, Authorization:Bearer 4MyGeneratedBearerTknz==. For more information, see Passing a bearer token in your API calls.

Parameters

None.

Returns

Response description

Name

Description

Result

If the token successfully refreshes, the value is 1.

Error

If the token expired, an error occurs.

API key '[API Key] is not valid. Try /authorize or /authorize/integrated.

Example: Refresh permissions

Request

GET https://test.venafi.example/vedsdk/Permissions/Refresh/
Authorization:Bearer 4MyGeneratedBearerTknz==

Response

HTTP/1.1 200 OK
{
   "Result":1
}

Response that requires a new key

{
   "Error":"API key '35f8f62f-be51-7691-3b65-274084d1362b' is not valid. Try /authorize or /authorize/integrated"
}