Summary
Custom connector built using faros-airbyte-cdk with OAuth authentication needs guidance on updating new access and refresh tokens in the source.
Question
Hi Team, I’ve built a custom connector using the faros-airbyte-cdk with OAUTH authentication where a refresh token becomes invalid after it has been used to create an access token. In these situations, a new refresh token is returned along with the access token.
How do i go about updating the new access and refresh token in the source?
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
["custom-connector", "oauth-authentication", "access-token", "refresh-token", "faros-airbyte-cdk"]
Hi <@U071RJWTACS>, the faros-airbyte-cdk is not maintained by Airbyte, it’s maintained by Faros AI.
<@U047ANT3J84>: Well thank you so much for point out such an intricate piece of information.
I wonder if anyone would have ever gotten to know of it without you pointing out the obvious.
That definitely the most appropriate answer one can/should expect.
I don’t appreciate your tone, and I think it’s an appropriate piece of information to add. I was to conveying that Airbyte engineers (and likely other Airbyte contributors) will not have context on how that code works, and that you’re more likely to find success reaching out to Faros via any of their channels for help.