[Users] Gmail OAuth2 Authorization Errors
Dustin Miller
dustbiz at gmail.com
Sat Apr 16 07:03:53 UTC 2022
On Wed, 13 Apr 2022 12:02:01 +0000
"David Fletcher" <David at megapico.co.uk> wrote:
> > > > * ?If you?re the app developer, make sure that these request
> > > > details comply with Google policies.
> > > > redirect_uri: urn:ietf:wg:oauth:2.0:oob
> > >
> > > I'm working on an update - I posted the first code to fix this
> > > yesterday on the Claws Mail developer list. However, that code was
> > > just a proof of how to overcome the problem - it needs integration
> > > into the Claws sources and testing to make sure it works properly.
> > > It's going to take a little time to work through fixing this.
> > >
> > DM: Hi, David. Thanks for your reply, and I really appreciate the
> > explanation ... as well as knowing that you're working on an update
> > related to this. ... ---Dustin
>
> Here's the info on fixing the Google Oauth2 deprecation issue (I'm
> assuming you are compiling Claws Mail from source):
>
DM: Thanks, David; this fix works for me. I appreciate you making this
available to us, and the clear concise instructions. Is this the type
of thing that will be mentioned in the notes of the next release if it
is included? It would be helpful to know at that point whether this fix
still needs to be applied manually. Thanks, ---Dustin
>
> (1) Replace
> "urn:ietf:wg:oauth:2.0:oob",
> with
> "https://127.0.0.1:8888",
> on line 50 of claws-mail/src/oauth2.c
>
> (2) Compile Claws Mail as normal.
>
> (3) Set up your account as normal.
>
> (4) Oauth2 authorization - Use the normal Open default browser
> button, or copy the code to your browser. Go through the Google
> authorization process as normal. After completing this Google will
> forward you to a web page that does not exist (see example screen
> attached). Copy the authorization code out of the URL and into the
> Claws Mail Authorization Code box. Make sure to copy just the code,
> not the whole URL, e.g. from the URL
> https://127.0.0.1:8888/?code=4/0AX4XfWiLeoP0OglH3-VeEIokX7Bm12L895CkWPlKqF3PkvqlhBtrjs7Aikxj_JeDk-xexQ&scope=https://mail.google.com/
>
> The code is this part:
> 4/0AX4XfWiLeoP0OglH3-VeEIokX7Bm12L895CkWPlKqF3PkvqlhBtrjs7Aikxj_JeDk-xexQ
>
> This is actually the way Microsoft Outlook and Exchange authorization
> works already.
>
> Longer term this can be improved to make it more automated and remove
> this copy/paste stage, but in the immediate term this fixes the
> deprecation issue with Gmail.
More information about the Users
mailing list