403 Permission Denied from Selenium webdriver

[chiapet92]

I'm working on switching over my application from a custom authorization to Google OIDC using these instructions.

I've integrated the button and sign-in features as recommended and the standard user-flow of:
page load -> user clicks on Google Sign-In button -> pop-up -> calls callback function, succeeds locally and in production.

The issue came up when I tried to refactor my automation testing to use the new user flow:
user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/88.0.4324.182 Safari/537.36
Upon clicking the Google Sign-In button, the pop-up dialog loads, but the follow console logs are generated.

{"level":"SEVERE","message":"https://myaccount.google.com/403 - Failed to load resource: the server responded with a status of 404 ()","timestamp":1614274089892,"type":""}
{"level":"SEVERE","message":"https://myaccount.google.com/403 - Failed to load resource: the server responded with a status of 404 ()","timestamp":1614274090581,"type":""}
{"level":"SEVERE","message":"http://google.com/403 - Failed to load resource: the server responded with a status of 404 (Not Found)","timestamp":1614274091086,"type":""}
{"level":"SEVERE","message":"https://google.com/403 - Failed to load resource: the server responded with a status of 404 ()","timestamp":1614274091885,"type":""}
{"level":"SEVERE","message":"https://accounts.google.com/403 - Failed to load resource: the server responded with a status of 404 ()","timestamp":1614274092437,"type":""}
{"level":"SEVERE","message":"https://accounts.google.com/403 - Failed to load resource: the server responded with a status of 404 ()","timestamp":1614274092793,"type":""}
{"level":"SEVERE","message":"http://google.com/403 - Failed to load resource: the server responded with a status of 404 (Not Found)","timestamp":1614274093286,"type":""}
{"level":"SEVERE","message":"https://google.com/403 - Failed to load resource: the server responded with a status of 404 ()","timestamp":1614274093998,"type":""}
{"level":"SEVERE","message":"http://google.com/403 - Failed to load resource: the server responded with a status of 404 (Not Found)","timestamp":1614274094787,"type":""}
{"level":"SEVERE","message":"https://google.com/403 - Failed to load resource: the server responded with a status of 404 ()","timestamp":1614274095488,"type":""}
{"level":"SEVERE","message":"https://google.com/403 - Failed to load resource: the server responded with a status of 404 ()","timestamp":1614274096191,"type":""}
{"level":"SEVERE","message":"https://accounts.google.com/403 - Failed to load resource: the server responded with a status of 404 ()","timestamp":1614274096491,"type":""}
{"level":"SEVERE","message":"https://accounts.google.com/403 - Failed to load resource: the server responded with a status of 404 ()","timestamp":1614274096884,"type":""}

On completion of the dialog, the pop-up closes, and onSignIn callback function was not called.

To me, it seems like the Google Sign-In pop-up is responding differently to being called by a selenium webdriver session vs a real user. Is my workflow supported? If this kind of testing should be working, what should I be looking to next for troubleshooting?

[ccdunder]

Thanks for reaching out. This bug tracker is intended to report bugs in the Google API JavaScript Client. This looks like a question about Sign In with Google.

For support with Sign In with Google issues, please see https://developers.google.com/identity; if you still need help, ask a question on Stack Overflow under the google-signin tag. If you determine there's an issue with google-api-javascript-client, feel free to open an issue here.

[ccdunder]

FWIW i'm not aware of any reason that the Google API Javascript Client would change it's behavior to redirect to these bogus urls (google.com/403 does not exist) under webdriver or any circumstances. It might help to dig into where those urls are constructed. As mentioned, google-signin tag on Stack Overflow will be able to provide further support.