# 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.
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.
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
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).
10. Click **OK** to complete the authorization configuration.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.aisera.com/aisera-platform/adding-data-to-your-tenant/integrations-and-data-sources/supported-auth-types-for-custom-integrations/oauth-custom.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
