Re: [Imap-protocol] OAUTH and IMAP
Michael M Slusarz <[email protected]>
| Newsgroups | gmane.mail.imap.general |
|---|---|
| Message-ID | <20140501221216.Horde.tVt3I3IxynGA-BHsdRqS5w6@bigworm.curecanti.org> |
Quoting "Jamie Nicolson (倪志明)" <[email protected]>: > This prints an access token that can login to [email protected], following the > instructions for XOAUTH2 Gmail access at > https://developers.google.com/gmail/xoauth2_protocol. I reported a viral bug/typo on that page months ago, but looks like it's still present. The sample client response is identified on that page as: [email protected]^Aauth=Bearer vF9dft4qmTc2Nvb3RlckBhdHRhdmlzdGEuY29tCg==^A^A (^A = ASCII 1) And the base64-encoded version of that is given as: dXNlcj1zb21ldXNlckBleGFtcGxlLmNvbQFhdXRoPUJlYXJlciB2RjlkZnQ0cW1UYzJOdmIzUmxj a0JoZEhSaGRtbHpkR0V1WTI5dENnPT0BAQo= The problem is that decodes to this string: [email protected]^Aauth=Bearer vF9dft4qmTc2Nvb3RlckBhdHRhdmlzdGEuY29tCg==^A^A<LF (ASCII 10)> The correct base64 representation is instead: dXNlcj1zb21ldXNlckBleGFtcGxlLmNvbQFhdXRoPUJlYXJlciB2RjlkZnQ0cW1UYzJOdmIzUmxj a0JoZEhSaGRtbHpkR0V1WTI5dENnPT0BAQ== michael _______________________________________________ Imap-protocol mailing list [email protected] http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol