Hey everyone. Has anyone managed to setup the Goog...
# replication-troubleshooting
l
Hey everyone. Has anyone managed to setup the Google Analytics Connector w/ OAuth? It doesn't make sense to me that it requires a Refresh Token. Shouldn't it just need a ClientID/Secret and then the Access Token and Refresh Token come once a user authenticates?
e
Hi. The need in Oauth2.0 for refresh token is that the fetching the access token will skip all the first parts of the Authorization. if you dont have a refresh token then the client on the front end needs to approve the app or you need to create extra logic in the code which is bad practice in some cases since a refresh token can live X amount of time before running out so it is good practice to use an existing one and only authenticate.
l
Okay, thank you. It looks like I had to use the OAuth playground to get a token. Is that expected? https://developers.google.com/oauthplayground/ My thought would've been that we would have to put the clientID/Secret in a config setting in the backend and then via the front end the user can use OAuth to grant access to their specific google analytics acct.
e
Depends on the use case, in airbyte you would want to provide the refresh token in advance. Out side of airbyte, really depends on the flow you need so... hatd to say expected or not
o
@Luke Pammant Could you please share the screenshot of your setup (connector’s input config) ?
Just looked at both GA4 and GA(UA) using cloud - the OAuth working as expected without asking for refresh token. Please confirm you’re using dev UI or cloud test workspace to test the OAuth flow for Google Analytics (any revision) thanks.
s
i’m guessing luke is on OSS
👍 1
l
Yes @Sherif Nada is correct, I'm on the OSS version. I was wondering if there was a way to provide my ClientId/Secret so it works the same way the Cloud version works.
s
Not at the moment unfortunately. For OSS you need to input those manually