Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: "printpagestopdf@yahoo.de" <printpagestopdf@yahoo.de>
To: "galene@lists.galene.org" <galene@lists.galene.org>
Subject: [Galene] Additional infos about the WP Plugin
Date: Wed, 5 Apr 2023 15:31:13 +0000 (UTC)	[thread overview]
Message-ID: <1533526394.8685685.1680708673432@mail.yahoo.com> (raw)
In-Reply-To: <1533526394.8685685.1680708673432.ref@mail.yahoo.com>

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

 Oh, yes access code is a bit missleading.
The groups that are created in galene server always using a JWT Token hidden from the user. 

The plugin generates links for every group and every role (presenter, ...) but this link points to the plugin host. The plugin checks the request for authentication details, that are store in the plugins database. These authentication details are configured by the administration UI of the plugin. For ervery Galene role the following auth mechanism can be configured:
- dedicated username/password from the plugins users database
- logged in in Wordpress with an allowed role- needs to know a 6 digit number that is generated randomly from the plugin- nothing at all - free access for everyone
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.
As an example a room/group can be configured following:- others: free access- presenters: 3 users from the plugins users database- op: Wordpress administratorsThats an example for an free audience, where 3 people are active speakers and the Wordpress administrator is op. Or as an alternative others have to know a 6 digit number than its a bit more limited. But all need to know the url's. In this example there are three urls (others,presenter,op) that are all pointing to the plugins host (and will be checked there). 

Hopefully that explains it a bit more? For sure one of the tasks on my list is to write some (more) documentation. 

P.S.: on Github in the subfolder docker there is a docker-compos.yml that should run a demoinstallation with some preconfigured rooms/groups

Best Regards,

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

       reply	other threads:[~2023-04-05 15:31 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 ` printpagestopdf [this message]
2023-04-10 14:10   ` [Galene] " Juliusz Chroboczek
2023-04-11 19:48     ` printpagestopdf
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=1533526394.8685685.1680708673432@mail.yahoo.com \
    --to=printpagestopdf@yahoo.de \
    --cc=galene@lists.galene.org \
    --subject='Re: [Galene] 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