A personal access token is a user specific long lasting authentication token. Any personal access token should be protected as if it were a password. There is no secondary authentication when using a personal access token - if a user has another user’s personal access token, they will be entirely able to act as the user that owns the personal access token on the LUSID platform.

For this reason it is very important that personal access tokens are strictly protected.

A personal access token can be provided as a Bearer token in the Authorization HTTP header of any request to the LUSID platform. If the personal access token is valid, the request will be associated to the user owning the personal access token, and the request will be processed as such. Any access roles (and associated policies) to which the user is assigned will be used for access control as per any other request.

Personal access tokens are intended for use by automated systems that cannot support the Open ID Connect authentication flows. Due to the reduced level of authentication and lack of Multi-Factor Authentication (MFA), Personal Access Tokens should not be the first choice for application authentication, but rather the last resort.

Personal access tokens can optionally be created with a fixed deactivation date after which the token will become invalid.

Using  personal access tokens

When making a request to a LUSID API, add an Authorization header with the value:

Bearer <my-personal-access-token>

Associated roles and policies

A personal access token represents a user, and reflects whatever roles or policies that user’s access is governed by. As such, roles and policies are not directly associated with a personal access token, only to the user that created the token. Changing the Roles assigned to a user, will affect the access capabilities of all of that user’s personal access tokens.

Support for personal access tokens

Any API call to the LUSID platform that currently supports a OpenID Connect Bearer token, will support a personal access token.

Currently Honeycomb does not currently support Personal Access Tokens, and the LUSID Website cannot be navigated using a personal access token.

Administering personal access tokens

Personal access tokens can be administered via the LUSID web application as well as directly through the Identity API.

To create and administer personal access tokens via the LUSID web application, please visit this article to learn more.

The details of how to do so through the API can be seen the Open API Documentation (Swagger) for the identity service:

Personal access tokens once created can be revoked. Revoking a personal access token will immediately mark it as invalid and it will be unusable on the LUSID platform. A token cannot be reactivated once revoked.

Deletion of a user will immediately permanently invalidate all of their personal access tokens.