From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mail.toke.dk; dkim=none; arc=none (Message is not ARC signed); dmarc=fail (Used From Domain Record) header.from=dietrich.cx policy.dmarc=reject Received: from mout-p-101.mailbox.org (mout-p-101.mailbox.org [80.241.56.151]) by mail.toke.dk (Postfix) with ESMTPS id C97C917024DB for ; Sat, 26 Sep 2026 15:50:42 +0200 (CEST) Received: from smtp2.mailbox.org (smtp2.mailbox.org [IPv6:2001:67c:2050:b231:465::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-101.mailbox.org (Postfix) with ESMTPS id 4hsTVS2y13z8sYS for ; Sat, 26 Sep 2026 15:50:40 +0200 (CEST) Date: Sat, 26 Sep 2026 15:50:39 +0200 (CEST) From: Alexander Dietrich To: Galene Mailing List Message-ID: <875895670.207844.1790430639655@app.mailbox.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_207843_1141799579.1790430639654" X-Priority: 3 Importance: Normal X-Rspamd-Queue-Id: 4hsTVS2y13z8sYS Message-ID-Hash: AMDOAUKUUMN5TGG2M53M2N3CH34QGD3L X-Message-ID-Hash: AMDOAUKUUMN5TGG2M53M2N3CH34QGD3L X-MailFrom: alexander@dietrich.cx X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list Subject: [Galene] Thoughts on global user passwords List-Id: =?utf-8?q?Gal=C3=A8ne_videoconferencing_server_discussion_list?= Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: ------=_Part_207843_1141799579.1790430639654 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hello, 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.) 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"? Galene could use these for password authentication when a user has permissions for a particular group, but no group-specific password. There's a thread called "User management" from 2021 in the archives which discussed similar ideas, but for my use case I would ideally like to work without any additional tools or services. Kind regards, Alexander ------=_Part_207843_1141799579.1790430639654 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
Hello,
 
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.)
 
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"? Galene could use these for password authentication when a user has permissions for a particular group, but no group-specific password.
 
There's a thread called "User management" from 2021 in the archives which discussed similar ideas, but for my use case I would ideally like to work without any additional tools or services.
 
Kind regards,
Alexander
 
------=_Part_207843_1141799579.1790430639654--