Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@irif.fr>
To: galene@lists.galene.org
Subject: [Galene] Heads up: group description format changes
Date: Tue, 09 Apr 2024 22:46:00 +0200	[thread overview]
Message-ID: <87zfu22rjr.wl-jch@irif.fr> (raw)

I'm almost ready to merge the "api" branch into master.  The group
description format is going to change, so here's a description of the
changes.

I haven't merged into master yet, so feel free to comment and criticise.


# Backwards compatibility is mostly preserved

Galene will continue reading old-format group descriptions, and
transparently convert them to the new format.  There are, however, some
minor details that will not be converted automatically:

  * "allow-anonymous" is ignored

    It is the default behaviour now.

  * It is no longer possible to have multiple users with the same username

    You used to be able to say

        "op": [{"username":"jch","password":"verysecret"}],
        "present": [{"username":"jch","password":"somewhatsecret"}],

    and Galene would choose the right permissions based on the password.  This
    is no longer possible, there can be only one user with a given username.

  * The config.json file has changed

    The "admin" field in the config.json file is ignored.  There is a new
    field "users".


# The new format

The following fields are obsolete:

  - op, presenter, other;
  - allow-anonymous.

In addition, The field "allow-subgroups" has been renamed to "auto-subgroups".

Instead of the three fields for users, there is just a single dictionary
called "users".  So instead of saying

    "op": [{"username":"jch","password":"verysecret"}],
    "present": [{"username":"john","password":"somewhatsecret"}],

you now say

    "users": {
        "jch": {"permissions": "op", "password": "verysecret"},
        "john": {"permissions": "present", "password": "somewhatsecret"}
    }

In order to convert fields with no username (wildcards), there is a new
field "fallback-users".  However, its use is not recommended -- tokens are
the new way of providing password-less access.


# Changes to the configuration file

The same changes have been applied to "config.json": the field "admin" is
obsolete, you should now say something like

    "users": {
        "jch": {"permissions": "admin", "password": "verysecret"}
    ]

Unlike the group files, which preserve compatibility, the config.json file
does not -- you'll need to modify it manually.


-- Juliusz

                 reply	other threads:[~2024-04-09 20:46 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=87zfu22rjr.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