Re: Aw: Re: A general Suggestion from a tester who'd like easier user experience with the software

2020-03-28 Thread info

 Hello,

This is better - personally I would color the camera and mic icons  
that are activated, so they look "ON" - (without the slash of course)  
- and to indicate the "OFF" status - it is fine - with the slash.


For example, when you hover over (or mouse over) the tiny speaker icon  
in the dragable user rectangle we see the orange-colored old-fashioned  
microphone  image pop-up - this is excellent. I would also have theat  
tiny speaker icon in the dragable user rectangle in orange to indicate  
its state is "ON" when it is on - the other two tiny icons (refresh  
and minimize) at the top of the dragable user rectangle are fine in  
grey since they are settings to change not states and users know what  
to expect with them.


This is my advice since you asked - I'm more concerned with  
fonctionality! It is working well.


One question - I have tested this extensively in Chrome adn I notice  
that if one sets the volume of teh microphone different than 50 (in  
the tiny icon in the dragable user rectangle) -each time I refres the  
user it si reset to level 50. Is this desired? Wouldn't it be better  
to keep the last user volumn settings through a "refresh" since users  
will most probably use the refresh to see or hear another user who may  
have changed the state of their camera and microphone. This is just an  
idea - it is OK as it is since it's easy to reset it.


Thansk for the good work. I'll test this on FF adn Edge and if there  
are any problems will reply again.


Ed

Quoting Maxim Solodovnik :


The demo is updated   
   Is it what you want? :)

 On Fri, 27 Mar 2020 at 20:58, Maxim Solodovnik  
 wrote:



done  will update demo as soon build will be ready
  
 Will appreciate if you can test it :)

 On Fri, 27 Mar 2020 at 20:08, Maxim Solodovnik  
 wrote:


it seems icons have to be changed ...  give me couple  
of minutes


 On Fri, 27 Mar 2020 at 20:06, Marcus Schulz  
 wrote:


I experienced the same with these buttons. I had to read the  
tooltip also before clicking.

  
 Am Freitag, den 27.03.2020, 11:31 +0100 schrieb Juan  
Antonio Moreno Carmona:


Well, for my part I agree with the suggestion provided by Ed. I  
think it is more intuitive. Maybe other users can contribute  
their opinion. El 27/3/20 a las 11:29, BBS Technik  
escribió:

I think it is a good ideal to swap it.  Regards  Ed
Gesendet: Freitag, 27. März 2020 um 11:22 Uhr   Von:  
"Maxim Solodovnik" <   solomax...@gmail.com
>   An: "Openmeetings user-list" <
user@openmeetings.apache.org   >   Betreff:  
Re: A general Suggestion from a tester who'd like easier user  
experience with the software   Well   To  
implement this I need to swap 2 lines of code   No  
problem at all if community will approve this   On  
Fri, 27 Mar 2020 at 17:19, <
i...@bureau-de-poste.net   > wrote:
Hello everyone,I love this software 5.0.0 M3  
(running on Ubuntu 18.04) with KMS 6.13A few  
questions and an important suggestion:1) I have  
been unable to install this on debian buster so that it works  
   well - can this be done? How? We'd like to be able  
to use this on buster.2) When having  
inexperienced users test our M3 version (and when testing  
   the M4 version -the same problem exists): 
The left-hand user column symbols for camera and microphone  
indicate to-doaction links, and I think they  
should indicate actual states - because thisis  
more intuitive and is what users expect.So, I  
suggest instead of showing a microphone with a red circle  
with awhite "x" in it in M3 or an orange  
old-fashion mic symbol with a slashthrough it in  
M4 to indicate that the mic is "ON" and that you have to   
  click on it to turn it "OFF", I suggest that exactly  
the opposite be shown:the actual state of the  
feature - that a slash through a symbol (perhaps in
 grey to double indicate it is off) indicates that it is  
"OFF" and a coloredon symbol or icon without a  
slash indicates that it is "ON"The same  
suggestion for the camera.95 % of user problems  
that I have encountered result from this. Users see
 something with a slash through it and they think that means  
that it is"OFF" or not activated. Why not give  
users what they expect intuitivelyrather than  
force them to behave different than usual for this app?
 I love this app/project, and this is just a friendly  
suggestion, notcriticism.best to all   
  Ed


-- WBR   Maxim aka solomax


   
--
  WBR
Maxim aka solomax


 
--
WBR
Maxim aka solomax


   
--
  WBR
M

[no subject]

2020-03-28 Thread Hassan Ayoub
I ve followed the guides "Installation OpenMeetings 5.0.0-M3 on Ubuntu
 18.04 LTS.pdf.pdf" and "Installation SSL certificates and Coturn
 for OpenMeetings 5.0.0-M3.pdf" without coturn installation as I have
a vps with real ip, however still the generated certificate
 with letsenrypt not working and it is showing the self signed certificate.
Any missed thing I have to do?



Re: Aw: Re: A general Suggestion from a tester who'd like easier user experience with the software

2020-03-28 Thread info
 One last idea - and I understand that I am just a tester / user of  
this and that it is your project in which I participate ( I also  
participate in spark, hadoop, nutch - i love apache projects), but  
since you asked, I would change the color of everythign that is "ON"  
or enabled to green and everything that is "OFF" to red - just like  
the traffic lights!  For what it's worth, and I have nothing against  
the color orange!


Best Ed

Quoting i...@bureau-de-poste.net:


Hello,

This is better - personally I would color the camera and mic icons  
that are activated, so they look "ON" - (without the slash of  
course) - and to indicate the "OFF" status - it is fine - with the  
slash.


For example, when you hover over (or mouse over) the tiny speaker  
icon in the dragable user rectangle we see the orange-colored  
old-fashioned microphone  image pop-up - this is excellent. I would  
also have theat tiny speaker icon in the dragable user rectangle in  
orange to indicate its state is "ON" when it is on - the other two  
tiny icons (refresh and minimize) at the top of the dragable user  
rectangle are fine in grey since they are settings to change not  
states and users know what to expect with them.


This is my advice since you asked - I'm more concerned with  
fonctionality! It is working well.


One question - I have tested this extensively in Chrome adn I notice  
that if one sets the volume of teh microphone different than 50 (in  
the tiny icon in the dragable user rectangle) -each time I refres  
the user it si reset to level 50. Is this desired? Wouldn't it be  
better to keep the last user volumn settings through a "refresh"  
since users will most probably use the refresh to see or hear  
another user who may have changed the state of their camera and  
microphone. This is just an idea - it is OK as it is since it's easy  
to reset it.


Thansk for the good work. I'll test this on FF adn Edge and if there  
are any problems will reply again.


Ed

Quoting Maxim Solodovnik :


The demo is updated 
Is it what you want? :)

   On Fri, 27 Mar 2020 at 20:58, Maxim Solodovnik  
 wrote:



donewill update demo as soon build will be ready
   
  Will appreciate if you can test it :)

   On Fri, 27 Mar 2020 at 20:08, Maxim Solodovnik  
 wrote:


it seems icons have to be changed ...give me  
couple of minutes


   On Fri, 27 Mar 2020 at 20:06, Marcus Schulz  
 wrote:


I experienced the same with these buttons. I had to read the  
tooltip also before clicking.

   
  Am Freitag, den 27.03.2020, 11:31 +0100 schrieb Juan  
Antonio Moreno Carmona:


Well, for my part I agree with the suggestion provided by Ed. I  
think it is more intuitive. Maybe other users can contribute  
their opinion.  El 27/3/20 a las 11:29, BBS Technik  
escribió:

I think it is a good ideal to swap it.   Regards   Ed
Gesendet: Freitag, 27. März 2020 um 11:22 UhrVon:  
"Maxim Solodovnik" An: "Openmeetings user-list" < 
user@openmeetings.apache.org>Betreff:  
Re: A general Suggestion from a tester who'd like easier user  
experience with the softwareWellTo  
implement this I need to swap 2 lines of codeNo  
problem at all if community will approve thisOn  
Fri, 27 Mar 2020 at 17:19, < 
i...@bureau-de-poste.net> wrote:
Hello everyone, I love this software 5.0.0 M3  
(running on Ubuntu 18.04) with KMS 6.13 A few  
questions and an important suggestion: 1) I have  
been unable to install this on debian buster so that it  
works well - can this be done? How? We'd like to  
be able to use this on buster. 2) When having  
inexperienced users test our M3 version (and when testing 
 the M4 version -the same problem exists):
  The left-hand user column symbols for camera and  
