You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Zenon Panoussis <or...@provocation.net> on 2020/04/20 12:36:43 UTC
Schematics
Hello
Could someone please help me understand the communication lines
between the client, the moodle plugin, the OM server and kurento?
There are so many possibilities...
Most importantly, does the client or the plugin ever talk directly
to kurento, or is kurento used exclusively by the OM server? To
phrase it differently, can kurento be firewalled so that only the
OM server has access to it?
Similarly, does a client who connects to the moodle plugin need
direct access to the OM server, or does the plugin act as a proxy
between the client and the OM server?
Cheers,
Z
Re: Schematics
Posted by Maxim Solodovnik <so...@gmail.com>.
On Mon, 20 Apr 2020 at 22:09, Zenon Panoussis <or...@provocation.net> wrote:
>
>
> > This diagram is being discussed here
> > https://openmeetings.markmail.org/thread/5n2qm57gzogwmmor
>
> Ah, thanks, this diagram answers all my questions.
>
> > KMS can be firewalled but in this case you need TURN ....
>
> If the client has to talk directly to kms, kms needs to
> be accessible on a public IP (directly or NAT:ed, but
> accessible). The background to my question was that if
> the client never talked directly with kurento, I could
> limit kms to 127.0.0.1 and close 8433 for input on the
> public address(es).
>
> Another question on a similar subject: is it possible
> (or will it be in the future) to tell OM to use and
> advertise ksm on a different IP-address and/or port?
> In other words, to run OM on one machine and ksm on
> another?
Just change this line:
https://github.com/apache/openmeetings/blob/master/openmeetings-web/src/main/webapp/WEB-INF/classes/applicationContext.xml#L148
:))
>
> Cheers,
>
> Z
>
>
--
Best regards,
Maxim
Re: Schematics
Posted by Zenon Panoussis <or...@provocation.net>.
> This diagram is being discussed here
> https://openmeetings.markmail.org/thread/5n2qm57gzogwmmor
Ah, thanks, this diagram answers all my questions.
> KMS can be firewalled but in this case you need TURN ....
If the client has to talk directly to kms, kms needs to
be accessible on a public IP (directly or NAT:ed, but
accessible). The background to my question was that if
the client never talked directly with kurento, I could
limit kms to 127.0.0.1 and close 8433 for input on the
public address(es).
Another question on a similar subject: is it possible
(or will it be in the future) to tell OM to use and
advertise ksm on a different IP-address and/or port?
In other words, to run OM on one machine and ksm on
another?
Cheers,
Z
Re: Schematics
Posted by Maxim Solodovnik <so...@gmail.com>.
Hello Z,
The Moodle plugin "talks" with OM via REST/SOAP,
As a result special link with secure hash is displayed in the iframe
Other communications were reverse engineered by Sebastian
https://cwiki.apache.org/confluence/display/OPENMEETINGS/OpenMeetings+Session+Initialisation+and+Security
This diagram is being discussed here
https://openmeetings.markmail.org/thread/5n2qm57gzogwmmor
KMS can be firewalled but in this case you need TURN ....
On Mon, 20 Apr 2020 at 19:37, Zenon Panoussis <or...@provocation.net> wrote:
>
>
> Hello
>
> Could someone please help me understand the communication lines
> between the client, the moodle plugin, the OM server and kurento?
> There are so many possibilities...
>
> Most importantly, does the client or the plugin ever talk directly
> to kurento, or is kurento used exclusively by the OM server? To
> phrase it differently, can kurento be firewalled so that only the
> OM server has access to it?
>
> Similarly, does a client who connects to the moodle plugin need
> direct access to the OM server, or does the plugin act as a proxy
> between the client and the OM server?
>
> Cheers,
>
> Z
--
Best regards,
Maxim