Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Marty Betz <martybetz@gmail.com>
To: galene@lists.galene.org
Subject: [Galene] Admin group creation
Date: Sun, 1 Dec 2024 15:17:33 -0800	[thread overview]
Message-ID: <CAK0PyndLw7Ss55CD-M_Hun=YSePSErG9T1cULKFqCUWykN7FPg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]

Hello,
I'm learning a lot using Galene.  Thanks.  I've been experimenting with
creating groups programmatically using the REST admin interface.

In particular I tried to create a group using PUT method with JSON body and
it works fine for simple groups like:
{"op": [{"username": "elmer", "password": "1234567"}],"presenter": [{}],
"public": true}

But if I include a "users" list or a "wildcard-user" value, it fails with a
"description is not sanitized" error. For example this body fails:
{"op": [{"username": "elmer", "password": "1234567"}],"presenter": [{}],
"public": false, "users":{"john": {"password": "260530", "permissions":
"present"},"fred": {"password": "940934", "permissions": "present"}}}

I commented out the 3 lines of UpdateDescription() in description.go,
recompiled, and I was able to make this group just fine using the API.

if desc.Users != nil || desc.WildcardUser != nil || desc.AuthKeys != nil {
        return errors.New("description is not sanitised")
}

Why is this "sanitized" check existing in UpdateDescription().  It seems
relevant only for displaying group properties.

-Marty

[-- Attachment #2: Type: text/html, Size: 1644 bytes --]

             reply	other threads:[~2024-12-01 23:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-01 23:17 Marty Betz [this message]
2024-12-02 12:08 ` [Galene] " Juliusz Chroboczek
2024-12-02 17:28   ` Marty Betz
2024-12-02 18:00     ` Marty Betz
2024-12-02 19:12       ` Juliusz Chroboczek
2024-12-02 19:56         ` Marty Betz

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='CAK0PyndLw7Ss55CD-M_Hun=YSePSErG9T1cULKFqCUWykN7FPg@mail.gmail.com' \
    --to=martybetz@gmail.com \
    --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