Google OAuth - Incorrect JSON while Validating Access Token

Question

I'm getting an access token from the Android SDK which I'm sending to the server. On the server side, I'm calling the following API to validate my token:

https://www.googleapis.com/oauth2/v1/tokeninfo?access_token=<token here>

From Google, I'm getting the following response (partial response added):

{\"statusCode\":200,\"body\":\"{n \"issued_to\": 
\"407408718192.apps.googleusercontent.com\",n \"audience\":
\"407408718192.apps.googleusercontent.com\",n \"user_id\": 
\"110586055381870434283\",n \"scope\": 
\"https://www.googleapis.com/auth/plus.login 
https://www.googleapis.com/auth/plus.me"}

Unfortunately, this JSON is not parseable because of the backslashes & i'm not able to validate the token identity.

Is this a problem with the Google API or do I need to apply any regex?

Were you able to find a solution for this? I am having the same issue. — Mitchell Ingram, Dec 04 '15 at 19:44

score 0 · Answer 1 · answered May 27 '15 at 16:00

0

Google sends back proper JSON without the slashes, being exactly the part that's inside the "body" element of the output that you paste (well without the slashes).

So your Node.js HTTP client is wrapping it with the HTTP status code element and puts in the slashes as well, so your clients need convert back from that on its own.

answered May 27 '15 at 16:00

Hans Z.

50,496
12
102
115

Any way to convert it back? I'm not able to find a solution – Rohit Lala May 28 '15 at 12:32
isn't it just the printout that adds the slashes? where/how do you print it out? – Hans Z. May 28 '15 at 13:59
I'm getting the slashes in the response itself. I'm using the npm module 'request' to hit the API. And the response is printed by JSON.stringify() – Rohit Lala May 28 '15 at 14:03
1

see http://stackoverflow.com/questions/16507858/json-stringify-escapes-double-quotes-every-time-when-stringified – Hans Z. May 28 '15 at 14:12

Google OAuth - Incorrect JSON while Validating Access Token

1 Answers1