Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 UI & UX: default values are not loaded for OAuth Flow #8837

Closed
bazarnov opened this issue Dec 16, 2021 · 0 comments · Fixed by #8856
Closed

🐛 UI & UX: default values are not loaded for OAuth Flow #8837

bazarnov opened this issue Dec 16, 2021 · 0 comments · Fixed by #8856
Assignees
Labels
needs-triage type/bug Something isn't working

Comments

@bazarnov
Copy link
Collaborator

Environment

  • Airbyte version: dev
  • OS Version / Instance: any
  • Deployment: Docker
  • Source Connector and version: no matter
  • Destination Connector and version: no matter
  • Severity: High/Critical
  • Step where error happened: Setup new connection

Current Behavior

While setting up the connector, the UI doesn't preload the default values that are set with default parameter inside of ConnectorSpecification. As the result, we hit the error (see the video attached).

Expected Behavior

The default values coming from the ConnectorSpecification should be preloaded before the Authenticate button is pressed.

Logs

Oauth_default_values.mov

Steps to Reproduce

  1. Run the DEV version of UI locally, along with DEV version of Airbyte instance.
  2. Modify any of existing connectors suitable for OAuth2.0 to have the default value for the field that should be passed from Front-end to Back-end to pass the Authentication using OAuth2.0. (you can use this PR for the test as well)
  3. Rebuild and change the version of the connector to be the dev in the settings.
  4. Create the source connection.
  5. Don't touch the field you are testing, during the connection setup.
  6. Press the Authenticate button - you should see nothing happens.
  7. Check the console/network for broken requests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants