Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: "printpagestopdf@yahoo.de" <printpagestopdf@yahoo.de>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: "galene@lists.galene.org" <galene@lists.galene.org>
Subject: [Galene] Re: Additional infos about the WP Plugin
Date: Tue, 11 Apr 2023 19:48:45 +0000 (UTC)	[thread overview]
Message-ID: <790622636.3178670.1681242525967@mail.yahoo.com> (raw)
In-Reply-To: <87pm8b25g3.wl-jch@irif.fr>

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

Oh, that sounds great. Both enhancements would be great (but one of them would be sufficiant from the point of my plugin)! Because for some of the "administrators" it is a barrier to set up sftp access or filesharing. So if such an easier alternative way would be available to manage the server groups would enhance the usability of the plugin.
P.S.: As I read Version 0.7.0 of Galene will have exactly one of the ideas the plugin does (invitation links) as a native implementation - very nice.
Reinhold

   Am Montag, 10. April 2023 um 16:11:01 MESZ hat Juliusz Chroboczek <jch@irif.fr> Folgendes geschrieben:  
 
 > If this is checked by the plugin (e.g. for the first case it asks for a
> username/password) then the request is redirected to the configured Galene
> Server including the immediately generated JWT token.

Ok, so you're ignoring Galene's built-in authentication mechanisms, and
just using short-lived JWTs for everything.  That makes sense.

I'm wondering what I could do on the Galene side to simplify your usage.
In particular, would it be useful if you could just do an HTTPS PUT
(properly authentified) in order to update a group definition in order to
avoid sftp?  Or perhaps we could have a mode of operation where groups
automagically come into existence if they are required by a properly
authentified token?

-- Juliusz


_______________________________________________
Galene mailing list -- galene@lists.galene.org
To unsubscribe send an email to galene-leave@lists.galene.org
  

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

  reply	other threads:[~2023-04-11 19:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1533526394.8685685.1680708673432.ref@mail.yahoo.com>
2023-04-05 15:31 ` [Galene] " printpagestopdf
2023-04-10 14:10   ` [Galene] " Juliusz Chroboczek
2023-04-11 19:48     ` printpagestopdf [this message]
2023-04-11 20:34       ` Juliusz Chroboczek

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=790622636.3178670.1681242525967@mail.yahoo.com \
    --to=printpagestopdf@yahoo.de \
    --cc=galene@lists.galene.org \
    --cc=jch@irif.fr \
    --subject='[Galene] Re: Additional infos about the WP Plugin' \
    /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