OAuth Custom

The OAuth Custom authorization type is now available in the authentication dropdown for Generic Connectors.

This feature was developed in response to customer requests for supporting non-standard authentication fields and flows, enabling integration with third-party systems that require custom key-value pairs.

To use the OAuth Custom Authorization Type:

1. Navigate to Settings > Integrations in the Aisera Admin UI.

2. Choose the + New Integration button in the upper-right corner.

3. Type Generic in the Search field.

1. Select the Generic icon.

2. Click Next.

3. Fill in a Name for the integration and add the Endpoint.

4. Click Next.

5. Select OAuthCustom from the Auth Type pull-down list.

Choosing OAuthCustom displays a full set of fields for custom authentication.

1. Enter the parameters you want to use for authorization. The parameter fields correspond to the following authorization fields in a database:

• tokenPrefix (string)

• access_token_url (string)

• accessTokenMethod (string)

• accessTokenBodyIsJson (checkbox)

• encryptedAccessTokenBody (encrypted string, JSON snippet)

• encryptedAccessTokenHeaders (encrypted string, JSON snippet)

• accessTokenExtractionPath (string)

• refreshTokenExtractionPath (string)

• expiresInExtractionPath (string)

• useRefreshToken (checkbox)

• refreshTokenURL (string) — Note: The field is now camelCase (refreshTokenURL) for backend compatibility (previously refresh_token_url)

• refreshTokenMethod (string)

• refreshTokenBodyIsJson (checkbox)

• encryptedRefreshTokenBody (encrypted string, JSON snippet)

• encryptedRefreshTokenHeaders (encrypted string, JSON snippet)

• accessTokenExtractionPathFromRefreshRequest (string)

• refreshTokenExtractionPathFromRefreshRequest (string)

• expiresInExtractionPathFromRefreshRequest (string)

• trustAnySSLCertificate (checkbox)

• clientCertificateP12Path (string)

• clientPrivateKeyPem (encrypted string)

• clientCertificatePem (encrypted string)

• customSSLCertificate (encrypted string)

• Security & Usability Enhancements

All encrypted fields (encryptedAccessTokenBody, encryptedAccessTokenHeaders, encryptedRefreshTokenBody, encryptedRefreshTokenHeaders) are stored as strings in the auth_config JSON to ensure proper encryption/decryption by the backend. Encrypted fields are masked for all users except those with the Administrator role.

For users with an Administrator, an eye icon is displayed to reveal secret values in password-type fields. For fields accepting JSON data, the eye icon is not available due to technical limitations (these are not password fields).

1. Click OK to complete the authorization configuration.