New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
oauth_service_token Not working with scope as list/vector of urls, only as space delimited string #282
Comments
I ran into this, but then I can't get a request running afterwards. Do you have working example? If I modify the oauth2.0 example to use the JSON I have:
|
Mark, as a further issue with this, I had to manually create the request. I
|
Thanks, I just read this similar issue which suggests putting the token in the request parameters, sounds like what you are saying too :) |
FYI - this is what I ended up doing, kind of a hack..I had to change the function to get around the two issues I filed.
|
@craigcitro @siddharthab any idea where scopes are always space separated? |
I suppose it is a quirk. Did not have to be that way but it is. From https://developers.google.com/identity/protocols/OAuth2ServiceAccount > Preparing to make an authorized API call > HTTP/REST
|
Distinct possibility that I'm doing something completely wrong, but I can't seem to get this function to work. I believe in the past I have coded out the http request myself to get it to function. Here is some example code:
And from this I get:
However, this works:
and so does this:
It looks like it all comes down to needing to supply the scopes as a space delimited string (just like the Google API wants – keep in mind it may be different for different APIs). I am putting this here for posterity so should anyone else run into the problem, they have a solution. I will try to find the problem in the package itself and send a pull request – that is, if this isn't a planned "feature" in the first place.
The text was updated successfully, but these errors were encountered: