participants have to authenticate even with user_auth: false

[nebulon]

This would require some kind of LDAP or OpenID integration on MiroTalk side, which I think does not exist. Depending on if @MiroTalk would be interested, we could see if we can contribute this.

Still I am not 100% sure if all this rather belongs to the MiroTalk Web scheduler instead https://github.com/miroslavpejic85/mirotalkwebrtc

[imc67]

@avatar1024 said in participants have to authenticate even with user_auth: false:

@MiroTalk said in participants have to authenticate even with user_auth: false:

I will verify this as it is not the expected behavior.

Have you been able to reproduce this? Or any clues what the problem might be?

Many thanks

@MiroTalk With the latest stable version 1.4.14 the logic still doesn't work as expected, the setting below makes also the participants to have a username / password:

host: {
    protected: true,
    user_auth: false,

[nebulon]

So it seems that protected and user_auth are mostly covering the same things for the case where mirotalk web is not used as a scheduler.

This means if protected is false but user_auth true, then the login is shown while joining the room, while if protected is true, the login is shown before creating the room.

In both cases users have to authenticate.

Maybe we need more info from @MiroTalk here on the intended behavior or if one value only makes sens together with mirotalk web scheduler.

[imc67]

@nebulon on this page https://docs.mirotalk.com/mirotalk-sfu/host-protection/ it says:

Host Protection Logic:

If host.protected is set to true, the following logic applies:

• Host login with username and password is required.
• Upon successful login, the IP is saved as a valid authentication IP.
• After authentication, the host can create a room, join a room, and share the room link.
• All guests can join until the host logs out.
• When the host leaves the room or exits the browser, their IP is removed from valid auth IPs to prevent unauthorized access.
• To access it again, the host needs to provide a username and password.
• If host.user_auth is set to true, additional authentication is required.

[imc67]

@imc67 said in participants have to authenticate even with user_auth: false:

@nebulon on this page https://docs.mirotalk.com/mirotalk-sfu/host-protection/ it says:

Host Protection Logic:

If host.protected is set to true, the following logic applies:

• Host login with username and password is required.
• Upon successful login, the IP is saved as a valid authentication IP.
• After authentication, the host can create a room, join a room, and share the room link.
• All guests can join until the host logs out.
• When the host leaves the room or exits the browser, their IP is removed from valid auth IPs to prevent unauthorized access.
• To access it again, the host needs to provide a username and password.
• If host.user_auth is set to true, additional authentication is required.

@nebulon can it be that the app doesn’t use the host’s IP but the container “internal” IP like some apps do sometimes keeps asking for authentication?

[nebulon]

This does not really clear up things for me and I am not sure how this is IP related. Either way setting any auth/protection does show the login in my tests, as expected, and works with the users from the config file.

Maybe I don't understand what the issue is then I guess.

[imc67]

@nebulon

This setting:

host: {
    protected: true,
    user_auth: false,

should make it possible to start as host an authenticated video conference and ANY participant that has the URL can join without authentication.

According to the docs it is done by storing the IP of the host (who started the video conference)…..

[nebulon]

Ah thanks for the clarification, I missed "All guests can join until the host logs out." but yes I also alwasy get the authentication wall, so something isn't working as expected. @imc67 if you know your way around Javascript maybe you can dig through the upstream code if you have some time to help diagnose this.

[MiroTalk]

Hi everyone, Please try it now in the MiroTalk SFU v1.4.16. If the issue persists, then as soon as I have a bit more time available, I'll take a deeper look into it.

Any contributions to the project are always highly valued and appreciated!

Thank you all for your involvement in MiroTalk SFU.
We'll keep making it better with your feedback!

[nebulon]

@MiroTalk awesome and thanks. The new package for 1.4.16 is already published here.

[MiroTalk]

@nebulon Good, You're welcome!

[imc67]

I was very hopeful but it still doesn’t work as expected, the participant still needs to login while the host is online and waiting. Tested in Safari iPadOS and Safari iOS.

[jdaviescoates]

@imc67 said in participants have to authenticate even with user_auth: false:

I was very hopeful but it still doesn’t work as expected, the participant still needs to login while the host is online and waiting. Tested in Safari iPadOS and Safari iOS.

And I just tested in Firefox too. Same thing.

[MiroTalk]

@imc67 said in participants have to authenticate even with user_auth: false:

This setting:

host: {
    protected: true,
    user_auth: false,

should make it possible to start as host an authenticated video conference and ANY participant that has the URL can join without authentication.

It should be fixed in the latest MiroTalk SFU version 1.4.18.

[nebulon]

SFU version 1.4.18 package is now published

[imc67]

Update failed, uninstall and new install works!

[jdaviescoates]

@imc67 said in participants have to authenticate even with user_auth: false:

Update failed, uninstall and new install works!

Great!

Now I just have to wait for the port conflict issue to be fixed on Cloudron (which I mistakenly thought had already happened) and then I can give it another try!

[girish]

@jdaviescoates port conflict issue is already fixed in 7.7.2 .

[jdaviescoates]

@girish doesn't seem that it is:

Ah, perhaps I was just re-installing in the same place too quickly and the old install hadn't fully been cleaned up or something? (because I just hit install again and it worked)

[avatar1024]

I can confirm that with 1.4.18 authentication now works as expected! Thank you @MiroTalk and @staff !