microphone indicate to-do action links, and I  
think they should indicate actual states - because this   
   is more intuitive and is what users expect.
  So, I suggest instead of showing a microphone with a red  
circle with a white "x" in it in M3 or an orange  
old-fashion mic symbol with a slash through it  
in M4 to indicate that the mic is "ON" and that you have to   
   click on it to turn it "OFF", I suggest that  
exactly the opposite be shown: the actual state  
of the feature - that a slash through a symbol (perhaps in
  grey to double indicate it is off) indicates that  
it is "OFF" and a colored on symbol or icon  
without a slash indicates that it is "ON" The  
same suggestion for the camera. 95 % of user  
problems that I have encountered result from this. Us

Re: Openmeetings, kurento and TURN behind NAT

2020-03-28 Thread YUP
Maxim,
Finally I managed to launch openmeetings with kurento and coturn. The
problem was in coturn server which didn't work as expected. I
installed coturn server on my private laptop (no firewall and NAT)
which listens on port 443, with the following configuration:

listening-port=443
tls-listening-port=5349
verbose
lt-cred-mech
user=kurento:kurento
realm=my_openmeetings_server_domain
log-file=/var/log/turnserver/turn.log

After that all openmeetings users can see each other cameras and hear
each other. The only problem remain, that session recording files are
wav file, not avi. Do you have a clue what is the reason is? Coul it
be a ffmpeg issue?

Best,
Yarema


On Thu, Mar 19, 2020 at 9:43 PM YUP  wrote:
>
> Maxim,
> I made a mistake, in nginx configuration section for openmetings port
> should be 5443 instead of 5080, sorry for that.
> I also forgot to mention that only tcp requests are allowed in our
> firewall, udp if prohibited, as far as know.
> Can you examine my configs and say what is wrong?
>
> Regards,
> Yarema
>
>   location /openmeetings {
> proxy_pass http://localhost:5080/openmeetings;
>
> proxy_set_header Host $host;
> proxy_http_version 1.1;
> proxy_set_header Upgrade $http_upgrade;
> proxy_set_header Connection "upgrade";
>
> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
> proxy_set_header Referer 'https://$host/openmeetings/';
> proxy_set_header X-Real-IP $remote_addr;
> }
>
> On Mon, Mar 16, 2020 at 5:01 PM YUP  wrote:
> >
> > Please take your time.
> > I gonna describe my set up briefly .
> >
> > Initial data:
> > External nat has address external_nat_ip
> > All external ports are closed except 443
> > From inside allowed only http connections to ports 80, 8080, 443 and 22
> >
> > Openmeetings runs in docker, I use docker-compose with the following
> > docker-compose.yml:
> >
> > version: '3.7'
> > services:
> >   openmeetings:
> > image: apache/openmeetings:min-5.0.0-M3
> > ports:
> >   - "5080:5080"
> >   - "5443:5443"
> > volumes:
> >   - ~/openmeetings/omdata:/opt/omdata
> >   - ~/openmeetings/logs:/opt/openmeetings/logs
> > environment:
> >   - OM_KURENTO_WS_URL=ws://kurento:/kurento
> >   - TURN_USER=kurento
> >   - TURN_PASS=kurento
> >   - TURN_URL=external_nat_ip?transport=tcp
> >   - OM_DB_TYPE=mysql
> >   - OM_DB_HOST=172.17.0.1
> >   - OM_DB_PORT=3306
> >   - OM_DB_USER=om_user
> >   - OM_DB_PASS=om_passwd
> >   - OM_DB_NAME=openmeetings
> > depends_on:
> >   - kurento
> >   - coturn
> > restart: unless-stopped
> >   kurento:
> > image: kurento/kurento-media-server
> > ports:
> >   - ":"
> > environment:
> >   - KMS_TURN_URL=kurento:kurento@external_nat_ip?transport=tcp
> > restart: unless-stopped
> >   coturn:
> > image: kurento/coturn-auth
> > ports:
> >   - "3478:3478"
> > environment:
> >   - LISTENING_PORT=3478
> >   - REALM=kurento.org
> >   - USER=kurento
> >   - PASSWORD=kurento
> > restart: unless-stopped
> >
> > I use sslh https://github.com/yrutschle/sslh to connect do different
> > services behind nat with the following configuration:
> >
> > verbose: true
> > timeout: 18000;
> > listen:
> > (
> > { host: "internal_nat_ip"; port: "443"; }
> > );
> > protocols:
> > (
> > # ssh:
> >  { name: "ssh"; service: "ssh"; host: "localhost"; port: "22";
> > probe: "builtin"; },
> > # openvpn:
> >  { name: "openvpn"; host: "localhost"; port: "1194"; probe: "builtin"; 
> > },
> > # nginx:
> >  { name: "ssl"; host: "localhost"; port: "2443"; probe: "builtin";
> > log_level: 0;},
> > # coturn:
> >  { name: "regex"; host: "localhost"; port: "3478"; regex_patterns:
> > [ "\x21\x12\xa4\x42" ]; }
> > );
> > transparent: true;
> >
> >
> > And nginx configuration (there are another services, I left only
> > openmeetings and kurento (do I really need to have kurento websocket
> > outside nat?))
> >
> >
> > server {
> > listen   2443 ssl http2;
> > listen [::]:2443 ssl http2;
> > server_name  localhost;
> >
> > autoindex on;
> > root   /srv/http/;
> > index index.php index.html index.htm;
> >
> > #ssl_certificate  /etc/httpd/conf/server.crt;
> > #ssl_certificate_key  /etc/httpd/conf/server.key;
> >
> > include conf/001-certbot.conf;
> >
> > #ssl on;
> > ssl_session_cache  builtin:1000  shared:SSL:10m;
> > ssl_protocols  TLSv1 TLSv1.1; #TLSv1.2;
> > #ssl_ciphers HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4;
> > #ssl_prefer_server_ciphers on;
> >
> >
> >  proxy_headers_hash_max_size 512;
> >  proxy_headers_hash_bucket_size 128;
> >
> > location ~ [^/]\.php(/|$) {
> > fastcgi_split_path_info  ^(.+\.php)(/.+)$;
> > fastcgi_indexindex.php;
> > fastcgi_pass unix:/run/php-fpm/php-fpm.sock;
> > inclu

Re: Aw: Re: A general Suggestion from a tester who'd like easier user experience with the software

2020-03-28 Thread Daniel Baker

Yes  this   would be  clearer.

On 28/03/2020 11:20, i...@bureau-de-poste.net wrote:


One last idea - and I understand that I am just a tester / user of 
this and that it is your project in which I participate ( I also 
participate in spark, hadoop, nutch - i love apache projects), but 
since you asked, I would change the color of everythign that is "ON" 
or enabled to green and everything that is "OFF" to red - just like 
the traffic lights!  For what it's worth, and I have nothing against 
the color orange!


Best Ed

Quoting i...@bureau-de-poste.net :


Hello,

This is better - personally I would color the camera and mic icons 
that are activated, so they look "ON" - (without the slash of course) 
- and to indicate the "OFF" status - it is fine - with the slash.


For example, when you hover over (or mouse over) the tiny speaker 
icon in the dragable user rectangle we see the orange-colored 
old-fashioned microphone  image pop-up - this is excellent. I would 
also have theat tiny speaker icon in the dragable user rectangle in 
orange to indicate its state is "ON" when it is on - the other two 
tiny icons (refresh and minimize) at the top of the dragable user 
rectangle are fine in grey since they are settings to change not 
states and users know what to expect with them.


This is my advice since you asked - I'm more concerned with 
fonctionality! It is working well.


One question - I have tested this extensively in Chrome adn I notice 
that if one sets the volume of teh microphone different than 50 (in 
the tiny icon in the dragable user rectangle) -each time I refres the 
user it si reset to level 50. Is this desired? Wouldn't it be better 
to keep the last user volumn settings through a "refresh" since users 
will most probably use the refresh to see or hear another user who 
may have changed the state of their camera and microphone. This is 
just an idea - it is OK as it is since it's easy to reset it.


Thansk for the good work. I'll test this on FF adn Edge and if there 
are any problems will reply again.


Ed

Quoting Maxim Solodovnik >:



The demo is updated
Is it what you want? :)

On Fri, 27 Mar 2020 at 20:58, Maxim Solodovnik > wrote:


done
will update demo as soon build will be ready
Will appreciate if you can test it :)

On Fri, 27 Mar 2020 at 20:08, Maxim Solodovnik
mailto:solomax...@gmail.com>> wrote:

