Custom OAuth Token Extraction Issue

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

Summary

User is facing an issue while configuring OAuth authentication for a custom connector due to the token being nested in the API response. Inquires about how to specify the correct access token property name for Airbyte’s expected format.


Question

Hello, I’m trying to build a custom connector for an API but when I setup the authentication using OAuth, I’m not able to select the token returned from the API as it is nested in response > body > data > token and not response > access_token like Airbyte is expecting by default. What am I supposed to put in “Access Token Property Name” to select the token correctly?


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-authentication', 'custom-connector', 'api-response', 'access-token-property-name']
2

Did you try to use Refresh Token Property Name as token?

3

<@U01MMSDJGC9> yes but it says key not found because ‘token’ is nested in the api response, something like this:

{'response': {'body': {'data': {'token':123)}}}

4

It seems a limitation today Nawfel. Please open <https://github.com/airbytehq/airbyte-python-cdk|an issue> reporting your use case for future implementation.

5

I was actually able to make it work by using “Session Token” method which gives more flexibility to specify how to get the token from the response, I didn’t see that option before