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.
According to the docs it is done by storing the IP of the host (who started the video conference)…..
-
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.
-
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! -
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.
-
@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.
-
@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.
-
Update failed, uninstall and new install works!
-
@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!
-
-