google-api-php-client VS google-api-javascript-client

In Ruby on Rails GoogleAPI it is done by special return_url - urn:ietf:wg:oauth:2.0:oob. When a user granted their permission, the code is sent there and then Google notifies the application itself, so after granting permission user just log in into their account. Is there a similar thing for PHP or it's done different way? I found this repo https://github.com/googleapis/google-api-php-client but looks like it is deprecated and might not work.

API client for PHP

I'll insert the link here as well for convenient purpose. https://github.com/googleapis/google-api-php-client

in this walkthrough, we'll be modifying our existing laravel 8 restful(ish) api to accept logins via google and to read data about the user's google drive via the google api.

I am using this https://github.com/googleapis/google-api-php-client

Recommended by Google https://developers.google.com/identity/gsi/web/guides/verify...

I've been trying to use the Google Cloud Client Library for PHP and the Google APIs PHP Client github but all of the samples start with autoload.php in a vendor subfolder that doesn't download anywhere and i'm not sure what that's supposed to do.

Sometimes different JavaScript libraries are needed for in-browser vs node.js. I think that the npm googleapis package is specifically for node.js, and for in-browser use you need to use https://github.com/google/google-api-javascript-client

Incorrect, twice. We're not asking you to trust us, you can verify it yourself, Google Auth's scripts are open source. Here and here. They're also available in our repo as well.

API client for JavaScript

One interesting consequence of this is that Google's own javascript api client will no longer work with MV3 and there are apparently no plans to ever make it work.

See https://github.com/google/google-api-javascript-client/issue...

So effectively this means extensions on MV3 can't easily access Google apis, which is quite unfortunate since Chrome extensions in particular made Google authentication super straightforward (piggybacking off of chrome's built-in google authentication). If someone knows a better way I'd love to hear it.

I believe the reason that the current incarnation of the javascript library won't work is because it modifies the dom to add script tags to fetch and run the api library (or components of it), which is specifically what MV3 will disallow AFAIK.

What I want to do is contact the developers of this library. I looked at the google-api-client-libary for Javascript and thought about raising an issue due to the insufficient documentation, but the owners seem to be very slow in responding. How do I contact the developers and perhaps get a response in 1-2 days or at most a week?

Have you read the documentation and source? If so, maybe include the part that is confusing to you so people can help explain that specifically.

Here is an example of using Google APIs Client Library for browser JavaScript, aka gapi with no authentification. The Google Api we are calling here is Calendar API.

I have a Vue 3 / Quasar / TypeScript app that is using the Google API Client Library for JavaScript (also known as gapi).

I know that this is problem with server side rendering in my Next.js app and people recommend using a client side package like this https://github.com/google/google-api-javascript-client. But google-api-javascript-client doesn't have any documentation on authenticating with a .json credentials file instead of an API KEY which I do not have.

I've authenticated the user using Firebase successfully, giving me a user object to play with, however, to ping the Calendar API, I'm using the gapi library. This means, though, that I have to do the whole OAuth2 cycle twice - once to 'log in' the user to the application, and once to 'authorise' the application to use the user's token to use the Calendar API.