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

Google Search Console - Service Account Key Authentication Failure #19343

Closed
ghost opened this issue Nov 11, 2022 · 5 comments · Fixed by #22295
Closed

Google Search Console - Service Account Key Authentication Failure #19343

ghost opened this issue Nov 11, 2022 · 5 comments · Fixed by #22295

Comments

@ghost
Copy link

ghost commented Nov 11, 2022

Environment

  • Airbyte version: 0.40.16
  • OS Version / Instance: Debian GNU/Linux 10 VM instance
  • Deployment: Docker
  • Source Connector and version: Google Search Console 0.1.18
  • Destination Connector and version: BigQuery 1.2.5
  • Step where error happened: Setup new connection

Current Behavior

The connection tests failed.
"Unable to connect to Google Search Console API with the provided credentials - KeyError('siteEntry')"

Expected Behavior

Setting up connection

Logs

NA

Steps to Reproduce

  1. Setup GSC as described in Setup Guide
  2. Click "Setup source"

Are you willing to submit a PR?

Sure

@ghost
Copy link
Author

ghost commented Jan 2, 2023

Ok, so in the end it seems that the confusion is due to a mistake in the info window of the connector it says:

Website URL Property
The URLs of the website property attached to your GSC account. Read more here.
Example values
https://example1.com/ https://example2.com/

should be changed to

Website URL Property
The URLs of the website property attached to your GSC account. Read more here.
Example values
https://example1.com/ sc-domain:example2.com

and maybe also link this site

Prerequisites:
Enable Google Search Console API

I can claim this issue and submit a PR

@natalyjazzviolin
Copy link
Contributor

@sbrickel-nimble looking forward to the PR!

@dictcp
Copy link
Contributor

dictcp commented Feb 2, 2023

We encountered similar troubleshooting steps and would like to contribute (in #22295) on the documentation to save new comers' troubleshooting time.

@ghost
Copy link
Author

ghost commented Feb 2, 2023

Maybe we can merge our PRs ( #21260)

@dictcp
Copy link
Contributor

dictcp commented Feb 7, 2023

it would be great if either @natalyjazzviolin or @marcosmarxm can visit the PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants