I put it on a remote web server and got a redirect URI mismatch when signing into Google. It does the same when working on localhost.
Sorry for the late reply.
The URL where it is hosted needs to be registered with the Client ID from Google. You can put the connector on any web host, you then need to create your own Client ID with Google, and tell Google where you put the connector. Then update the connector code with your Client ID per the third paragraph in the original post.
We just made it easier to use this connector. Just point Tableau at this url: http://tableau.github.io/webdataconnector/Examples/GoogleSheetsConnector.html
It's the same connector, but now hosted on github.
Thanks, Dan. This works great.
Thanks for the great connector. It would be very useful for some or our Tableau use cases.
I've been successfully using the connector through the Github hosting. But in the end we should be able to use the data on our Tableau Server and there I get into trouble. After extracting your example, I first made a few changes:
- Referenced all files locally to avoid having a path
- Renamed the HTML file to only contain allowed characters
- Adjusted the redirect URL so that it points to the location of the HTML on our Tableau Server
- Imported all files to Tableau Server
I'm now able to use this connector from my Tableau Desktop and can refresh the data extract. Publishing also works (I am required to embed my credentials for the file) but the refreshing the extract on Server fails. It runs once successfully (see first screenshot), but subsequent extracts fail with an error complaining about a file not existing ([TableauTemp].[webdata.42376.942235682873.]) and not being able to connect to localhost.
I read somewhere that extracting web connectors on Tableau Server only works if they don't require authentication. I've tried doing that (the sheet is shared as "anyone with the link can view") but the Web Connector always requires me to authenticate, no matter what sharing settings I try.
Hope someone can help. Thanks in advance!
I sent Wouter an email earlier (let me know if you have any questions, Wouter), but in case anyone else is having a similar problem, here's what I have been able to find:
1. What Wouter is seeing above is expected. If you sign in to Google to connect to a Google spreadsheet with the WDC, the session associated with the OAuth token will expire at some point, and the next refresh will fail.
2. The WDC will require you to sign in to Google to connect to a spreadsheet, even if permissions were set to "anyone with the link can view," unless the spreadsheet is also published to the web.
I found that if I publish a spreadsheet first, I can connect without authenticating.
Hope that helps.