OAuth Client Credentials Issue in Local Airbyte Setup

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

In a local Airbyte setup, OAuth client credentials function correctly when passed as JSON but fail when sent as URL-encoded content type. In contrast, the Airbyte cloud setup supports both content types without issues.


Question

In locally setup Airbyte ,oauth client crendentials working when credentials passed as json but not working when passed as urlencoded content type. But in airbyte cloud one it is working with both urlencoded and json one when credentials are send in one of the content-type


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', 'client-credentials', 'urlencoded', 'json', 'airbyte-local', 'airbyte-cloud']
2

For the future, please write in a thread or in a single message.

Back to your issue:
https://reference.airbyte.com/reference/createaccesstoken
According to docs, use content-type: application/json
As you discovered, it also works in both cases: Airbyte Cloud and Airbyte OSS

3

For the future, please write in a thread or in a single message.

Back to your issue:
https://reference.airbyte.com/reference/createaccesstoken
According to docs, use content-type: application/json
As you discovered, it also works in both cases: Airbyte Cloud and Airbyte OSS