From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Farblos <akfkqu.9df7rp@vodafonemail.de>
Cc: emacs-devel@gnu.org
Subject: Re: Extending auth-source and plstore for more XOAUTH2 scenarios
Date: Thu, 11 May 2023 17:04:20 -0400 [thread overview]
Message-ID: <m3h6sieg17.fsf@fitzsim.org> (raw)
In-Reply-To: <53d1fe04-9c66-fd9c-a9a4-3f7a05792b36@vodafonemail.de> (Farblos's message of "Thu, 11 May 2023 22:22:11 +0200")
Hi Farblos,
Farblos <akfkqu.9df7rp@vodafonemail.de> writes:
> I've made some extensions to package auth-source and plstore to cover
> more XOAUTH2 scenarios. My employer uses MS Office 365 with a device
> grant for the MUTT/Gnus/whatever outcasts, where you need additional
> URL parameters to refresh an access token. Plus I store the access
> token *and* its expiry date in a plstore to avoid token refresh cycles
> as much as possible.
[...]
> So much for the bigger picture. What do you think?
It would indeed be nice to have in GNU ELPA a package that has
configuration logic for IMAP/SMTP/POP3 OAuth 2.0.
I currently use the https://github.com/harishkrupo/oauth2ms Python
script for IMAP and SMTP XOAUTH2. Have you seen it? It's got excellent
documentation and the script has been solid. However, I would prefer to
eliminate the external Python script and have a pure Elisp solution. It
sounds like that's what you'd like to contribute, in which case, great!
Also have a look at url-http-oauth, which I just released to GNU ELPA
this week. It provides OAuth 2.0 support for HTTP services, and uses
the auth-source netrc backend. See if you may be able to make use of
parts of it. I started with netrc support because that's what I use,
and because authinfo.gpg can be GPG-encrypted. There's not much
netrc-specific though, so it might be worth trying with the plstore
backend if that's what you prefer.
Thomas
next prev parent reply other threads:[~2023-05-11 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 20:22 Extending auth-source and plstore for more XOAUTH2 scenarios Farblos
2023-05-11 21:04 ` Thomas Fitzsimmons [this message]
2023-05-18 0:04 ` Björn Bidar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3h6sieg17.fsf@fitzsim.org \
--to=fitzsim@fitzsim.org \
--cc=akfkqu.9df7rp@vodafonemail.de \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).