it seems icons have to be changed ...
give me couple of minutes

On Fri, 27 Mar 2020 at 20:06, Marcus Schulz
mailto:m...@polarnetworks.de>> wrote:

I experienced the same with these buttons. I had to read
the tooltip also before clicking.
Am Freitag, den 27.03.2020, 11:31 +0100 schrieb Juan
Antonio Moreno Carmona:

Well, for my part I agree with the suggestion provided by Ed. I 
think it
is more intuitive. Maybe other users can contribute their opinion.
El 27/3/20 a las 11:29, BBS Technik escribió:

I think it is a good ideal to swap it.
Regards
Ed

Gesendet: Freitag, 27. März 2020 um 11:22 Uhr
Von: "Maxim Solodovnik" <
solomax...@gmail.com  
>
An: "Openmeetings user-list" <
user@openmeetings.apache.org  
>
Betreff: Re: A general Suggestion from a tester who'd like easier 
user experience with the software
Well
To implement this I need to swap 2 lines of code
No problem at all if community will approve this
On Fri, 27 Mar 2020 at 17:19, <
i...@bureau-de-poste.net  
> wrote:

Hello everyone,
I love this software 5.0.0 M3 (running on Ubuntu 18.04) with KMS 
6.13
A few questions and an important suggestion:
1) I have been unable to install this on debian buster so that it 
works
well - can this be done? How? We'd like to be able to use this on 
buster.
2) When having inexperienced users test our M3 version (and when 
testing
the M4 version -the same problem exists):
The left-hand user column symbols for camera and microphone 
indicate to-do
action links, and I think they should indicate actual states - 
because this
is more intuitive and is what users expect.
So, I suggest instead of showing a microphone with a red circle 
with a
white "x" in it in M3 or an orange old-fashion mic symbol with a 
slash
through it in M4 to indicate that the mic is "ON" and that you have 
to
click on it to turn it "OFF", I suggest that exactly the opposite 
be shown:
the actual state of the feature - that a slash

Aw: Re: Re: A general Suggestion from a tester who'd like easier user experience with the software

2020-03-28 Thread BBS Technik
Hi,

 


I would also have a few small suggestions for the design.

 

- The symbol and the text for leaving the room should be highlighted (in color?).

 

- The character > should be inverted in the chat bar. That would correspond to the same logic as with the new camera and microphone symbol.

 

- The color selection dialog should open near the tools properties window.
At the moment the color selection appears in the top left corner and makes long movements with the mouse.

 

- The icons in the toolbar could be a little bit smaler. They almost touch the chat bar. see attached screenshot.

 

But this should not slow down the release process.   ;-)

 

Regards Ed


 
 

Gesendet: Samstag, 28. März 2020 um 14:44 Uhr
Von: "Daniel Baker" 
An: user@openmeetings.apache.org, i...@bureau-de-poste.net
Betreff: Re: Aw: Re: A general Suggestion from a tester who'd like easier user experience with the software


Yes  this   would be  clearer.

On 28/03/2020 11:20, i...@bureau-de-poste.net wrote:

 





One last idea - and I understand that I am just a tester / user of this and that it is your project in which I participate ( I also participate in spark, hadoop, nutch - i love apache projects), but since you asked, I would change the color of everythign that is "ON" or enabled to green and everything that is "OFF" to red - just like the traffic lights!  For what it's worth, and I have nothing against the color orange!

Best Ed

Quoting i...@bureau-de-poste.net:


Hello,

This is better - personally I would color the camera and mic icons that are activated, so they look "ON" - (without the slash of course) - and to indicate the "OFF" status - it is fine - with the slash.

For example, when you hover over (or mouse over) the tiny speaker icon in the dragable user rectangle we see the orange-colored old-fashioned microphone  image pop-up - this is excellent. I would also have theat tiny speaker icon in the dragable user rectangle in orange to indicate its state is "ON" when it is on - the other two tiny icons (refresh and minimize) at the top of the dragable user rectangle are fine in grey since they are settings to change not states and users know what to expect with them.

This is my advice since you asked - I'm more concerned with fonctionality! It is working well.

One question - I have tested this extensively in Chrome adn I notice that if one sets the volume of teh microphone different than 50 (in the tiny icon in the dragable user rectangle) -each time I refres the user it si reset to level 50. Is this desired? Wouldn't it be better to keep the last user volumn settings through a "refresh" since users will most probably use the refresh to see or hear another user who may have changed the state of their camera and microphone. This is just an idea - it is OK as it is since it's easy to reset it.

Thansk for the good work. I'll test this on FF adn Edge and if there are any problems will reply again.

Ed

Quoting Maxim Solodovnik :


The demo is updated
 

Is it what you want? :)

 


On Fri, 27 Mar 2020 at 20:58, Maxim Solodovnik  wrote:


done
will update demo as soon build will be ready

 

Will appreciate if you can test it :)

 


On Fri, 27 Mar 2020 at 20:08, Maxim Solodovnik  wrote:


it seems icons have to be changed ...
give me couple of minutes

 


On Fri, 27 Mar 2020 at 20:06, Marcus Schulz  wrote:



I experienced the same with these buttons. I had to read the tooltip also before clicking.

 

Am Freitag, den 27.03.2020, 11:31 +0100 schrieb Juan Antonio Moreno Carmona:


Well, for my part I agree with the suggestion provided by Ed. I think it 

is more intuitive. Maybe other users can contribute their opinion.

El 27/3/20 a las 11:29, BBS Technik escribió:


I think it is a good ideal to swap it.

Regards

Ed


Gesendet: Freitag, 27. März 2020 um 11:22 Uhr

Von: "Maxim Solodovnik" <

solomax...@gmail.com

>

An: "Openmeetings user-list" <

user@openmeetings.apache.org

>

Betreff: Re: A general Suggestion from a tester who'd like easier user experience with the software

Well

To implement this I need to swap 2 lines of code

No problem at all if community will approve this

On Fri, 27 Mar 2020 at 17:19, <

i...@bureau-de-poste.net

> wrote:


Hello everyone,

I love this software 5.0.0 M3 (running on Ubuntu 18.04) with KMS 6.13

A few questions and an important suggestion:

1) I have been unable to install this on debian buster so that it works

well - can this be done? How? We'd like to be able to use this on buster.

2) When having inexperienced users test our M3 version (and when testing

the M4 version -the same problem exists):

The left-hand user column symbols for camera and microphone indicate to-do

action links, and I think they should indicate actual states - because this

is more intuitive and is what users expect.

So, I suggest instead of showing a microphone with a red circle with a

white "x" in 

google oauth2 error

2020-03-28 Thread Ruben ALLITTEH

Hello !

I’m trying to configure oauth2 google for openmeetings 5.0.0-M2

I have activated ID client oauth2 with client ID and secret.

However authentication don’t working, once you are authenticated with google 
oauth2, openmeetings redirect to the sign-in page



My current configuration

Name : Google



Client_id : ooo



Client_secret : 



Redirect_URI : https://media.trstech.net:5443/openmeetings/oauth/2



Request Key URL : 
https://accounts.google.com/o/oauth2/auth?redirect_uri={$redirect_uri}&response_type=code&client_id={$client_id}&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile



Request token URL : 
https://oauth2.googleapis.com/tokeninfo?id_token={$code}&client_id={$client_id}&client_secret={$client_secret}&redirect_uri={$redirect_uri}&grant_type=authorization_code



Request token attributes : 
code={$code}&client_id={$client_id}&client_secret={$client_secret}&redirect_uri={$redirect_uri}&grant_type=authorization_code



Request info URL : 
https://www.googleapis.com/auth/userinfo?access_token={$access_token}



Have anyone running google oauth2 with OM 5.0.0-M2 ?






ldap config

2020-03-28 Thread Orm Finnendahl
Hi,

 we successfully installed openmeetings on our server but have some
issues regarding integration with our ldap authentication server.

LDAP:

1. The location of the file om_ldap.cfg is unclear:

   The example file is located in

   /opt/open503/webapps/openmeetings/data/conf/

   but the online documentation states it should be in

   /opt/open503/webapps/openmeetings/conf/

   What is the right location?

2. The config file says:

   #ConfigKey 'ldap_config_path' must be set in DataBase Configuration
   # of OM and point to this file

   I can't find that entry anywhere. Can someone help?

