OAuth 2.0 Connector Authentication Issue with Airbyte


The user is facing an issue with OAuth 2.0 authentication in building a connector for an API. They are unable to provide the Basic token in the header or configure the Bearer token received in response. They are seeking guidance on how to address this issue.


I’m trying to build a connector for an API that uses OAuth 2.0.

The authentication process requires me to enter client_id, client_secret and a Basic token, which after the request, returns me a Bearer token, which allows me to get the data I need.

When selecting the OAuth method, Airbyte only prompts me to provide client_id and client_secret, I found no way of providing the Basic token in the header nor configure the Bearer token that I get in response to be used. Is there a way to do it?

That’s the <https://developers.hotmart.com/docs/en/start/app-auth/|platform docs>

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["oauth-2.0", "connector", "authentication", "api", "bearer-token", "basic-token", "airbyte"]

Based on the information provided in the extracts, Airbyte’s OAuth 2.0 authentication method currently supports the use of client_id, client_secret, and refresh_token to obtain an access token. This access token is then used in the Authorization header for subsequent requests. However, there is no explicit mention of support for a Basic token in the OAuth 2.0 authentication process. Here is an example of how the OAuth 2.0 authentication is configured in Airbyte, as shown in the Square API example: bash curl -X POST \ -H "Content-Type: application/json" \ -d '{"client_id": "&lt;client id&gt;", "client_secret": "&lt;client secret&gt;", "refresh_token": "&lt;refresh token&gt;", "grant_type": "refresh_token" }' \ &lt;token refresh endpoint&gt; The response is a JSON object containing an access_token property and an expires_at property. The access_token is then used in the Authorization header for subsequent requests. bash curl -X GET \ -H "Authorization: Bearer &lt;access-token&gt;" \ <https://connect.squareup.com/v2/&lt;stream> path&gt; However, if your API requires a Basic token as part of the OAuth 2.0 authentication process, this might not be directly supported by Airbyte’s current OAuth 2.0 authentication method. You may need to customize the authentication process in your connector to accommodate this requirement. For more detailed information on how to implement authentication in your connector, you can refer to the Authentication section of the Airbyte connector development documentation. Please note that the information provided here is based on the extracts provided and may not cover all possible scenarios or recent updates in Airbyte’s functionality. For the most accurate and up-to-date information, please refer to the official Airbyte documentation and resources.