GNU bug report logs -
#41386
28.0.50; Gnus nnimap OAuth 2.0 support
Previous Next
Reported by: Thomas Fitzsimmons <fitzsim <at> fitzsim.org>
Date: Tue, 19 May 2020 02:06:01 UTC
Severity: wishlist
Tags: wontfix
Found in version 28.0.50
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Noam Postavsky <npostavs <at> gmail.com> writes:
> There is something called xoauth2, is that related? Someone posted a
> package for it, but the docs are a bit thin...
>
> https://github.com/ccrusius/auth-source-xoauth2
Below are the instructions for end-user usage. I think you can sum that
up as "er, no". :-/
1. Go to the developer console,
https://console.developers.google.com/project
2. Create a new project (if necessary), and select it once created.
3. Select \"APIs & Services\" from the navigation menu.
4. Select \"Credentials\".
5. Create new credentials of type \"OAuth Client ID\".
6. Choose application type \"Other\".
7. Choose a name for the client.
This should get you all the values but for the refresh token. For that one:
1. Clone the https://github.com/google/gmail-oauth2-tools repository
2. Execute the following command in the cloned repository:
python2.7 python/oauth2.py
--generate_oauth2_token \
--client_id=<client id from previous steps> \
--client_secret=<client secret from previous steps>
You should now have all the required values (the :token-url value should
be \"https://accounts.google.com/o/oauth2/token\").")
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
This bug report was last modified 2 years and 200 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.