@kapa.ai: Failes to obtain or add access token

"Failed to obtain or add access token" in Airbyte This error typically appears in Airbyte's workload-launcher or dataplane components and has been reported across several versions. Here's what's known about causes and fixes: Common Causes 1. Dataplane Client Credentials Issue The most common root cause is a problem with the

airbyte-auth-secrets

Kubernetes secret or the dataplane client credentials stored in the database. [GitHub Issue] One user reported that having the

airbyte-auth-secrets

secret pre-created externally (rather than letting Airbyte manage it) prevented the credentials from being updated properly, causing the token request to fail with HTTP 500. [GitHub Issue] 2. Upgrade from 1.7.x to 2.0.x (Dataplane Group Mismatch) After upgrading from 1.7.x to 2.0.x, a secondary authentication failure can occur in the workload-launcher:

ERROR - Failed to obtain or add access token
java.lang.Exception: Token request failed with HTTP code 500
Caused by: ClientException: Client error : 401 Unauthorized
ERROR - Failed to initialize data-plane

This is associated with stale Temporal workflows and dataplane group mismatches. [GitHub Issue] 3. Corrupted or Missing Dataplane Records If you manually deleted records from the database (e.g.,

DELETE FROM dataplane_client_credentials

and

DELETE FROM dataplane

), the dataplane secrets may not be recreated automatically, causing this error. [GitHub Issue] Suggested Fixes • For

abctl

deployments: Re-run the install command and give it time to complete:abctl local install --insecure-cookies -v[GitHub Issue] • For Kubernetes OSS deployments: Ensure the

airbyte-auth-secrets

secret is not pre-created or externally managed, so Airbyte can manage and update it automatically. [GitHub Issue] • For version-related issues: The token generation bug affecting versions 1.8.x (where

client_id

was missing or empty in the UI) was reported as resolved in the 2.0.0 release. [GitHub Issue] Additional Context If you are seeing this error during a long-running sync (not related to the platform auth), it may be a connector-level OAuth token expiry issue rather than a platform issue — for example, the

destination-gcs-data-lake

connector has a known bug where static OAuth2 tokens expire after ~1 hour. [GitHub Issue] Could you share more details about your Airbyte version, deployment method (abctl, Kubernetes, Docker), and where exactly the error appears? That would help narrow down the specific cause. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.