The first problem is that the old SID authentication didn't require
the username to include a domain, whereas auth token authentication
does (at least, according to http://code.google.com/apis/accounts/docs/AuthForInstalledApps.html#Request
). There have been a few FeedDemon customers who reported
authentication failures that went away after they appended
"@gmail.com" to their username. Because of this, I'm now
programmatically adding "@gmail.com" to the username if no domain is
specified.
And I have one customer who has been unable to use FeedDemon ever
since the authentication switchover - every request failed with HTTP
502. After quite a bit of back-and-forth with this customer, it
became clear that they were stuck using a corporate proxy server that
was mangling the request/response. There's nothing you can do in this
situation except cross your fingers that their IT department is
willing to fix the proxy (unlikely, in my experience!), but if you're
seeing customers reporting this problem, at least you know it's not
your fault :)
Nick
Thanks for sharing. Very valuable and essential information. I got
reports of users entering the wrong password, but then it was probably
just this.
Adding @gmail.com probably doesn't work all the time, or would this
also work for the users that have accounts that end in googlemail.com?
Again, thanks for sharing.
Cheers,
Mariano
> To unsubscribe from this group, send email to fougrapi+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
>
On Mar 22, 11:51 am, Nick Bradbury <nick.bradb...@gmail.com> wrote:
> FeedDemon switched to the "new" auth token authentication method last
> month, and for the most part the change was a non-event: most
> customers weren't aware of the switchover and experienced no
> problems. I have had a few bug reports resulting from the change,
> though, and I thought it might help if I shared them here.
>
> The first problem is that the old SID authentication didn't require
> the username to include a domain, whereas auth token authentication
> does (at least, according tohttp://code.google.com/apis/accounts/docs/AuthForInstalledApps.html#R...
This is just a guess, but my assumption is that since googlemail.com
redirects to mail.gmail.com, then this should still work.
Nick
Can't explain it, just reporting it :)
Nick
Thanks for the reports and tips. Much appreciated!
Kind Regards,
-Nik