BasicToBearer
When you choose this authorization type, the Aisera platform makes a REST API request, to trade a set of basic credentials with a Token.
The connector will make a request to the Access Token URL, using the Basic Authorization header from the username and password. Any headers will be included in the Request, and the HTTP Operation parameter will define the HTTP type. The Extraction Keys instruct the connector on how to extract the token and the TTL from the response.
BasicToBearer authentication includes the following fields:
Fields
Field Explanation
Username *
This field in most cases is the username of a user of the instance of the external system
Password *
This field in most cases is the password of a user of the instance of the external system
Access Token URL *
The URL where the client exchanges the authorization code for an access token.
Access Token Extraction Key
Which key should contain the access_token in the JSON object. By default is access_token but this can change.
Expires In Extraction Key
Which key should contain the expires_in value for the new access token in the JSON object. By default it expires_in but this can change.
Http Operation *
What HTTP Operation is used for the authorization request (DEFAULT is POST)
Headers
The custom headers in JSON format; e.g. {"apiKey": "api_key_value"}.
Use Raw Token
This checkbox needs to be enabled only when the prefix 'Bearer' needs not to be added in front of the token. After obtaining the authorization token, we must decide whether to include the 'Bearer' prefix before appending it to the request for the ingestion part. This is accomplished using this checkbox flag.
Authorization Explanation
This authorization allows the Aisera application to make API calls, after supplying the Username, Password, and the Access Token URL. After the credentials are added, the application receives a bearer token that serves as the credentials for the API call.
An example of this is the TeamDynamix connector that uses this authorization.
Examples:
The setup for integrating with TeamDynamix involves providing the following credentials:
Username: The username used to authenticate with the TeamDynamix platform. Password: The corresponding password for the provided username. Client Id (Application Id): A unique identifier assigned to the application by TeamDynamix. Upon successful authentication with the provided credentials, TeamDynamix returns an access token. This access token serves as a secure means of authentication for subsequent requests to the TeamDynamix API. Once obtained, this token can be included in the headers of API requests to authenticate and authorize access to TeamDynamix resources.
Note: This authorization flow involves sending the username and password to the access token URL in order to obtain the access token.
Last updated