Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: Alexander Dietrich <alexander@dietrich.cx>
Cc: Galene Mailing List <galene@lists.galene.org>
Subject: [Galene] Re: Thoughts on global user passwords
Date: Sat, 26 Sep 2026 18:05:44 +0200	[thread overview]
Message-ID: <877bk86lrb.wl-jch@irif.fr> (raw)
In-Reply-To: <179043064484.1076.1779405941341360418@gauss>

> I've been experimenting with Galene recently, and really like it so far! Except
> for the part where you potentially have to create the same "op" user accounts
> in a bunch of groups, each with their own but identical password. (At least
> that's my understanding of the current system.)

Yes.  The reason it's not a problem for me is that I generally create
a whole hierarchy (using the "auto-subgroups" functionality) rather than
a distinct group for every task.

> I was wondering what you think about adding the ability to store
> usernames/passwords for regular users in the "users" map of "data/config.json"?

I've thought about it, but it's not that easy:

  - data/config.json is read-only, so it won't be possible to add new
    global users through the API;
  - you'd probably want users that only exist in a subhierarchy, for
    example a user that's an op in all groups under "group/teaching/*".

So my take would be to create a database of users, similar to the token
database.

I encourage you to design and implement a proof of concept, but please be
aware that it'll likely not be merged until we find satisfactory answers
to the questions above (and others).

-- Juliusz

           reply	other threads:[~2026-09-26 16:05 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <179043064484.1076.1779405941341360418@gauss>]

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=877bk86lrb.wl-jch@irif.fr \
    --to=jch@irif.fr \
    --cc=alexander@dietrich.cx \
    --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