@kapa.ai what is this error when try to auth salseforce

trackError() failed because RUM is not initialized. Error:
 HttpError: errors.http.internalServerError
    at fyt (core-l0xde5f173.js:56:1032)
    at async getConsentUrl (core-l0xde5f173.js:435:44912)
    at async core-l0xde5f173.js:435:46374
 Context:

{i18nKey: 'errors.http.internalServerError', i18nParams: {…}, name: 'HttpError', requestId: 'arrrzaGzJbH173imoTZWTh', request: {…}, …}
fullStory
:
undefined
i18nKey
:
"errors.http.internalServerError"
i18nParams
:
{status: 500}
name
:
"HttpError"
request
:
{url: '/api/v1/destination_oauths/get_consent_url', method: 'POST', headers: {…}, data: {…}}
requestId
:
"arrrzaGzJbH173imoTZWTh"
response
:
{message: 'Internal Server Error: Requested OAuth implementat…fix, but it is not included in the oauth mapping.', exceptionClassName: 'java.lang.IllegalStateException', exceptionStack: Array(0), rootCauseExceptionStack: Array(0)}
status
:
500
[[Prototype]]
:
Object

Salesforce OAuth 500 Error: "Not included in the oauth mapping" The error you're seeing is: >

Internal Server Error: Requested OAuth implementation for [connector], but it is not included in the oauth mapping.

This is a known issue that occurs when a connector does not have a built-in OAuth implementation registered in Airbyte's internal OAuth mapping. In your case, it's happening on the destination Salesforce connector (

/api/v1/destination_oauths/get_consent_url

). What's happening When Airbyte 1.4+ introduced a new OAuth flow, connectors that lack a

DeclarativeOAuthFlow

(or a legacy OAuth2.0 implementation registered in the platform's OAuth mapping) will throw this 500 error when you click the "Authenticate" button. [RD Station OAuth issue] What you can try 1. Re-authenticate: If you had a previously working connection, try editing the source/destination and re-authenticating. Expired or revoked credentials can sometimes surface as OAuth errors. [Google Sheets 500 issue] 2. Manually provide credentials: Instead of using the OAuth button, try entering your Salesforce credentials manually:For the destination-salesforce connector specifically, verify your Connected App's Consumer Key and Consumer Secret are correct, and ensure the Is Sandbox setting matches your Salesforce environment. [Salesforce destination docs] ◦ Consumer Key (Client ID) ◦ Consumer Secret (Client Secret) ◦ Refresh Token (obtained directly from Salesforce) 1. Check your Airbyte version: This issue has been observed on Airbyte 1.4+. Make sure you're on the latest version, as fixes may have been released. 2. OAuth scopes: A recent update (connector version

2.7.23

) added explicit OAuth scopes (

api

,

web

,

refresh_token

,

lightning

) to the Salesforce source connector's consent URL. If you're on an older version, upgrading the connector may help. [Salesforce OAuth scopes PR] Note The knowledge sources don't contain a definitive fix specifically for the destination-salesforce OAuth mapping issue. If the above steps don't resolve it, I'd recommend opening an issue on the Airbyte GitHub or checking the Airbyte community Slack for the latest updates. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.