I noticed that the new file was one byte less, I think that there was an
unprintable character added to the file when I appended the new keys
from the web.
Ali
On 12/30/22 2:28 PM, Maxim Solodovnik wrote:
from mobile (sorry for typos ;)
On Fri, Dec 30, 2022, 18:27 Ali Alhaidary
wrote:
from mobile (sorry for typos ;)
On Fri, Dec 30, 2022, 18:27 Ali Alhaidary
wrote:
> Thank you max, the test was successful, then I just rearranged the
> openmeeting.properties file entries as per build#210 and adding the missing
> keys (as I did before) and upgraded to build#210 and the system w
Thank you max, the test was successful, then I just rearranged the
openmeeting.properties file entries as per build#210 and adding the
missing keys (as I did before) and upgraded to build#210 and the system
was up and running. Was it not working because entries were not in the
same order?
BTW
hmmm
Are you sure you sent valid logs?
Could you please try:
0) stop OM (if any)
- - check with `ps -ef|grep java`
1) unpack to NEW empty folder
2) change nothing
3) cd to this NEW_FOLDER/apache-openmeetings-7.0.0-SNAPSHOT/
3) run `./admin.sh -i -v -user ui_admin -email someem...@gmail.com -tz
Hi Max, it is there but blank, should I fill it with a value? what would
the value be?
Ali
On 12/30/22 6:50 AM, Maxim Solodovnik wrote:
Hello Ali,
According to the log: "Could not resolve placeholder 'otp.issuer' in
value "${otp.issuer}""
Your `openmeetings.properties` doesn't have the line
Hello Ali,
According to the log: "Could not resolve placeholder 'otp.issuer' in value
"${otp.issuer}""
Your `openmeetings.properties` doesn't have the line:
```
otp.issuer=
```
please add it :)
On Fri, 30 Dec 2022 at 00:59, Ali Alhaidary
wrote:
> Attached log files of the latest 210 build
>
>
from mobile (sorry for typos ;)
On Thu, Dec 29, 2022, 01:40 Ali Alhaidary
wrote:
> Yes, I know that these lines were added, as you can see in my previous
> post, however, I did not change it assuming that the application will
> perform as usual until we set 2 factor authentication.
>
Yes, this
Yes, I know that these lines were added, as you can see in my previous
post, however, I did not change it assuming that the application will
perform as usual until we set 2 factor authentication.
Is there and keys I should add to the database on build#205 ?
Ali
On 12/28/22 2:10 PM, Maxim Solod
The following section has been added :)
## Time-based One Time Password ##
## Please NOTE these values need to be changed BEFORE users will set-up OTP
for themselves
## otherwise they can't login
# NOTE Config->application.name will be used if blank
otp.issuer=
ot
Is it possible just to pint it out please?
Ali
On 12/27/22 6:53 PM, Maxim Solodovnik wrote:
I would start with examine the logs
and will add missing key-value part to openmeetings.properties :)
On Tue, 27 Dec 2022 at 19:00, Ali Alhaidary
wrote:
Where and what ? :-)
Ali
On 12
I would start with examine the logs
and will add missing key-value part to openmeetings.properties :)
On Tue, 27 Dec 2022 at 19:00, Ali Alhaidary
wrote:
> Where and what ? :-)
>
> Ali
> On 12/27/22 8:13 AM, Maxim Solodovnik wrote:
>
> you have to add new values to your config :)
>
> #206 is at
Where and what ? :-)
Ali
On 12/27/22 8:13 AM, Maxim Solodovnik wrote:
you have to add new values to your config :)
#206 is at demo-next
seems to work as expected :)
On Tue, 27 Dec 2022 at 10:37, Ali Alhaidary
wrote:
No, I did not change anything in openmeetings.properties as we
wa
you have to add new values to your config :)
#206 is at demo-next
seems to work as expected :)
On Tue, 27 Dec 2022 at 10:37, Ali Alhaidary
wrote:
> No, I did not change anything in openmeetings.properties as we want to use
> om as before initially...
>
> ## Time-based One Time P
No, I did not change anything in openmeetings.properties as we want to
use om as before initially...
## Time-based One Time Password ##
## Please NOTE these values need to be changed BEFORE users will set-up
OTP for themselves
## otherwise they can't login
# NO
Anything suspicious in the log?
Have you updated openmeetings.properties with "otp" specific values?
from mobile (sorry for typos ;)
On Mon, Dec 26, 2022, 22:54 Ali Alhaidary
wrote:
> Could not login from moodle plugin, and (HTTP Status 404 – Not Found) in
> stand alone app.
>
> Ali
> On 12/26
Could not login from moodle plugin, and (HTTP Status 404 – Not Found) in
stand alone app.
Ali
On 12/26/22 5:18 PM, Ali Alhaidary wrote:
Seems ok, and translated...
Ali
On 12/26/22 8:37 AM, Maxim Solodovnik wrote:
Seems to be implemented
I would appreciate if someone can test this new funct
Seems ok, and translated...
Ali
On 12/26/22 8:37 AM, Maxim Solodovnik wrote:
Seems to be implemented
I would appreciate if someone can test this new functionality
(And wording :)))
On Thu, 22 Dec 2022 at 14:14, Maxim Solodovnik
wrote:
On Thu, 22 Dec 2022 at 14:01, seba.wag...@gmail.c
Seems to be implemented
I would appreciate if someone can test this new functionality
(And wording :)))
On Thu, 22 Dec 2022 at 14:14, Maxim Solodovnik wrote:
>
>
> On Thu, 22 Dec 2022 at 14:01, seba.wag...@gmail.com
> wrote:
>
>> Sry I did not have enough time. But it would be a good feature to
On Thu, 22 Dec 2022 at 14:01, seba.wag...@gmail.com
wrote:
> Sry I did not have enough time. But it would be a good feature to add.
>
> Also a good message we can share around enhancing OpenMeetings security.
> Relevant for many education/public environments.
>
I agree :))
Will update JIRA/demo-
Sry I did not have enough time. But it would be a good feature to add.
Also a good message we can share around enhancing OpenMeetings security.
Relevant for many education/public environments.
Thx
Seb
Sebastian Wagner
Director Arrakeen Solutions, OM-Hosting.com
http://arrakeen-solutions.co.nz/
h
https://issues.apache.org/jira/browse/OPENMEETINGS-2755
will try to implement it :)
On Wed, 3 Aug 2022 at 13:45, Ali Alhaidary
wrote:
> +1
>
> Yes, why not...
>
> Ali
> On 8/3/22 8:34 AM, Maxim Solodovnik wrote:
>
> we already have BSD 3-clause:
> https://github.com/apache/openmeetings/blob/mas
+1
Yes, why not...
Ali
On 8/3/22 8:34 AM, Maxim Solodovnik wrote:
we already have BSD 3-clause:
https://github.com/apache/openmeetings/blob/master/LICENSE#L2479
will need to add one line only :)
On Wed, 3 Aug 2022 at 12:25, seba.wag...@gmail.com
wrote:
There seem to be a few options
we already have BSD 3-clause:
https://github.com/apache/openmeetings/blob/master/LICENSE#L2479
will need to add one line only :)
On Wed, 3 Aug 2022 at 12:25, seba.wag...@gmail.com
wrote:
> There seem to be a few options for Google using Java
> E.g. https://github.com/wstrange/GoogleAuth
>
> I do
There seem to be a few options for Google using Java
E.g. https://github.com/wstrange/GoogleAuth
I don't quite see in that lib how it generates the QR code for scanning but
there should be a way :)
The BSD license would require us to add a copy left into our License file,
but in general it would
Hello Seb,
Sorry for a late response, I'm on vacation :)
I would
+1 this feature :)
The problems we'll need to solve
- add 2fa mechanisms other than email (not sure if apps like "Google
authenticator" has open source API :(, we can use telegram API )
- we'll need to move this out of om_user
Not many pros or cons in this discussion.
But I think it would be a good option to have available for users. As well
as a good feature to advertise for. Especially in order to use OpenMeetings
in a Gov/Education environment where compliance may require to have 2
factor auth for applications in ord
I would like to add a ticket to investigate and look into adding 2 factor
authentication to OpenMeetings. As an optional feature, default would be
turned off.
There are various libraries to achieve 2 factor auth. I would
probably prefer using the Google Authenticator as a method since it seems
the
27 matches
Mail list logo
