Token Management for Xero Airbyte Connector with Bearer Access Token Authentication

Summary

The user is inquiring about how Airbyte handles token management for the Xero connector with Bearer Access Token authentication to prevent sync interruptions upon token expiration.


Question

Hello <#C021JANJ6TY|>,
I’m using the Xero Airbyte connector from the Airbyte Marketplace to sync data to BigQuery with the ‘Bearer Access Token’ authentication method.
Given that the Xero access token expires every 30 minutes, I need to understand if Airbyte automatically handles the generation of a new token upon expiration or if the sync process will be interrupted and the connection will fail after 30 minutes if the token is not refreshed.

Any insights on how token management is handled when using the ‘Bearer Access Token’ authentication type would be greatly appreciated.



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

["xero-airbyte-connector", "bearer-access-token", "token-management", "sync-interruption", "authentication"]

Check this code https://github.com/airbytehq/airbyte/blob/458e96ea668366d3326d3f97fe477a30d8b6f838/airbyte-integrations/connectors/source-xero/source_xero/manifest.yaml#L11-L35|manifest.yaml#L11-L35

Thank you for your response, <@U05JENRCF7C>.

I explored the .yaml file and noticed that it outlines the process Airbyte follows for automatic access token generation once the token expires.

However, I want to specifically know about how token management is handled when using the ‘Bearer Access Token’ authentication type, not the ‘OAuth Custom Connection’ method. Will Airbyte manage automatic token generation once it expires, or will my pipeline fail after the token expires?