unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Farblos <akfkqu.9df7rp@vodafonemail.de>
Cc: emacs-devel@gnu.org
Subject: Re: Extending auth-source and plstore for more XOAUTH2 scenarios
Date: Thu, 18 May 2023 03:04:10 +0300	[thread overview]
Message-ID: <874joa7bet.fsf@thaodan.de> (raw)
In-Reply-To: <53d1fe04-9c66-fd9c-a9a4-3f7a05792b36@vodafonemail.de> (Farblos's message of "Thu, 11 May 2023 22:22:11 +0200")


Hello,

I'm not sure how exactly that relates to this issue. But sasl.el that
was taken from FLIM, FLIM supports XOAUTH2.

FLIM is used in Wanderlust for this kind of purpose I think it.
It would make sense to import sasl-xoauth2 and sasl-scram for
completeness into Emacs.

I worked with signon-plugin-oauth2 in the past to implement the
Microsoft OAuth2 Workflow.
I have a few pointers regarding that:
- Microsoft's way of doing OAuth2 with a clientid rather than a client
  secret is ironically much friendlier to FOSS programs such as
  Emacs. Emacs can simply write the clientid inside the sources after
  registering an AppID at Microsoft. An example where this was already
  done is KDE PIM/Akonadi.
  No further intervention is needed on the user side besides pointing
  the user to the webpage to give Emacs the permission to access all the
  requested areas.
- I think it would make sense to see how Wanderlust implemented OAuth2
  for Microsoft.
- Take pointers from other existing implementations that try to add Microsoft
  Oauth to Gnus.

Br,

Björn Bidar



      parent reply	other threads:[~2023-05-18  0: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
2023-05-18  0:04 ` Björn Bidar [this message]

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=874joa7bet.fsf@thaodan.de \
    --to=bjorn.bidar@thaodan.de \
    --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).