BasicToBearer

Overview

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 Time To Live (TTL) from the response.

Fields

The BasicToBearer authentication type includes the following fields:

Field
Description

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.

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.

HTTP Operation

What HTTP Operation is used for the authorization request. By default this is POST.

Headers

The custom headers in JSON format: {"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.

Last updated

Was this helpful?