MBOX-Line: From slusarz at curecanti.org  Thu May  1 21:12:16 2014
To: imap-protocol@u.washington.edu
From: Michael M Slusarz <slusarz@curecanti.org>
Date: Fri Jun  8 12:34:52 2018
Subject: [Imap-protocol] OAUTH and IMAP
In-Reply-To: <CACU8CfSWORaqU=NG6DrxTXFoam3N0BHFdngb91HZgJrBtTFj+Q@mail.gmail.com>
References: <53608FE7.8090909@verizon.net>
	<CABa8R6sJQ0SV5O_udOusA983vE5NNbuRt27VthkCPuMbAge2yA@mail.gmail.com>
	<5360FF8D.9000201@comaxis.com>
	<20140430143517.743B37306E@mailwash38.pair.com>
	<53611C4E.7030904@comaxis.com>
	<CACU8CfSWORaqU=NG6DrxTXFoam3N0BHFdngb91HZgJrBtTFj+Q@mail.gmail.com>
Message-ID: <20140501221216.Horde.tVt3I3IxynGA-BHsdRqS5w6@bigworm.curecanti.org>

Quoting "Jamie Nicolson (???)" <nicolson@google.com>:

> This prints an access token that can login to foo@bar.com, 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:

user=someuser@example.com^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:

user=someuser@example.com^Aauth=Bearer  
vF9dft4qmTc2Nvb3RlckBhdHRhdmlzdGEuY29tCg==^A^A<LF (ASCII 10)>

The correct base64 representation is instead:

dXNlcj1zb21ldXNlckBleGFtcGxlLmNvbQFhdXRoPUJlYXJlciB2RjlkZnQ0cW1UYzJOdmIzUmxj
a0JoZEhSaGRtbHpkR0V1WTI5dENnPT0BAQ==


michael


