githubEdit

OAuth 2.0 Password Grant

Authenticate using the OAuth 2.0 Password Grant

Overview

OAuth 2.0 Password Grantarrow-up-right is an industry standard authentication method where the application exchanges the username and password for an access token.

Fields

OAuth 2.0 Password Grant authentication includes the following fields:

Fields
Description

Client Id

A unique identifier assigned to the client application by the authorization server.

Client Secret

A confidential string used by the client to authenticate itself to the authorization server.

Username

This field is the username of a user for the external system that you want to integrate with.

Password

This field is the password of a user of the external system that you want to integrate with.

Grant Type

This is "password' by default. Certain applications may require you to specify the grant type in a non-standard way, or may support a variation of the Password Grant type. This can be replaced according to the requirements of the third-party application.

Headers

This field can be used when extra headers must be specified for authorization.

Access Token URL

The URL where the client exchanges the authorization code for an access token.

Refresh Token URL

The Refresh Token URL is the endpoint in the OAuth 2.0 authorization server where a client can request a new access token using a refresh token. This URL is used when the current access token expires to obtain a new one without requiring the user to re-authenticate.

Use Raw Token

Enabling this removes the Bearer prefix from the Authorization header.

Body Parameters

Use this field to include extra form parameters for authentication, which will be added as the request body. This field accepts values using the JSON format {"key":"value"}.

circle-info

Not all fields are required. Only fields with an asterisk by them are required. Required combinations of fields differ based on the specific requirements of the external system.

Configuring the external platform

When configuring the external system for OAuth 2.0 integration with the Aisera platform, the following redirect URLs may need to be whitelisted.

Service Account Authorization

For service account authorization for use with the data sources and workflows whitelist:

https://<cluster_id>.login.aisera.<top_level_domain>/?id=aisera.oauth.oauthCommand

Contact your Aisera support team for the Cluster Id.

User Authorization

For user authorization for use with workflows whitelist:

https://<vanity_url>.chatbot.aisera.<top_level_domain>/oauth2/authorize

Last updated

Was this helpful?