3. What has to be filled in the ldap_admin_dn? We tried the following
   which uses a new created user in our ldap (without heightened
   privileges):

   ldap_admin_dn=cn=openmeetings,dc=selma,dc=hfmdk-frankfurt,dc=de

   ldap_passwd=

4. What has to be put into the Web Form at Administration/LDAP? I made
   an entry and entered "openmeetings" as Name, enabled it and called
   the config file name "om_ldap.cfg", saved it and hit reload. I can
   still see no users when trying to invite participants or log in
   with any of our ldap users.

5. Are there any logs to check in order to determine what goes wrong?


virtual host config

2020-03-28 Thread Orm Finnendahl
Hi,

 we successfully installed openmeetings on our server but have some
issues regarding virtual host settings in the apache config. Are there
any exampe files?

Using our vpn and accessing it using the vpn local ip works like this:

https://10.8.0.11:5443/openmeetings/

Below is our entry in the apache config to make it accessible using
https:///openmeetings

We get "The requested URL was not found on this server"

Any help is appreciated.

--
Orm

VirtualHost *:443>
ServerName 
SSLEngine On
SSLCertificateFile/etc/apache2/certs/www.mydomain.com.pem
SSLCertificateKeyFile /etc/apache2/certs/www.mydomain.com.key

SSLCACertificatePath /etc/ssl/certs/
 

RewriteEngine Off

ProxyRequests Off
SetEnv proxy-nokeepalive 1
ProxyPreserveHost On
ProxyPassInterpolateEnv On
ProxyPass /openmeetings http://127.0.0.1:5080/openmeetings interpolate


Order allow,deny
Allow from all


http://127.0.0.1:5080>
RequestHeader set "x-webobjects-server-port" "443"
RequestHeader set "x-webobjects-server-name" "mydomain.com:8800"
RequestHeader set "x-webobjects-server-url" 
"https://mydomain.com:8800";
RequestHeader set "x-webobjects-server-protocol" "HTTP/1.0"
RequestHeader set "x-webobjects-remote-host" "127.0.0.1"
AddDefaultCharset UTF-8


ErrorLog /var/log/apache2/om-error.log
CustomLog /var/log/apache2/om-access.log combined




virtual host config

2020-03-28 Thread Orm Finnendahl
Hi,

 we successfully installed openmeetings on our server but have issues
regarding RTC broadcasting. Logging in and testing the camera and
sound works as expected. Changing into a room and allowing
camera/microphone access results in the following error:

Failed to start broadcast: Factory 'WebRtcEndpoint' not found
(Code:40108, Type:null, Data: {"type":"MEDIA_OBJECT_NOT_AVAILABLE"})

We couldn't find any documentation on that. How can we fix it?

--
Orm


Some one have letsencrypt working rigt wit OpenMeetings-5 ?

2020-03-28 Thread Alvaro
Hello All,

Some one have letsencrypt working rigt wit OpenMeetings-5 ?

I have rights letsencrypt certificates, these are tested with
apache web server ssl, at the same machine that OM, and the
browsers say "Secure connection".

I have so:








...but with this configuration the browsers say "not secure
connection".

'Ve try in different ways but don't get it.

If somebody know the right way, please tell it.

Thanks

Alvaro




---




Re: Some one have letsencrypt working rigt wit OpenMeetings-5 ?

2020-03-28 Thread Alvaro

Ok, it is solved.
I will add the instructions in the tutorial:
Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M3.pdf
...and in two days will upload it again.
Regards
Alvaro

.


In two or three da
El sáb, 28-03-2020 a las 18:04 +0100, Alvaro escribió:
> Hello All,
> 
> Some one have letsencrypt working rigt wit OpenMeetings-5 ?
> 
> I have rights letsencrypt certificates, these are tested with
> apache web server ssl, at the same machine that OM, and the
> browsers say "Secure connection".
> 
> I have so:
> 
>  protocol="org.apache.coyote.http11.Http11AprProtocol"
> maxThreads="150" SSLEnabled="true" >
> 
> 
>  certificateKeyFile="/etc/letsencrypt/live/your_true_domain/privkey.pe
> m"
> certificateFile="/etc/letsencrypt/live/your_true_domain/cert.pem"
> certificateChainFile="/etc/letsencrypt/live/your_true_domain/fullchai
> n.pem"
> type="RSA" />
> 
> 
> 
> ...but with this configuration the browsers say "not secure
> connection".
> 
> 'Ve try in different ways but don't get it.
> 
> If somebody know the right way, please tell it.
> 
> Thanks
> 
> Alvaro
> 
> 
> 
> 
> ---
> 
> 
> 

Re: New tutorial installation SSL certificates and Coturn for OpenMeetings 5.0.0-M3

2020-03-28 Thread Alvaro


...in two days i will upload the same tutorial completing
the instructions for real letsencrypt "Connection secure".


..

El vie, 27-03-2020 a las 21:19 +0100, stefanx escribió:
> I followed this instruction, the letsencrpyt installation is ok, by
> now I get "HTTP Status 404 – Not Found"
> 
> Any ideas ?
> 
> Am 27.03.20 um 17:20 schrieb Alvaro:
> > 
> > Hello,
> > 
> > It is at your disposal a new tutorial called:
> > 
> > 
> > Installation SSL certificates and Coturn for OpenMeetings 5.0.0-
> > M3.pdf
> > 
> > 
> > It is tested with an OpenMeetings 5 server installed on a pc
> > at home, after NAT router; and each in the room saw and heard the
> > others
> > cameras and your own correctly.
> > Also in the tests done, we have uploaded files, recorded video
> > and shared desktop without any error.
> > 
> > You can download the tutorial directly from here:
> > 
> > https://cwiki.apache.org/confluence/download/attachments/27838216/I
> > nstallation%20SSL%20certificates%20and%20Coturn%20for%20OpenMeeting
> > s%205.0.0-M3.pdf
> > 
> > ...or find it here:
> > 
> > https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+
> > for+installing+OpenMeetings+and+Tools
> > 
> > Best regards
> > 
> > Alvaro
> > 
> > 
> > 
> > -
> 
> 


Re: New tutorial installation SSL certificates and Coturn for OpenMeetings 5.0.0-M3

2020-03-28 Thread stefanx



https://:5443/openmeetings/ : HTTP Status 404 – Not Found

Perhaps "application.base.url" in the Openmeetings configuration now is wrong ?

But I now cannot change application.base.url, except with mysql db modification 
?


Am 28.03.20 um 04:12 schrieb Maxim Solodovnik:
> 404 at what URL?
>
> On Sat, 28 Mar 2020 at 03:19, stefanx  > wrote:
>
> I followed this instruction, the letsencrpyt installation is ok, by now I 
> get "HTTP Status 404 – Not Found"
>
> Any ideas ?
>
> Am 27.03.20 um 17:20 schrieb Alvaro:
> >
> > Hello,
> >
> > It is at your disposal a new tutorial called:
> >
> >
> > Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M3.pdf
> >
> >
> > It is tested with an OpenMeetings 5 server installed on a pc
> > at home, after NAT router; and each in the room saw and heard the others
> > cameras and your own correctly.
> > Also in the tests done, we have uploaded files, recorded video
> > and shared desktop without any error.
> >
> > You can download the tutorial directly from here:
> >
> > 
> https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20SSL%20certificates%20and%20Coturn%20for%20OpenMeetings%205.0.0-M3.pdf
> >
> > ...or find it here:
> >
> > 
> https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools
> >
> > Best regards
> >
> > Alvaro
> >
> >
> >
> > -
>
>
>
> -- 
> WBR
> Maxim aka solomax



Re: virtual host config

2020-03-28 Thread Marcus Schulz

Hi Orm,


here is a working  example for Apache webserver. You need the WebSockets 
to be rewritten.
Expecteing the tomcat of your openmeeting installation running in port 
5080 @ localhost.
If your apache is configured for ssl, be sure to add scheme and security 
to your tomcat connector:


 


Apache fragment for vhost:
###  OpenMeetings    ###
## Custom fragment
RewriteEngine On
RewriteCond %{REQUEST_URI} ^/$
RewriteRule (.*) /openmeetings/ [R=301]
RewriteCond %{HTTP:Connection} Upgrade [NC]
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteRule /(.*) ws://localhost:5080/$1 [P,L]
RedirectMatch ^/$ https://yourservername.de/openmeetings
ProxyPreserveHost On


  Require all granted
  ProxyPass http://localhost:5080/openmeetings
  ProxyPassReverse http://localhost:5080/openmeetings
  RewriteEngine On
  RewriteRule ^/(.*) http://localhost:5080/$1 [P]


  Require all granted
  ProxyPass http://localhost:5080/open
  ProxyPassReverse http://localhost:5080/open


  Require all granted
  ProxyPass http://localhost:5080/send
  ProxyPassReverse http://localhost:5080/send


  Require all granted
  ProxyPass http://localhost:5080/idle
  ProxyPassReverse http://localhost:5080/idle


  Require all granted
  ProxyPass http://localhost:5080/close
  ProxyPassReverse http://localhost:5080/close


