During Google OAuth setup, the workflow does not finish, instead it keeps hanging with a "Waiting for response from service" message.
I tried in incognito window to avoid issues with browser cache. I click the authorization link in Matillion and a new tab is opened; after sending my google credentials and approving the scopes the authorization flow shows a screen of 'Authorisation complete' in that tab, but in the matillion tab it keeps hanging.
This is ocurring in Matillion 1.50
HI @azucena.coronel ,
This might be a good question to throw at support as it could be a bug in Matillion's 1.50 version. The only thing I can think of to check would be to make sure the Matillion instance has connectivity to your Google environment from a network perspective. Even though the auth part might be working there could be inbound/outbound traffic being blocked on one or more services. Sorry I couldn't be of more help.
That is a very good point Bryan, thanks very much!
I'll check if there is any inbound/outbound traffic being blocked, great pointer thanks!
Hi. Did you have any luck solving this? Did it need an upgrade or was it some networking issue? We're having the same issue on 1.50 and wanted to understand what to expect
Even I am facing same issue. while configuring google analytics connection , when I add client ID & Client secret and try to authorize the account I am getting 'Authorisation complete' message but matillion screen shows 'Waiting for response from service'
have you resolved this? Appreciate your response
It worked for me. Here is the response from Matillion Support:
We've seen the behaviour you've described before where Matillion is waiting for a response and it is usually when there is a conflict with a browser plugin. To get around this issue, we recommend going through the same steps again, but this time with the browser in incognito/private mode.
If the above does not work, then it is likely linked to an issue caused in the latest versions of Chrome and Firefox that has most recently been resolved as of our 1.51.5 release or with using Internet Explorer.
Hello!
Thanks for the answer Tushar! Indeed a bit fiddly and browser dependant this behaviour.
After fiddling a bit without being able to make it work I decided to better use the OAuth authentication with Service Account
https://documentation.matillion.com/docs/2963740
I think it's also better to use a service account, to avoid needing that pop up to authenticate with a specific user.
I've used the service account for Google Analytics and Google Spreadsheets and it has been working consistently.
Cheers!
Have there been any new developments in the OAuth workflow problems with Google Analytics? I am using Matillion 1.50.6 launched from Snowflake Partner Connect. So my Matillion implementation is not a standalone - it launched from the Snowflake partner connect feature, which may make my situation different from others.
I am still encountering OAuth setup workflow issue. I have followed the instructions and links above. When using Chrome browser in incognito mode, the OAuth worklflow does not finish.. I have tried the service account method as well: https://documentation.matillion.com/docs/2963740 however I don't think I can store the service account p12 certificate file on a server. I am running Matillion via the Snowflake Parntner Connect and don't know where to setup the certificate file.
Has this been fixed?
Hi CR295672
I haven't been able to make it work via the oauth workflow, I'd suggest to raise a ticket to support as it might be a bug in that version.
I resolved the issue with the OAuth workflow by updating to the latest version of Matillion. For me, this was 1.58.4 . I did not expect to need an update considering this was a new install, but I was new to Matillion and did not know that this issue was in fact corrected.
From there, I had other issues using OAuth for google analytics that I could only resolve by using certain steps from various Matillion articles. Various connection options needed to be specified to get it work, as was the need to install an encryption key file to my VM to prevent the OAuth token from expiring.
The OAuth functionality has been working (fingers crossed) and it was a critical function for us. Hoping the setup and documentation for this can be improved for all users (and platforms).
any luck?