# 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.

<div align="left"><figure><img src="https://docs.aisera.com/~gitbook/image?url=https%3A%2F%2F2983236984-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiZkLJr3EjXkd2tHYiQJP%252Fuploads%252F1VlQhyYlpN440uwXBQKr%252Funknown.png%3Falt%3Dmedia%26token%3Dcae7324d-8f9e-4e13-8725-ba7fe2706230&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=8475a611&#x26;sv=2" alt="" width="375"><figcaption></figcaption></figure></div>

4. Select the **Generic** icon.
5. Click **Next**.
6. Fill in a **Name** for the integration and add the **Endpoint**.
7. Click **Next**.
8. Select **OAuthCustom** from the **Auth Type** pull-down list.

<div align="left"><figure><img src="https://docs.aisera.com/~gitbook/image?url=https%3A%2F%2F2983236984-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiZkLJr3EjXkd2tHYiQJP%252Fuploads%252FkvR8z2cWN1qpbTTZ8CxS%252Funknown.png%3Falt%3Dmedia%26token%3Deb6dcef3-97bc-46fb-a8ee-ea71af1d05f6&#x26;width=300&#x26;dpr=4&#x26;quality=100&#x26;sign=44b3cb8a&#x26;sv=2" alt="" width="375"><figcaption></figcaption></figure></div>

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

9. 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&#x20;

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).

![](https://docs.aisera.com/~gitbook/image?url=https%3A%2F%2F2983236984-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiZkLJr3EjXkd2tHYiQJP%252Fuploads%252FBhFVkmAPGCbAlhSTApwj%252Funknown.png%3Falt%3Dmedia%26token%3D72101aa3-b34f-4290-93f0-336b5436ae7e\&width=300\&dpr=4\&quality=100\&sign=76cb86e5\&sv=2)

10. Click **OK** to complete the authorization configuration.