From: Demetrius Iatrakis <demetrius.iatrakis@gmail.com>
To: 9fans <9fans@9fans.net>
Cc: 9front@9front.org
Subject: [9front] Re: [9fans] OAuth2 in factotum
Date: Sun, 22 Aug 2021 23:32:13 +0300 [thread overview]
Message-ID: <CALo7eEusX6z88gkWZyOv6tDmHk4wWNmpdB=v+-QycdRp27dWgw@mail.gmail.com> (raw)
In-Reply-To: <FEF7A1A8AA43660462E5C685BBCF3230@eigenstate.org>
Thank you for your work.
Don't forget to add
type is text
dst is oauth
plumb to oauth
to your plumber's rules file to create the oauth port.
I have also added the authorization code flow to the factotum module
(can be enabled by adding `flow=auth` to the key), but it requires the
user to import the plan9port plumber into factotum's namespace. I am
unsure what the best way to do this is. Plan9port provides import(4)
which relies on SSH, but 9front does not provide an SSH server.
--
Demetrius
next prev parent reply other threads:[~2021-08-22 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALo7eEuXOfgr=2nj7A-rKNDejHdyBHWg98eJhvmLTneNaM5=Gw@mail.gmail.com>
2021-08-22 20:16 ` ori
2021-08-22 20:32 ` Demetrius Iatrakis [this message]
2021-08-22 20:38 ` ori
2021-08-22 20:36 ` ori
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALo7eEusX6z88gkWZyOv6tDmHk4wWNmpdB=v+-QycdRp27dWgw@mail.gmail.com' \
--to=demetrius.iatrakis@gmail.com \
--cc=9fans@9fans.net \
--cc=9front@9front.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.
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 NNTP newsgroup(s).