Hope, that helps.


Am 28.03.2020 um 17:32 schrieb Orm Finnendahl:

Hi,

  we successfully installed openmeetings on our server but have some
issues regarding virtual host settings in the apache config. Are there
any exampe files?

Using our vpn and accessing it using the vpn local ip works like this:

https://10.8.0.11:5443/openmeetings/

Below is our entry in the apache config to make it accessible using
https:///openmeetings

We get "The requested URL was not found on this server"

Any help is appreciated.

--
Orm

VirtualHost *:443>
 ServerName 
 SSLEngine On
 SSLCertificateFile/etc/apache2/certs/www.mydomain.com.pem
 SSLCertificateKeyFile /etc/apache2/certs/www.mydomain.com.key

 SSLCACertificatePath /etc/ssl/certs/
  


 RewriteEngine Off

 ProxyRequests Off
 SetEnv proxy-nokeepalive 1
 ProxyPreserveHost On
 ProxyPassInterpolateEnv On
 ProxyPass /openmeetings http://127.0.0.1:5080/openmeetings interpolate

 
 Order allow,deny
 Allow from all
 

 http://127.0.0.1:5080>
 RequestHeader set "x-webobjects-server-port" "443"
 RequestHeader set "x-webobjects-server-name" 
"mydomain.com:8800"
 RequestHeader set "x-webobjects-server-url" 
"https://mydomain.com:8800";
 RequestHeader set "x-webobjects-server-protocol" "HTTP/1.0"
 RequestHeader set "x-webobjects-remote-host" "127.0.0.1"
 AddDefaultCharset UTF-8
 

 ErrorLog /var/log/apache2/om-error.log
 CustomLog /var/log/apache2/om-access.log combined






Re: Some one have letsencrypt working rigt wit OpenMeetings-5 ?

2020-03-28 Thread Marcus Schulz

Hello Alvaro,

Yes, me.

I configured SSL Apache straigt forward and then use the PLAIN connector 
of the tomcat. You cannot proxy with an SSL virtual host to another SSL 
connector as far as I know.



use that connector for tomcat:

 

Here is my apache vhost config:


    ServerAdmin mar...@mydomain.de
    ServerName meeting.mydomain.de

    DocumentRoot /var/www-meeting
    TraceEnable Off

    ErrorDocument 404 /index.php
    ErrorLog /var/log/apache2/meeting-error.log

    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn

    CustomLog /var/log/apache2/meeting-access.log combined
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/meeting.mydomain.de-0004/cert.pem
SSLCertificateKeyFile 
/etc/letsencrypt/live/meeting.mydomain.de-0004/privkey.pem
SSLCertificateChainFile 
/etc/letsencrypt/live/meeting.mydomain.de-0004/chain.pem


###  OpenMeetings    ###
## Custom fragment
RewriteEngine On
RewriteCond %{REQUEST_URI} ^/$
RewriteRule (.*) /openmeetings/ [R=301]
RewriteCond %{HTTP:Connection} Upgrade [NC]
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteRule /(.*) ws://localhost:5080/$1 [P,L]
RedirectMatch ^/$ https://yourserver.de/openmeetings
ProxyPreserveHost On


  Require all granted
  ProxyPass http://localhost:5080/openmeetings
  ProxyPassReverse http://localhost:5080/openmeetings
  RewriteEngine On
  RewriteRule ^/(.*) http://localhost:5080/$1 [P]


  Require all granted
  ProxyPass http://localhost:5080/open
  ProxyPassReverse http://localhost:5080/open


  Require all granted
  ProxyPass http://localhost:5080/send
  ProxyPassReverse http://localhost:5080/send


  Require all granted
  ProxyPass http://localhost:5080/idle
  ProxyPassReverse http://localhost:5080/idle


  Require all granted
  ProxyPass http://localhost:5080/close
  ProxyPassReverse http://localhost:5080/close





Hope that helps



AJP13 could work also, but I did not test.

Am 28.03.2020 um 18:04 schrieb Alvaro:

Hello All,

Some one have letsencrypt working rigt wit OpenMeetings-5 ?

I have rights letsencrypt certificates, these are tested with
apache web server ssl, at the same machine that OM, and the
browsers say "Secure connection".

I have so:

protocol="org.apache.coyote.http11.Http11AprProtocol"

maxThreads="150" SSLEnabled="true" >


certificateKeyFile="/etc/letsencrypt/live/your_true_domain/privkey.pem"

certificateFile="/etc/letsencrypt/live/your_true_domain/cert.pem"
certificateChainFile="/etc/letsencrypt/live/your_true_domain/fullchain.pem"
type="RSA" />



...but with this configuration the browsers say "not secure connection".

'Ve try in different ways but don't get it.

If somebody know the right way, please tell it.

Thanks

Alvaro




---







Firefox 74 on windows - hanging

2020-03-28 Thread Carl Brewer



Hey,

Latest build 5.0.0-m4- 3072 I think, Ubuntu server.  Edge and Chrome log 
in fine, but FF 74 on Win 10-64 seems to sit with the three spinning 
balls for ever and not get past the login screen.


The PC in question has no speakers, camera or microphone.

any clues? Just use Chrome? :)

Carl




Re:

2020-03-28 Thread Maxim Solodovnik
Have you restarted OM after all changes were made?

(turn server still might be required ...)

On Sat, 28 Mar 2020 at 18:03, Hassan Ayoub 
wrote:

> I ve followed the guides "Installation OpenMeetings 5.0.0-M3 on Ubuntu
>  18.04 LTS.pdf.pdf" and "Installation SSL certificates and Coturn
>  for OpenMeetings 5.0.0-M3.pdf" without coturn installation as I have
> a vps with real ip, however still the generated certificate
>  with letsenrypt not working and it is showing the self signed certificate.
> Any missed thing I have to do?
>
>

-- 
WBR
Maxim aka solomax


Re: Openmeetings, kurento and TURN behind NAT

2020-03-28 Thread Maxim Solodovnik
Hello Yarema,

sorry had no time and HW so far to experiment

it would be more reasonable to have
listening-port=80
in this case (due to it insecure)

>> The only problem remain, that session recording files are
>> wav file, not avi. Do you have a clue what is the reason is? Coul it
>> be a ffmpeg issue?

During session recording intermediate files are *.webm
Later *.wav is extracted/generated to create *.mp4 (not avi)

Could you check if you have *.webm in `data` folder?

On Sat, 28 Mar 2020 at 18:43, YUP  wrote:

