docker container execution results in Access to XMLHttpRequest has been blocked by CORS policy: No 'Access-Control-Allow-Origin'

[marco]

1. downloaded docker container

2. run it on localhost:9000, used the client id from google oauth.

3. google OAuth being configured according to proposals

4. referencing a google sheet that properly works with the version hosted by thoughtworks itself, but it does not with the one I'm running locally in docker

Access to XMLHttpRequest at 'https://docs.google.com/spreadsheets/d/1l58pkwxOjLOxGUa85D3jmuQdwhC_1RYPWwGxxbVlfec' from origin 'http://localhost:9000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
5. hard reload of cash (Chrome) done several times, did not help anything

I have no further idea what to try, why is the docker container not working as the hosted instance is?

[Devansh Sharma]

Hi @marcopersi , you mentioned you are hosting the app on port 9000, but in the OAuth config your entry is for port 9090. Can you pls update either of them to match the ports and check ?

If that does not help, can you try to have only the localhost+port (eg: http://localhost:9000) entry in the OAuth config, and remove the http://localhost one ?

Thanks!

[marco]

Dear @devansh-sharma-tw

thank you for coming back. You were right. But unfortunately it didn't change anything:

I'm kind of surprised. Guess that it actually just should open the google verification popup/window , that's it.
But it does not, while it did from the hosted version.

Have you had the local docker version successfully running ?

[Devansh Sharma]

Hi marco,

Yes, the client ID is responsible for triggering the Google auth. I just tried on my local docker as well, with the latest master branch code. It's working fine.

From your last screenshot, I see a new error (the one that says "You have created a new client application....") in the Chrome console. Can you try expanding it and sharing a screenshot of what that says ? Seems to be related to the Google client ID itself.

Thanks!

[marco]

Hi I have now tried another Google Account, create new authentication credentials , same configuration as my own (http://localhost:9000 <http://localhost:9000/>) used the appropriate (new) client_id. The yellow rectangle is the link to the google sheet. If I test the link just as an URL in the browser it works. but not from the docker container. A browser setting? something that prevents the opening of the google oAuth popup being opened or so? Since it’s working from your container but not from mine, it must be a local config of my browser or google account best regards Marco

…

Am 20.10.2022 um 12:00 schrieb Devansh Sharma ***@***.***>: Hi marco, Yes, the client ID is responsible for triggering the Google auth. I just tried on my local docker as well, with the latest master branch code. It's working fine. From your last screenshot, I see a new error (the one that says "You have created a new client application....") in the Chrome console. Can you try expanding it and sharing a screenshot of what that says ? Seems to be related to the Google client ID itself. Thanks! — Reply to this email directly, view it on GitHub <#281 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFKEYL5F2Z4W7WOJDOY3YPTWEEJ4TANCNFSM6AAAAAARDS763M>. You are receiving this because you were mentioned.

[marco]

Hi again Update: - added a chrome plugin to get rid of the CORS Problem, that worked. - but there is still this. „idpiframe_initialization_failed“ there would be solutions on stackoverflow however, it means that I’ll have to build the src on my own best, marco

…

Am 20.10.2022 um 20:16 schrieb Marco Persi ***@***.***>: Hi I have now tried another Google Account, create new authentication credentials , same configuration as my own (http://localhost:9000 <http://localhost:9000/>) used the appropriate (new) client_id. The yellow rectangle is the link to the google sheet. If I test the link just as an URL in the browser it works. but not from the docker container. A browser setting? something that prevents the opening of the google oAuth popup being opened or so? Since it’s working from your container but not from mine, it must be a local config of my browser or google account best regards Marco <Bildschirmfoto 2022-10-20 um 20.11.14.png> > Am 20.10.2022 um 12:00 schrieb Devansh Sharma ***@***.*** ***@***.***>>: > > > Hi marco, > > Yes, the client ID is responsible for triggering the Google auth. I just tried on my local docker as well, with the latest master branch code. It's working fine. > > From your last screenshot, I see a new error (the one that says "You have created a new client application....") in the Chrome console. Can you try expanding it and sharing a screenshot of what that says ? Seems to be related to the Google client ID itself. > > Thanks! > > — > Reply to this email directly, view it on GitHub <#281 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFKEYL5F2Z4W7WOJDOY3YPTWEEJ4TANCNFSM6AAAAAARDS763M>. > You are receiving this because you were mentioned. >

[marco]

Dear @devansh-sharma-tw <https://github.com/devansh-sharma-tw> now I’m running the local checkout, without docker, git clone, running it... the full text of the details is: You have created a new client application that uses libraries for user authentication or authorization that will soon be deprecated. New clients must use the new libraries instead; existing clients must also migrate before these libraries are deprecated. See the [Migration Guide](https://developers.google.com/identity/gsi/web/guides/gis-migration) for more information. In the google console, I therefore obviously changed to localhost:8080 Refreshing cache did not help anything, might be that I’m trying to change your impl to the new google auth apis; since this might be time costly , pls don’t expect feedback too soon best

…

Am 20.10.2022 um 20:43 schrieb Marco Persi ***@***.***>: Hi again Update: - added a chrome plugin to get rid of the CORS Problem, that worked. - but there is still this. „idpiframe_initialization_failed“ there would be solutions on stackoverflow however, it means that I’ll have to build the src on my own best, marco <PastedGraphic-1.png> > Am 20.10.2022 um 20:16 schrieb Marco Persi ***@***.*** ***@***.***>>: > > Hi > > I have now tried another Google Account, create new authentication credentials , same configuration as my own (http://localhost:9000 <http://localhost:9000/>) > used the appropriate (new) client_id. > > The yellow rectangle is the link to the google sheet. If I test the link just as an URL in the browser it works. > but not from the docker container. > > A browser setting? something that prevents the opening of the google oAuth popup being opened or so? > > Since it’s working from your container but not from mine, it must be a local config of my browser or google account > > best regards > Marco > > <Bildschirmfoto 2022-10-20 um 20.11.14.png> > >> Am 20.10.2022 um 12:00 schrieb Devansh Sharma ***@***.*** ***@***.***>>: >> >> >> Hi marco, >> >> Yes, the client ID is responsible for triggering the Google auth. I just tried on my local docker as well, with the latest master branch code. It's working fine. >> >> From your last screenshot, I see a new error (the one that says "You have created a new client application....") in the Chrome console. Can you try expanding it and sharing a screenshot of what that says ? Seems to be related to the Google client ID itself. >> >> Thanks! >> >> — >> Reply to this email directly, view it on GitHub <#281 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFKEYL5F2Z4W7WOJDOY3YPTWEEJ4TANCNFSM6AAAAAARDS763M>. >> You are receiving this because you were mentioned. >> >

[Devansh Sharma]

Hi @marcopersi ,

Thanks for further checking on this.
We have also come to the conclusion on doing the auth library migration and are in the middle of the implementation right now.

Till the migration is done, newly created Client IDs would not work for Google Sheets URLs in local setups, as you have also observed. But JSON and CSV files will continue to work fine as they do not depend on Google Auth. We've further explained what is affected by this deprecation in the README here.

Thanks!