Perceptive Content Authorization Tokens

Describes authorization tokens and scopes supported by the Integration Server API.

Perceptive Content token authentication must be configured in the Perceptive Content environment in order to utilize Perceptive Content authorization tokens.
Note: Perceptive tokens are only valid for the Perceptive Content environment from which they were generated.

Perceptive Content Bearer Token

Bearer tokens can be generated by requesting the psw-user-bearer-api-token token type.

A bearer token can be used to make requests against supported Integration Server API operations. They prove that the user has been authenticated by the Perceptive Content instance used to generated the token.

Perceptive Content Bearer Token Scopes

The following is a list of scopes the can be requested using the /v1/authorization/perceptivetoken/token endpoint. Each scope grants access to the operations specified.
Additional scopes can be configured for more information, see the inserver.ini [Perceptive Token Management] settings topic of the Manage Content help.

List Operations / Hide Operations

Perceptive Content Identity Token

Identity tokens can be generated by requesting the psw-identity-api-token token type.

An identity token can be generated to prove the identity of an authenticated Perceptive Content user. These tokens can be introspected to validate the user's identity and the scopes that were requested when the token was initially created. This can be used for federating Perceptive Content users for external authentication and user management use cases.

Perceptive Content Identity Token Scopes

Any scopes that are configured for the Perceptive Content Server environment can be requested. For more information, see the inserver.ini [Perceptive Token Management] settings topic of the Manage Content help.