Key Information for the access-token-controller REST Web Service
This section covers the following aspects:
| • | Workflow |
| • | Permissions for access-token-controller |
| • | Base URL for access-token-controller |
| • | Additional Documentation for access-token-controller |
FlexNet Operations users call the access-token-controller REST web service to request an access token with a limited expiration from FlexNet Operations. The web service returns an access token which is a hexadecimal string with an rna_ prefix.
When firing requests to a FlexNet Operations API (REST or SOAP), this token must be added to the authentication header of the API request with the word Bearer followed by the token string.
The access token not only authenticates the requester but also defines the permissions of how the requester can use the API.
Permissions for access-token-controller
Any FlexNet Operations user can create and manage NORMAL tokens for themselves.
To create and manage tokens for other users (IMPERSONATED tokens), users require the following permissions:
| • | Create Impersonated Token |
| • | Plus at least one of the following permissions, depending on the type of user creating the IMPERSONATED token: |
| • | View and Manage Users |
| • | View and Manage Customer Users |
| • | View and Manage Partner Users |
Base URL for access-token-controller
Endpoints for the access-token-controller REST API are available on your FlexNet Operations host:
https://<siteID>.flexnetoperations.com/uar/v1/tokens
https://<siteID>.flexnetoperations.com/uar/v1/token
where <siteID> is your organization’s site ID which is supplied by Revenera. This is usually your organization's DNS name, but can also be the tenant ID that was assigned to your organization when FlexNet Operations was first implemented, and would have the format flexNNNN.
Note:URLs in this document refer to v1 of the APIs. Further releases of the API may increment this version. Please consult the Swagger documentation to identify the latest version of the API, and modify the URLs you use appropriately.
Additional Documentation for access-token-controller
In addition to this manual, the following documentation resources are available:
Redocly
Use the following URL to access the Redocly documentation:
https://fnoapi-access-token-controller.redoc.ly/
The access-token-controller pages on the Redocly platform provide the same information as the access-token-controller pages on Swagger, but in a slightly different format.
Swagger
Use the following URL to access the access-token-controller REST API documentation on Swagger:
https://<siteID>.flexnetoperations.com/flexnet/swagger-ui.html#/access45token45controller
where <siteID> is your organization’s site ID which is supplied by Revenera. This is usually your organization's DNS name, but can also be the tenant ID that was assigned to your organization when FlexNet Operations was first implemented, and would have the format flexNNNN.