> Maxim,
> Finally I managed to launch openmeetings with kurento and coturn. The
> problem was in coturn server which didn't work as expected. I
> installed coturn server on my private laptop (no firewall and NAT)
> which listens on port 443, with the following configuration:
>
> listening-port=443
> tls-listening-port=5349
> verbose
> lt-cred-mech
> user=kurento:kurento
> realm=my_openmeetings_server_domain
> log-file=/var/log/turnserver/turn.log
>
> After that all openmeetings users can see each other cameras and hear
> each other. The only problem remain, that session recording files are
> wav file, not avi. Do you have a clue what is the reason is? Coul it
> be a ffmpeg issue?
>
> Best,
> Yarema
>
>
> On Thu, Mar 19, 2020 at 9:43 PM YUP  wrote:
> >
> > Maxim,
> > I made a mistake, in nginx configuration section for openmetings port
> > should be 5443 instead of 5080, sorry for that.
> > I also forgot to mention that only tcp requests are allowed in our
> > firewall, udp if prohibited, as far as know.
> > Can you examine my configs and say what is wrong?
> >
> > Regards,
> > Yarema
> >
> >   location /openmeetings {
> > proxy_pass http://localhost:5080/openmeetings;
> >
> > proxy_set_header Host $host;
> > proxy_http_version 1.1;
> > proxy_set_header Upgrade $http_upgrade;
> > proxy_set_header Connection "upgrade";
> >
> > proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
> > proxy_set_header Referer 'https://$host/openmeetings/';
> > proxy_set_header X-Real-IP $remote_addr;
> > }
> >
> > On Mon, Mar 16, 2020 at 5:01 PM YUP  wrote:
> > >
> > > Please take your time.
> > > I gonna describe my set up briefly .
> > >
> > > Initial data:
> > > External nat has address external_nat_ip
> > > All external ports are closed except 443
> > > From inside allowed only http connections to ports 80, 8080, 443 and 22
> > >
> > > Openmeetings runs in docker, I use docker-compose with the following
> > > docker-compose.yml:
> > >
> > > version: '3.7'
> > > services:
> > >   openmeetings:
> > > image: apache/openmeetings:min-5.0.0-M3
> > > ports:
> > >   - "5080:5080"
> > >   - "5443:5443"
> > > volumes:
> > >   - ~/openmeetings/omdata:/opt/omdata
> > >   - ~/openmeetings/logs:/opt/openmeetings/logs
> > > environment:
> > >   - OM_KURENTO_WS_URL=ws://kurento:/kurento
> > >   - TURN_USER=kurento
> > >   - TURN_PASS=kurento
> > >   - TURN_URL=external_nat_ip?transport=tcp
> > >   - OM_DB_TYPE=mysql
> > >   - OM_DB_HOST=172.17.0.1
> > >   - OM_DB_PORT=3306
> > >   - OM_DB_USER=om_user
> > >   - OM_DB_PASS=om_passwd
> > >   - OM_DB_NAME=openmeetings
> > > depends_on:
> > >   - kurento
> > >   - coturn
> > > restart: unless-stopped
> > >   kurento:
> > > image: kurento/kurento-media-server
> > > ports:
> > >   - ":"
> > > environment:
> > >   - KMS_TURN_URL=kurento:kurento@external_nat_ip?transport=tcp
> > > restart: unless-stopped
> > >   coturn:
> > > image: kurento/coturn-auth
> > > ports:
> > >   - "3478:3478"
> > > environment:
> > >   - LISTENING_PORT=3478
> > >   - REALM=kurento.org
> > >   - USER=kurento
> > >   - PASSWORD=kurento
> > > restart: unless-stopped
> > >
> > > I use sslh https://github.com/yrutschle/sslh to connect do different
> > > services behind nat with the following configuration:
> > >
> > > verbose: true
> > > timeout: 18000;
> > > listen:
> > > (
> > > { host: "internal_nat_ip"; port: "443"; }
> > > );
> > > protocols:
> > > (
> > > # ssh:
> > >  { name: "ssh"; service: "ssh"; host: "localhost"; port: "22";
> > > probe: "builtin"; },
> > > # openvpn:
> > >  { name: "openvpn"; host: "localhost"; port: "1194"; probe:
> "builtin"; },
> > > # nginx:
> > >  { name: "ssl"; host: "localhost"; port: "2443"; probe: "builtin";
> > > log_level: 0;},
> > > # coturn:
> > >  { name: "regex"; host: "localhost"; port: "3478"; regex_patterns:
> > > [ "\x21\x12\xa4\x42" ]; }
> > > );
> > > transparent: true;
> > >
> > >
> > > And nginx configuration (there are another services, I left only
> > > openmeetings and kurento (do I really need to have kurento websocket
> > > outside nat?))
> > >
> > >
> > > server {
> > > listen   2443 ssl http2;
> > > listen [::]:2443 ssl http2;
> > > server_name  localhost;
> > >
> > > autoindex o

Re: google oauth2 error

2020-03-28 Thread Maxim Solodovnik
Hello,

Google OAuth works on demo https://om.alteametasoft.com:8443/next/
Can you check openmeetings.log?

On Sat, 28 Mar 2020 at 21:57, Ruben ALLITTEH  wrote:

>
> Hello !
>
> I’m trying to configure oauth2 google for openmeetings 5.0.0-M2
>
> I have activated ID client oauth2 with client ID and secret.
>
> However authentication don’t working, once you are authenticated with
> google oauth2, openmeetings redirect to the sign-in page
>
>
>
> My current configuration
>
> Name : Google
>
>
>
> Client_id : ooo
>
>
>
> Client_secret : 
>
>
>
> Redirect_URI : https://media.trstech.net:5443/openmeetings/oauth/2
>
>
>
> Request Key URL :
> https://accounts.google.com/o/oauth2/auth?redirect_uri={$redirect_uri}&response_type=code&client_id={$client_id}&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile
> 
>
>
>
> Request token URL :
> https://oauth2.googleapis.com/tokeninfo?id_token={$code}&client_id={$client_id}&client_secret={$client_secret}&redirect_uri={$redirect_uri}&grant_type=authorization_code
>
>
>
> Request token attributes :
> code={$code}&client_id={$client_id}&client_secret={$client_secret}&redirect_uri={$redirect_uri}&grant_type=authorization_code
>
>
>
> Request info URL :
> https://www.googleapis.com/auth/userinfo?access_token={$access_token}
>
>
>
> Have anyone running google oauth2 with OM 5.0.0-M2 ?
>
>
>
>
>

-- 
WBR
Maxim aka solomax


Re: ldap config

2020-03-28 Thread Maxim Solodovnik
Hello,

I assume you are using M3


On Sat, 28 Mar 2020 at 23:22, Orm Finnendahl <
orm.finnend...@selma.hfmdk-frankfurt.de> wrote:

> Hi,
>
>  we successfully installed openmeetings on our server but have some
> issues regarding integration with our ldap authentication server.
>
> LDAP:
>
> 1. The location of the file om_ldap.cfg is unclear:
>
>The example file is located in
>
>/opt/open503/webapps/openmeetings/data/conf/
>
>but the online documentation states it should be in
>
>/opt/open503/webapps/openmeetings/conf/
>
>What is the right location?
>

***/data/conf is correct
I'll try to update https://openmeetings.apache.org/LdapAndADS.html
please fill free to file JIRA:
https://openmeetings.apache.org/LdapAndADS.html


>
> 2. The config file says:
>
>#ConfigKey 'ldap_config_path' must be set in DataBase Configuration
># of OM and point to this file
>
>I can't find that entry anywhere. Can someone help?
>

This is really old comment
I believe it means:
you have to set the name of the file (with extention) at
Admin->Ldap->Config file name
and save :)


>
> 3. What has to be filled in the ldap_admin_dn? We tried the following
>which uses a new created user in our ldap (without heightened
>privileges):
>
>ldap_admin_dn=cn=openmeetings,dc=selma,dc=hfmdk-frankfurt,dc=de
>
>ldap_passwd=
>

admin_dn is used to perform user search (ldap_auth_type=SEARCHANDBIND)

(according to my tests it works much stable than SIMPLEBIND)


>
> 4. What has to be put into the Web Form at Administration/LDAP? I made
>an entry and entered "openmeetings" as Name, enabled it and called
>the config file name "om_ldap.cfg", saved it and hit reload. I can
>still see no users when trying to invite participants or log in
>with any of our ldap users.
>

Well,
I'm afraid it works slightly different

ATM LDAP is used to unify login only (like OAuth: if you will log-in with
Google account it will not let you to search google users)
You can use command line admin to import LDAP user into OM DB, this way
search will work

This can be improved
But I believe some questions should be answered first:
1) is the performance will be enough
2) how LDAP and DB results shoul be combined



>
> 5. Are there any logs to check in order to determine what goes wrong?
>

Everything is logged into openmeetings.log :)

-- 
WBR
Maxim aka solomax


Re: [HELP NEEDED] 5.0.0 release

2020-03-28 Thread Peter Dähn

Hi Maxim,

there are two issues left. Maybe my installation. But it is the same 
behaviour on test and on production.


1. I have upload problems. Not specific by time ore size. Same file 
might work or not.


I get an error in the logs, but no recommended solution helped.

