Issue with OAuth Token Management in Airbyte with Jira

Summary

The user is facing an issue with OAuth where Airbyte frequently calls for refresh_token renewal, leading to the revocation of refresh_tokens by Jira. There’s a conflict between the expected date format for expires_in and the numeric value provided by Jira, causing synchronization failures.


Question

Hey everyone,
I’m encountering an issue while working with Airbyte and Jira using OAuth. Here’s the problem:

When using Airbyte to fetch data from Jira via OAuth, there’s an issue where Airbyte makes frequent calls to the refresh_token to renew the access_token.
This causes Jira to detect an excessive number of refresh_token requests, leading to a revoke of the refresh_token, which results in the synchronization process failing.

Airbyte allows configuring the expires_in value (which defines the lifetime of the access_token), but the system requires this value to be provided in a date format, such as DD:MM:YY.
However, the expires_in value received from Jira is a numeric value in seconds (e.g., 3600 for one hour).
This discrepancy creates confusion and incompatibility in managing the token lifecycle.

If anyone has encountered a similar issue or knows how to resolve this, I’d really appreciate your help! :pray:
Thanks in advance!



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', 'jira', 'refresh_token', 'access_token', 'expires_in', 'airbyte']