From: Juliusz Chroboczek <jch@irif.fr>
To: galene@lists.galene.org
Subject: [Galene] Bearer tokens in the administrative API
Date: Tue, 23 Jun 2026 17:27:11 +0200 [thread overview]
Message-ID: <87se6dxoog.wl-jch@irif.fr> (raw)
I've just pushed code to authentify using bearer tokens in the
administrative API. This touches a lot of the auth code, albeit in minor
ways; I've tried to be careful, and hopefully didn't introduce any
security flaws.
Assuming you've got galenectl configured, crate a global admin token:
galenectl -insecure create-token -group "" -include-subgroups -permissions admin
Now edit your galenectl.json file: remove the "admin-password" field, and
replace it with an "admin-token" field that contains the newly generated
token.
While in principle the code supports cryptographic tokens (JWTs), in
practice it won't work with them, since there are no global keys yet. I'm
not quite sure where to store global keys: in the config file? In
a separate JWK file?
In the first place: what are the use cases for global stateless tokens?
-- Juliusz
reply other threads:[~2026-06-23 15:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87se6dxoog.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=galene@lists.galene.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