search

Tenshinur / google-buzz-api

Automatically exported from code.google.com/p/google-buzz-api
0 stars 1 forks source link

oAuth 2.0 doesn't warn you or allow you to turn on your google buzz profile if the profile is disabled #152

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. get a brand new gmail account, do not enable or turn on your buzz 
2. grant consent to a third party to post on your buzz using the new oAuth 2
3. Third party will get an access token with no problem
4. when the third party tries to post it gets a 403 Buzz profile required

What is the expected output? What do you see instead?
With oAuth 1.0, users were able to turn on google buzz profile before 
generating the access token.
I would like to see the same behavior for oAuth 2.0

What version of the product are you using? On what operating system?

Please provide any additional information below.

{"error":{"errors":[{"domain":"global","reason":"accountDisabled","message" :" 
*Buzz profile required* 
","locationType":"header","location":"Authorization"}],"code":403,"message" :" 
*Buzz profile required*"}}

Original issue reported on code.google.com by Fermen...@gmail.com on 8 Apr 2011 at 8:36