From: "Dernat Rémy" <remy.dernat@umontpellier.fr>
To: galene@lists.galene.org
Subject: [Galene] Re: User management
Date: Fri, 1 Oct 2021 16:43:32 +0200 [thread overview]
Message-ID: <4da2b65f-1843-a94c-69df-636c69b5f396@umontpellier.fr> (raw)
In-Reply-To: <9SCVvWIB9TfyEmG6di6LYCmoEeeJ_2Fsqzh8Y58_q0wSF1hRxJ_2I3YKATYXSCnaZQMJ6CdhvseVnbHsDmnSheS5b9SvRk1f9xhna0e2Y5Q=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 2060 bytes --]
Hi,
FYI, I created some months ago a basic room PHP project here:
https://github.com/remyd1/galene_room
Main goal was a bit different, because it was to let users create their
own room.
Admins, however, may delete rooms, list rooms, etc, using an API.
Best regards,
Le 28/09/2021 à 20:29, Jeroen van Veen a écrit :
> Hey!
>
> I'm working on and off a management interface for Galene in Pyrite
> (https://github.com/garage44/pyrite/issues/9)
> and was wondering how to best approach user management. Ideally the
> user definitions are separate from the group
> files. Any thoughts on a separate users.json that contains entries like:
>
> [
> {"name":"jeroen","password":"foobar","groups":{"pyrite":{"op":true,"presenter":true,"other":true}}},
> {"name":"pyrite","password":"foobar","groups":{}}
> ]
>
> The idea is to be able to set permissions per group, while having only
> one user entry at a central place. After modifying users.json,
> there will be another action from the backend that updates all
> accompanying group files. As I understand it, there is only 1
> administrator user
> defined in data/passwd? Would it be feasible to have multiple users in
> there, so each user can have an administrator flag?
>
> And what would be a good approach to delete or rename a group? Doing a
> request to the new group name works fine to make
> it available in the list, but I wonder what will happen to the group
> that is being renamed/deleted. Should I use protocol.js in the
> backend as well to connect to a group and kick all users out, before
> attempting to rename/delete it? If so, would it be useful to have
> a 'hidden' user available that can act on behalf of the backend?
>
> Cheers,
>
> Jeroen
>
>
> _______________________________________________
> Galene mailing list --galene@lists.galene.org
> To unsubscribe send an email togalene-leave@lists.galene.org
--
Dernat Rémy
Chef de projet SI, CNRS
Infrastructure des Systèmes d'Information ISI
ISEM Montpellier
[-- Attachment #2: Type: text/html, Size: 4346 bytes --]
next prev parent reply other threads:[~2021-10-01 15:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 18:29 [Galene] " Jeroen van Veen
2021-10-01 11:55 ` [Galene] " Juliusz Chroboczek
2021-10-01 14:05 ` Dave Taht
2021-10-01 14:20 ` [Galene] End-to-end encryption [was: User management] Juliusz Chroboczek
2021-10-01 14:38 ` [Galene] Re: End-to-end encryption Michael Ströder
2021-10-01 15:24 ` [Galene] Re: End-to-end encryption [was: User management] Dave Taht
2021-10-03 19:15 ` [Galene] Re: User management Jeroen van Veen
2021-10-26 19:02 ` [Galene] Config branch [was: User management] Juliusz Chroboczek
2021-10-27 18:23 ` [Galene] " Jeroen van Veen
2021-10-29 9:10 ` Jeroen van Veen
2021-10-29 17:52 ` Juliusz Chroboczek
2021-10-30 8:22 ` Jeroen van Veen
2021-10-01 14:43 ` Dernat Rémy [this message]
2021-10-03 19:15 ` [Galene] Re: User management Jeroen van Veen
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=4da2b65f-1843-a94c-69df-636c69b5f396@umontpellier.fr \
--to=remy.dernat@umontpellier.fr \
--cc=galene@lists.galene.org \
--subject='[Galene] Re: User management' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox