You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once a user grants consent and is redirected back to airbyte, they should be redirected to an endpoint which will do the following:
call complete_auth_request on the backend server, providing the following inputs:
connector definition ID
current workspace ID
any query params found in the redirect URL
complete_auth_request will return an object containing some properties related to oauth e.g: {refresh_token: XYZ, access_token: XYZ, ...}. Using this response, the UI should pre-fill any fields with the same name. For example, if the spec has only {refresh_token: {type: string}} then the UI should pre-fill that field with the value returned from the API.
Display the spec as normal and allow the user to fill it out like normal
The below diagram illustrates how this would work. See the portion after "Redirect user to airbyte with auth code".
The text was updated successfully, but these errors were encountered:
Once a user grants consent and is redirected back to airbyte, they should be redirected to an endpoint which will do the following:
complete_auth_request
on the backend server, providing the following inputs:complete_auth_request
will return an object containing some properties related to oauth e.g:{refresh_token: XYZ, access_token: XYZ, ...}
. Using this response, the UI should pre-fill any fields with the same name. For example, if the spec has only{refresh_token: {type: string}}
then the UI should pre-fill that field with the value returned from the API.The below diagram illustrates how this would work. See the portion after "Redirect user to airbyte with auth code".
The text was updated successfully, but these errors were encountered: