Default timeout for authenticated users

HI there,

I installed Jitsi Meet on a Ubuntu 16.4 LTS and applied the secured domain configuration:

everything looks perfect so far.

Users are authenticated to start the meetings, while guests will wait until the meeting starts by authenticated users and then they can join.

The only thing that I could not figure out (even after searching this forum and google) is the session’s timeout for authenticated users. Once a user logs in, he is always logged in, I know there is a logout button, but it would be great if the session’s timeout is set to 2-3 minutes from the time the meeting is over.

So, is this configurable?

Thanks for all the efforts done so far with this great solution.

IIRC the login information is saved in local / session storage, that’s how it’s remembered.

Thanks for the quick reply, but how do I set this up. Is in the Prosody, Jicofo configuration files?

In jicofo there is an auto login option which you can disable and no caching will be taken into account, and will ask for user/pass every time

See these options you can set in

That is great.

I just updated the under /etc/jitsi/jicofo and added the following setting:


Restarted all the services.

Unfortunately, nothing changed, I am still logged in forever!

Am I missing something?

You need to set org.jitsi.jicofo.auth.DISABLE_AUTOLOGIN=true

Worked like a charm, thanks for the help :smiley:

I have set “org.jitsi.jicofo.auth.DISABLE_AUTOLOGIN_PNAME=true” in /etc/jitsi/jicofo/, but its not working.

Hi @saghul : I have done the same setup. But it is not working in jitsi-meet 2.0.5390-3 version
But previously it was working in the older version. Could you please help on this regards.Thanks, Also be noted my prosody version is 0.11.8. Is this happening because of this? And below is the configuration for /etc/jitsi/jicofo/

That should work. @Boris_Grozev any idea? Maybe something related to the new config?

Thanks for your response @saghul . I am not very sure about that. Actually this issue was not there in the older version of jitsi-meet. It is happening after enabling the moderator in the new jitsi-meet version. Any Idea why is it happening? Also in this scenario, recording is also not working getting some javascript error.