Cross-client authentication with Backend. about react-google-login HOT 5 CLOSED

So the access_token you get from the react component is the one time token you can use on your server to get another token to be used later with api calls to other Google services like YouTube.

Also: 123SERVER123.apps.googleusercontent.com does not go into scope, it is your client id and should be the same on both the react component and on your server.

What library are you using for server side Google oAuth?

This might be what you need: https://developers.google.com/api-client-library/ruby/

from react-google-login.

Thanks Anthony! I appreciate the response!

On the backend I am using a youtube ruby gem https://github.com/Fullscreen/yt

I've used the access_token from the react component in the backend server to setup an account with this yt gem. That's what causes the 403 error.

Perhaps I cannot use the access_token directly on the server? But I must use that to get a new token for the server? I don't know how to do that with yt, but I can look into the api-client-library.

I can use the same client_id on front-end and backend, I was originally doing that.

from react-google-login.

Yes you will have to use the same client_id on the front and backend or it won't work.

I looks like you should be able to use the non-offline access_token from the component and use it in this, is that what you are currently trying?

# Content owners can be initialized with access token, refresh token or an authorization code content_owner = Yt::ContentOwner.new owner_name: 'CMSname', access_token: 'ya29.1.ABCDEFGHIJ'

from react-google-login.

No, I was using account = Yt::Account.new access_token: token. You were totally right, I should be using the ContentOwner class. Now works! Fantastic!

Basically, your module was working awesome I just was struggling to use the unrelated backend ruby stuff correctly. Thanks for saving my day!

from react-google-login.

Glad to hear.

from react-google-login.