search

Tenshinur / google-buzz-api

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

Authorization page of Google Buzz does not support multi sign-in #136

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Enable multiple sign-in in Google Account
2. Use OAuth to authorize my web site to google buzz
3. At the first page of authorization step on 
https://www.googleapis.com/auth/buzz, the right top of the page displays my 
default account
4. In the next page on https://www.google.com/accounts/OAuthAuthorizeToken, 
which supports multiple sing-in, choose a non-default account
5. Authorize the web site. 

It looks as if it succeeds, but not in fact. When my web site tries to create 
an activity, it gets 401 error.

I think the authorization page of google buzz should support multiple sign-in 
as well, or at least document this or give the user an notification.

Thanks

Original issue reported on code.google.com by GildorW...@gmail.com on 18 Dec 2010 at 8:15

GoogleCodeExporter commented 8 years ago 
This is WorkingAsintended because Buzz currently only works for @gmail.com 
addresses. However I'm leaving this bug open since we should make it more 
obvious that this is what's going on.

Original comment by a...@google.com on 20 Dec 2010 at 10:22

GoogleCodeExporter commented 8 years ago 
Maybe I did not describe clearly enough. 
Say I have two @gmail.com addresses. After turning on 'Multiple Sign-in' in my 
Google Account page, I can keep both of them in login state. Assume there are 
A@gmail.com and B@gmail.com while A@gmail.com is the default account.

When I'm navigated to the google buzz authorization page, the account shown on 
the right top of the page is A@gmail.com and I cannot choose the other since 
this page does not support multiple sign-in.

However, after this step, I'm navigated to google account authorization page 
which supports multiple sign-in. So I can click to choose the other account 
B@gmail.com on the right top of the page. 

Then Google Accounts authorizes B@gmail.com but it is A@gmail.com that Google 
Buzz has authorized.

This is why I was keeping getting 401 when playing with Buzz API. Maybe it is 
not so serious a problem, or it's not that worthy to fix it, but I do hope you 
guys add a note or warning in the docs and on the authorization page to prevent 
users from getting into such a situation. Anyway, it really took me quite a 
while to figure out the reason.

Thanks

Original comment by GildorW...@gmail.com on 20 Dec 2010 at 5:48

GoogleCodeExporter commented 8 years ago 
Thank you. That is much clearer.

Original comment by adewale on 3 Jan 2011 at 10:38