/WARN  03-28 00:57:13.083 o.a.w.m.h.f.Form:1469 [io-5080-exec-23] - 
Upload failed: Processing of multipart/form-data request failed. 
java.io.IOException: Stream reset//
//org.apache.commons.fileupload.FileUploadBase$IOFileUploadException: 
Processing of multipart/form-data request failed. java.io.IOException: 
Stream reset//
//    at 
org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:350)//
//    at 
org.apache.wicket.protocol.http.servlet.MultipartServletWebRequestImpl.parseFileParts(MultipartServletWebRequestImpl.java:196)//
//    at 
org.apache.wicket.markup.html.form.Form.handleMultiPart(Form.java:1419)//
//    at 
org.apache.openmeetings.web.room.sidebar.UploadDialog$1.handleMultiPart(UploadDialog.java:83)//
//    at 
org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:771)//
//    at 
com.googlecode.wicket.jquery.ui.widget.dialog.AbstractFormDialog.internalOnClick(AbstractFormDialog.java:215)//
//    at 
com.googlecode.wicket.jquery.ui.widget.dialog.AbstractDialog$2.onClick(AbstractDialog.java:440)//
//    at 
com.googlecode.wicket.jquery.ui.widget.dialog.DialogBehavior.onAjax(DialogBehavior.java:188)//
//    at 
com.googlecode.wicket.jquery.core.ajax.JQueryAjaxBehavior.respond(JQueryAjaxBehavior.java:174)//
//    at 
org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:597)//
//    at 
org.apache.wicket.core.request.handler.ListenerRequestHandler.internalInvoke(ListenerRequestHandler.java:306)//
//    at 
org.apache.wicket.core.request.handler.ListenerRequestHandler.invoke(ListenerRequestHandler.java:280)//
//    at 
org.apache.wicket.core.request.handler.ListenerRequestHandler.invokeListener(ListenerRequestHandler.java:222)//
//    at 
org.apache.wicket.core.request.handler.ListenerRequestHandler.respond(ListenerRequestHandler.java:208)//
//    at 
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:917)//
//    at 
org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:63)//
//    at 
org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283)//
//    at 
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:254)//
//    at 
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:222)//
//    at 
org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:71)//
//    at 
org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:207)//
//    at 
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:300)//
//    at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)//
//    at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)//
//    at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202)//
//    at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)//
//    at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:666)//
//    at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)//
//    at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)//
//    at 
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:688)//
//    at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)//
//    at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)//
//    at 
org.apache.coyote.http2.StreamProcessor.service(StreamProcessor.java:365)//
//    at 
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)//
//    at 
org.apache.coyote.http2.StreamProcessor.process(StreamProcessor.java:72)//
//    at 
org.apache.coyote.http2.StreamRunnable.run(StreamRunnable.java:35)//
//    at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)//
//    at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)//
//    at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)//

//    at java.base/java.lang.Thread.run(Thread.java:834)//
//Caused by: org.apache.catalina.connector.ClientAbortException: 
java.io.IOException: Stream reset//
//    at 
org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.java:340)//
//    at 
org.apache.catalina.connector.InputBuffer.checkByteBufferEof(InputBuffer.java:632)//
//    at 
org.apache.catalina.connector.InputBuffer.read(InputBuffer.java:362)//
//    at 
org.apache.catalina.connec

Re: ldap config

2020-03-28 Thread Maxim Solodovnik
Documentation is updated (will be published with next release)

On Sun, 29 Mar 2020 at 07:41, Maxim Solodovnik  wrote:

> Hello,
>
> I assume you are using M3
>
>
> On Sat, 28 Mar 2020 at 23:22, Orm Finnendahl <
> orm.finnend...@selma.hfmdk-frankfurt.de> wrote:
>
>> Hi,
>>
>>  we successfully installed openmeetings on our server but have some
>> issues regarding integration with our ldap authentication server.
>>
>> LDAP:
>>
>> 1. The location of the file om_ldap.cfg is unclear:
>>
>>The example file is located in
>>
>>/opt/open503/webapps/openmeetings/data/conf/
>>
>>but the online documentation states it should be in
>>
>>/opt/open503/webapps/openmeetings/conf/
>>
>>What is the right location?
>>
>
> ***/data/conf is correct
> I'll try to update https://openmeetings.apache.org/LdapAndADS.html
> please fill free to file JIRA:
> https://openmeetings.apache.org/LdapAndADS.html
>
>
>>
>> 2. The config file says:
>>
>>#ConfigKey 'ldap_config_path' must be set in DataBase Configuration
>># of OM and point to this file
>>
>>I can't find that entry anywhere. Can someone help?
>>
>
> This is really old comment
> I believe it means:
> you have to set the name of the file (with extention) at
> Admin->Ldap->Config file name
> and save :)
>
>
>>
>> 3. What has to be filled in the ldap_admin_dn? We tried the following
>>which uses a new created user in our ldap (without heightened
>>privileges):
>>
>>ldap_admin_dn=cn=openmeetings,dc=selma,dc=hfmdk-frankfurt,dc=de
>>
>>ldap_passwd=
>>
>
> admin_dn is used to perform user search (ldap_auth_type=SEARCHANDBIND)
>
> (according to my tests it works much stable than SIMPLEBIND)
>
>
>>
>> 4. What has to be put into the Web Form at Administration/LDAP? I made
>>an entry and entered "openmeetings" as Name, enabled it and called
>>the config file name "om_ldap.cfg", saved it and hit reload. I can
>>still see no users when trying to invite participants or log in
>>with any of our ldap users.
>>
>
> Well,
> I'm afraid it works slightly different
>
> ATM LDAP is used to unify login only (like OAuth: if you will log-in with
> Google account it will not let you to search google users)
> You can use command line admin to import LDAP user into OM DB, this way
> search will work
>
> This can be improved
> But I believe some questions should be answered first:
> 1) is the performance will be enough
> 2) how LDAP and DB results shoul be combined
>
>
>
>>
>> 5. Are there any logs to check in order to determine what goes wrong?
>>
>
> Everything is logged into openmeetings.log :)
>
> --
> WBR
> Maxim aka solomax
>


-- 
WBR
Maxim aka solomax


Re: New tutorial installation SSL certificates and Coturn for OpenMeetings 5.0.0-M3

2020-03-28 Thread Maxim Solodovnik
Nope, `application.base.url` is not the case

Is https://:5443 accessible? (maybe you have renamed `openmeetings`
context name?)
Any errors in catalina.out or other log files in log folder?

On Sun, 29 Mar 2020 at 03:24, stefanx  wrote:

>
>
> https://:5443/openmeetings/ : HTTP Status 404 – Not Found
>
> Perhaps "application.base.url" in the Openmeetings configuration now is
> wrong ?
>
> But I now cannot change application.base.url, except with mysql db
> modification ?
>
>
> Am 28.03.20 um 04:12 schrieb Maxim Solodovnik:
> > 404 at what URL?
> >
> > On Sat, 28 Mar 2020 at 03:19, stefanx  > wrote:
> >
> > I followed this instruction, the letsencrpyt installation is ok, by
> now I get "HTTP Status 404 – Not Found"
> >
> > Any ideas ?
> >
> > Am 27.03.20 um 17:20 schrieb Alvaro:
> > >
> > > Hello,
> > >
> > > It is at your disposal a new tutorial called:
> > >
> > >
> > > Installation SSL certificates and Coturn for OpenMeetings
> 5.0.0-M3.pdf
> > >
> > >
> > > It is tested with an OpenMeetings 5 server installed on a pc
> > > at home, after NAT router; and each in the room saw and heard the
> others
> > > cameras and your own correctly.
> > > Also in the tests done, we have uploaded files, recorded video
> > > and shared desktop without any error.
> > >
> > > You can download the tutorial directly from here:
> > >
> > >
> https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20SSL%20certificates%20and%20Coturn%20for%20OpenMeetings%205.0.0-M3.pdf
> > >
> > > ...or find it here:
> > >
> > >
> https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools
> > >
> > > Best regards
> > >
> > > Alvaro
> > >
> > >
> > >
> > > -
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
>
>

-- 
WBR
Maxim aka solomax


Re: [HELP NEEDED] 5.0.0 release

2020-03-28 Thread Maxim Solodovnik
Are you using most recent version of M4?


Do you have these upload issues on demo?
(If yes - please share problem doc)

* there was an issue in Wicket fixed recently, could you update and
re-build (new Wicket SNAPSHOT should be used automatically)

2) `group/customcss` can be ignored
Any other errors (in browser console or server log)?

(chat is missing sounds like JS error)


On Sun, 29 Mar 2020 at 08:00, Peter Dähn  wrote:

