Reports of issues with Oauth in Google Gadgets

[Andy "Rufus" Rothfusz]

We're investigating reports of HTTP 500 errors being returned to
gadgets requesting OAuth tokens.
This appears to affect new users and new gadgets.

If you or your users are experiencing this problem, please let us know
the first time this problem appeared in the following thread:

https://groups.google.com/group/google-apps-gadgets-api/browse_thread/thread/de31f9462e5d6818#

If you can arrange for us to reproduce the problems, let us know that
fact in your posting, and we will contact you to get the repro steps
from you.

Engineers are currently looking into the bad behavior.

[Andy "Rufus" Rothfusz]

Hello,

We pushed a fix last night and now this issue should be resolved for
all users.
I'm sorry for the difficulty this caused you and your customers.

The problem was in how we were parsing OAuth parameters in 3-legged
Oauth.
The issue appeared to affect new users and new gadgets because
most existing users had already obtained their OAuth tokens and
new users had never been authenticated, but actually the problem
affected all 3-legged OAuth.

The rollout of the fix to production completed this morning at a
little before 8:30am Pacific time.

Regards,

Rufus