@kapa.ai Received

Unexpected error when authenticating with identity provider

after enabling SSO

I'm sorry, but the knowledge sources do not contain specific information about the error message "Unexpected error when authenticating with identity provider." However, based on the available SSO documentation, here are the most common causes and troubleshooting steps: Troubleshooting SSO Authentication Errors 1. Verify your SSO configuration values Double-check the values entered in Organization settings > SSO: • Company identifier — must exactly match what you used in the redirect URI registered with your IdP • Client ID — copy directly from your IdP application settings • Client secret — ensure it hasn't expired (especially relevant for Azure Entra ID, which has expiring secrets) • Discovery URL — must be the correct OIDC metadata endpoint for your IdP [Okta SSO setup] [Entra ID SSO setup] 2. Check your redirect URI Ensure the redirect URI registered in your IdP exactly matches: • Cloud:

https://cloud.airbyte.com/auth/realms/<your-company-identifier>/broker/default/endpoint

• Self-Managed:

<your-airbyte-domain>/auth/realms/airbyte/broker/<app-integration-name>/endpoint

[Okta self-managed] 3. Verify user access in your IdP If the SSO configuration itself is correct, confirm that the user trying to log in has been granted access to the Airbyte application in your IdP (Okta or Entra ID). [Okta SSO setup] 4. Known issue: SSO fields locked after activation There is a known open issue where SSO configuration fields become read-only after activation, making it impossible to update settings like an expired client secret. If this applies to you, it's recommended to open a support ticket referencing the issue. [GitHub issue] If none of the above resolves your issue, please reach out via Airbyte Community Slack or open a support ticket with your specific error details. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.