There appears to be a bug in the new OAuth code for multiple accounts: http://stackoverflow.com/questions/12478524/has-google-pushed-an-update-to-their-oauth2-0-flow-that-breaks-multiple-accounts
Is there any way to upgrade the Google Oauth token and secret obtained using OAuth 1.0 to OAuth2 access token?
My application is having around 800+ Google users and if each user needs to go through the whole OAuth process again, it will be painful for them.
Haven't seen any posts regarding this anywhere. Any help would be much appreciated as I have already moved my app to OAuth2 and need a way out for these users asap.
Starting yesterday, my XMPP (jabberd) server can no longer communicate with the gmail.com XMPP servers. It fails with the message "dialback negotiation failed". Is this related to the recent roll out of OAuth 2.0? Because of this, my users can no longer communicate with @gmail.com addresses.
Last I heard, OAuth was easily compromised due to inherent vulnerabilities, so how does it add *anything* to security? Or does OAuth 2.0 fix them?
ReplyDeleteThe statement about a stolen device's security are a joke. All browsers have a show password option for each and every site.
ReplyDeleteThats why you have 2-Factor Auth turned on, right? :P
Deletehttp://support.google.com/accounts/bin/answer.py?hl=en&answer=180744
There appears to be a bug in the new OAuth code for multiple accounts: http://stackoverflow.com/questions/12478524/has-google-pushed-an-update-to-their-oauth2-0-flow-that-breaks-multiple-accounts
ReplyDeleteWhat options remain for normal username/password login to Google Talk? Or is it going to be OAuth 2.0 only?
ReplyDeleteIs there any way to upgrade the Google Oauth token and secret obtained using OAuth 1.0 to OAuth2 access token?
ReplyDeleteMy application is having around 800+ Google users and if each user needs to go through the whole OAuth process again, it will be painful for them.
Haven't seen any posts regarding this anywhere. Any help would be much appreciated as I have already moved my app to OAuth2 and need a way out for these users asap.
Thanks in advance,
Starting yesterday, my XMPP (jabberd) server can no longer communicate with the gmail.com XMPP servers. It fails with the message "dialback negotiation failed". Is this related to the recent roll out of OAuth 2.0? Because of this, my users can no longer communicate with @gmail.com addresses.
ReplyDeletec'est une mesure de sécurité importante qui v'as donner confiance aux internautes et aux entreprises d'opter pour google chrome
ReplyDeleteWould be nice if RAW IPs were supported in a test mode so we can test apps on an internal network before releasing as well...
ReplyDeletep.s., your OpenID integration is broken for blog comments...shows as "anonymous" :-P
Would be nice if you could use Raw IPs in a "test" mode as well...this is for testings apps internally before release.
ReplyDeleteTHANK YOU.
ReplyDelete