> Hi Maxim,
>
> there are two issues left. Maybe my installation. But it is the same
> behaviour on test and on production.
>
> 1. I have upload problems. Not specific by time ore size. Same file might
> work or not.
>
> I get an error in the logs, but no recommended solution helped.
>
> *WARN  03-28 00:57:13.083 o.a.w.m.h.f.Form:1469 [io-5080-exec-23] - Upload
> failed: Processing of multipart/form-data request failed.
> java.io.IOException: Stream reset*
> *org.apache.commons.fileupload.FileUploadBase$IOFileUploadException:
> Processing of multipart/form-data request failed. java.io.IOException:
> Stream reset*
> *at
> org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:350)*
> *at
> org.apache.wicket.protocol.http.servlet.MultipartServletWebRequestImpl.parseFileParts(MultipartServletWebRequestImpl.java:196)*
> *at
> org.apache.wicket.markup.html.form.Form.handleMultiPart(Form.java:1419)*
> *at
> org.apache.openmeetings.web.room.sidebar.UploadDialog$1.handleMultiPart(UploadDialog.java:83)*
> *at
> org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:771)*
> *at
> com.googlecode.wicket.jquery.ui.widget.dialog.AbstractFormDialog.internalOnClick(AbstractFormDialog.java:215)*
> *at
> com.googlecode.wicket.jquery.ui.widget.dialog.AbstractDialog$2.onClick(AbstractDialog.java:440)*
> *at
> com.googlecode.wicket.jquery.ui.widget.dialog.DialogBehavior.onAjax(DialogBehavior.java:188)*
> *at
> com.googlecode.wicket.jquery.core.ajax.JQueryAjaxBehavior.respond(JQueryAjaxBehavior.java:174)*
> *at
> org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:597)*
> *at
> org.apache.wicket.core.request.handler.ListenerRequestHandler.internalInvoke(ListenerRequestHandler.java:306)*
> *at
> org.apache.wicket.core.request.handler.ListenerRequestHandler.invoke(ListenerRequestHandler.java:280)*
> *at
> org.apache.wicket.core.request.handler.ListenerRequestHandler.invokeListener(ListenerRequestHandler.java:222)*
> *at
> org.apache.wicket.core.request.handler.ListenerRequestHandler.respond(ListenerRequestHandler.java:208)*
> *at
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:917)*
> *at
> org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:63)*
> *at
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283)*
> *at
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:254)*
> *at
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:222)*
> *at
> org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:71)*
> *at
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:207)*
> *at
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:300)*
> *at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)*
> *at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)*
> *at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202)*
> *at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)*
> *at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:666)*
> *at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)*
> *at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)*
> *at
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:688)*
> *at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)*
> *at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)*
> *at
> org.apache.coyote.http2.StreamProcessor.service(StreamProcessor.java:365)*
> *at
> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)*
> *at
> org.apache.coyote.http2.StreamProcessor.process(StreamProcessor.java:72)*
> *at org.apache.coyote.http2.StreamRunnable.run(StreamRunnable.java:35)*
> *at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)*
> *at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)*
> *at
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(T

Re: virtual host config

2020-03-28 Thread Maxim Solodovnik
Locations other than `openmeetings` required for version 4.0.x only and can
be dropped for 5.0.0
(`` ... etc.)

Described here
https://stackoverflow.com/questions/51721771/apache-openmeetings-4-0-4-csrf-attack-when-using-apache2-as-proxypass

On Sun, 29 Mar 2020 at 04:37, Marcus Schulz  wrote:

> Hi Orm,
>
>
> here is a working  example for Apache webserver. You need the WebSockets
> to be rewritten.
> Expecteing the tomcat of your openmeeting installation running in port
> 5080 @ localhost.
> If your apache is configured for ssl, be sure to add scheme and security
> to your tomcat connector:
>
>  connectionTimeout="2"
>redirectPort="5443" *secure="true" scheme="https"*/>
>
>
> Apache fragment for vhost:
> ###  OpenMeetings###
> ## Custom fragment
> RewriteEngine On
> RewriteCond %{REQUEST_URI} ^/$
> RewriteRule (.*) /openmeetings/ [R=301]
> RewriteCond %{HTTP:Connection} Upgrade [NC]
> RewriteCond %{HTTP:Upgrade} websocket [NC]
> RewriteRule /(.*) ws://localhost:5080/$1 [P,L]
> RedirectMatch ^/$ https://yourservername.de/openmeetings
> ProxyPreserveHost On
>
> 
>   Require all granted
>   ProxyPass http://localhost:5080/openmeetings
>   ProxyPassReverse http://localhost:5080/openmeetings
>   RewriteEngine On
>   RewriteRule ^/(.*) http://localhost:5080/$1 [P]
> 
> 
>   Require all granted
>   ProxyPass http://localhost:5080/open
>   ProxyPassReverse http://localhost:5080/open
> 
> 
>   Require all granted
>   ProxyPass http://localhost:5080/send
>   ProxyPassReverse http://localhost:5080/send
> 
> 
>   Require all granted
>   ProxyPass http://localhost:5080/idle
>   ProxyPassReverse http://localhost:5080/idle
> 
> 
>   Require all granted
>   ProxyPass http://localhost:5080/close
>   ProxyPassReverse http://localhost:5080/close
> 
>
> Hope, that helps.
>
>
> Am 28.03.2020 um 17:32 schrieb Orm Finnendahl:
>
> Hi,
>
>  we successfully installed openmeetings on our server but have some
> issues regarding virtual host settings in the apache config. Are there
> any exampe files?
>
> Using our vpn and accessing it using the vpn local ip works like this:
> https://10.8.0.11:5443/openmeetings/
>
> Below is our entry in the apache config to make it accessible using
> https:///openmeetings
>
> We get "The requested URL was not found on this server"
>
> Any help is appreciated.
>
> --
> Orm
>
> VirtualHost *:443>
> ServerName 
> SSLEngine On
> SSLCertificateFile/etc/apache2/certs/www.mydomain.com.pem
> SSLCertificateKeyFile /etc/apache2/certs/www.mydomain.com.key
>
> SSLCACertificatePath /etc/ssl/certs/
>
>
> RewriteEngine Off
>
> ProxyRequests Off
> SetEnv proxy-nokeepalive 1
> ProxyPreserveHost On
> ProxyPassInterpolateEnv On
> ProxyPass /openmeetings http://127.0.0.1:5080/openmeetings interpolate
>
> 
> Order allow,deny
> Allow from all
> 
>
> http://127.0.0.1:5080>
> RequestHeader set "x-webobjects-server-port" "443"
> RequestHeader set "x-webobjects-server-name" 
> "mydomain.com:8800"
> RequestHeader set "x-webobjects-server-url" 
> "https://mydomain.com:8800"; 
> RequestHeader set "x-webobjects-server-protocol" "HTTP/1.0"
> RequestHeader set "x-webobjects-remote-host" "127.0.0.1"
> AddDefaultCharset UTF-8
> 
>
> ErrorLog /var/log/apache2/om-error.log
> CustomLog /var/log/apache2/om-access.log combined
>
> 
>
>
>

-- 
WBR
Maxim aka solomax


Re: Firefox 74 on windows - hanging

2020-03-28 Thread Maxim Solodovnik
Can you check browser console?
Are there anything suspicious?

On Sun, 29 Mar 2020 at 05:53, Carl Brewer  wrote:

>
> Hey,
>
> Latest build 5.0.0-m4- 3072 I think, Ubuntu server.  Edge and Chrome log
> in fine, but FF 74 on Win 10-64 seems to sit with the three spinning
> balls for ever and not get past the login screen.
>
> The PC in question has no speakers, camera or microphone.
>
> any clues? Just use Chrome? :)
>
> Carl
>
>
>

-- 
WBR
Maxim aka solomax


Re: Openmeetings, kurento and TURN behind NAT

2020-03-28 Thread YUP
Hi Maxim,
Probably I found what caused that issue with *.webm files. I run
openmeetings in a docker container which load dependent kurento
container (see my docker-compose.yml file in my first email).
Something is wrong with communication between them, maybe permission
issue, different users, don't know now.

> it would be more reasonable to have
> listening-port=80
> in this case (due to it insecure)

Good advice, I forgot that firewall allows connection to 80 port too :)

Regards,
Yarema


Re: Openmeetings, kurento and TURN behind NAT

2020-03-28 Thread Maxim Solodovnik
I'm installing KMS inside docker to avoid this
Not sure if I can help with your advanced config :(

On Sun, Mar 29, 2020, 08:57 YUP  wrote:

> Hi Maxim,
> Probably I found what caused that issue with *.webm files. I run
> openmeetings in a docker container which load dependent kurento
> container (see my docker-compose.yml file in my first email).
> Something is wrong with communication between them, maybe permission
> issue, different users, don't know now.
>
> > it would be more reasonable to have
> > listening-port=80
> > in this case (due to it insecure)
>
> Good advice, I forgot that firewall allows connection to 80 port too :)
>
> Regards,
> Yarema
>