Shailendra Jaiswar
02/19/2026, 8:20 AMFailed to obtain or add access token
java.lang.Exception: Token request failed with HTTP code 500kapa.ai
02/19/2026, 8:21 AMFailed to obtain or add dataplane access token with HTTP 500) have been reported on 1.6.x and 1.8.x Helm/abctl installs. [[Could not deploy 1.6.0](https://github.com/airbytehq/airbyte/issues/58587)] In those cases, the problem was not about “region without organizationId”, but about dataplane auth / secrets / token generation. 2. Regions and organizationId For self‑managed / OSS Enterprise‑style setups, creating a region via /api/public/v1/regions requires an organizationId. In most OSS/Enterprise self‑managed docs, this is 00000000-0000-0000-0000-000000000000. [[Multi‑region 1.8](https://docs.airbyte.com/platform/1.8/enterprise-setup/multi-region#step-1)] There is no indication in the docs that you should or even can create a region without `organizationId`; it is documented as required. 3. Known 1.8.x token issues - There is a known “Invalid client id or token” / token generation problem on 1.8.0–1.8.2 that was reported as fixed in 1.8.3+ for the /api/public/v1/applications/token endpoint. [[getting error when getting token](https://github.com/airbytehq/airbyte/issues/65592)] - Another issue shows that even on 1.8.5 some users still had missing client_id in the UI and token problems, and the maintainers indicated this should be resolved in 2.0.0. [[Token generation fails after abctl install](https://github.com/airbytehq/airbyte/issues/65595)] 4. Secrets / auth configuration can break dataplane token flow In 1.6.x Helm installs, users seeing the same “Failed to obtain or add dataplane access token” error found it was related to how the airbyte-auth-secrets secret and instance admin auth were configured. One workaround was to not pre‑create and not externally manage that secret, and to comment out these Helm values so the chart manages them: [[Could not deploy 1.6.0](https://github.com/airbytehq/airbyte/issues/58587)] text global.auth.instanceAdmin.secretName global.auth.instanceAdmin.emailSecretKey global.auth.instanceAdmin.passwordSecretKey When those were commented out, the workload‑launcher became healthy. --- ### Direct answers to your questions - “Do I need to create a region without organizationId?” Based on the docs, no: organizationId is required when creating a region; for OSS/Enterprise‑style setups it is typically 00000000-0000-0000-0000-000000000000. [[Multi‑region 1.8](https://docs.airbyte.com/platform/1.8/enterprise-setup/multi-region#step-1)] - What is more likely causing the 500 on token request? From the issues, it is more likely related to: - Dataplane / workload API auth configuration, or - Secrets such as airbyte-auth-secrets and instance admin auth values being pre‑created or misconfigured, or - Known token bugs in 1.8.x Helm/abctl deployments. [[Could not deploy 1.6.0](https://github.com/airbytehq/airbyte/issues/58587); [Token generation fails after abctl install](https://github.com/airbytehq/airbyte/issues/65595)] Because the sources don’t include a definitive 1.8.5‑specific fix, I can’t give a guaranteed resolution, but based on them I would: 1. Ensure you are using the documented organizationId when creating regions (don’t omit it). 2. Check whether you have manually created or externally managed airbyte-auth-secrets or overridden global.auth.instanceAdmin.* in your Helm values; if so, try removing those overrides so Helm manages them. 3. If the problem persists, consider testing with a newer Airbyte version (2.0.0+) where maintainers state related token issues are resolved. [[Token generation fails after abctl install](https://github.com/airbytehq/airbyte/issues/65595)]Shailendra Jaiswar
02/19/2026, 8:49 AMorganizationId then how would I create region and dataplane?kapa.ai
02/19/2026, 8:49 AMkapa.ai
02/19/2026, 8:49 AMorganizationId in the request body. [[Multi‑region 1.8](https://docs.airbyte.com/platform/1.8/enterprise-setup/multi-region#step-1)] bash curl --request POST \ --url <https://example.com/api/public/v1/regions> \ --header "Authorization: Bearer $TOKEN" \ --header "Content-Type: application/json" \ --data '{ "name": "aws-us-east-1", "organizationId": "00000000-0000-0000-0000-000000000000" }' - For self‑managed Enterprise‑style deployments, the docs explicitly say: “In most cases, this is 00000000-0000-0000-0000-000000000000.” [[Multi‑region 1.8](https://docs.airbyte.com/platform/1.8/enterprise-setup/multi-region#step-1)] The knowledge sources do not describe any supported way to: - Omit organizationId, or - Discover a different organizationId for the community/OSS platform. So, based on what we have: - You must include an organizationId when creating the region. - For self‑managed style setups, the documented value to use is 00000000-0000-0000-0000-000000000000. [[Multi‑region 1.8](https://docs.airbyte.com/platform/1.8/enterprise-setup/multi-region#step-1)] Once the region is created with that organizationId, you can proceed with creating the data plane and configuring the Kubernetes secrets and values.yaml as shown in the multi‑region docs. [[Multi‑region step 4](https://docs.airbyte.com/platform/1.8/enterprise-setup/multi-region#step-4); [Multi‑region step 5](https://docs.airbyte.com/platform/1.8/enterprise-setup/multi-region#step-5)]