I've seen a couple posts on this topic - Espo on Ubuntu 18.04 and also on 22.04 does not honor setting 'Auth Token Max Idle Time (hours) if I set it to .10 (10 minutes)
I've seen one post where an admin running windows did this with a Windows batch file and I could do the same with a CronTab job and an sh file if it is do-able.
I have a test server and I've been experimenting with it, and although it does trigger it seems to be hit or miss on hitting the 10 minutes to log out an idle user.
I saw a post from Yuri and verified the following:
Administration > Authentication
* Auth Token Lifetime (hours) - Set for 2 hours
* Auth Token Max Idle Time (hours) - Set for .1 (10 minutes)
Administration > Scheduled Job - check whether "Auth Token Control" is Active - done, it's active
Not sure if it matters but we also use 2-factor.
Do we know if this is do-able or am I like the dog chasing his tail ?
Any tips/suggestions/advice most welcome.
Even a 'It dosen't work that way' would be welcome if that's the case.
Thank You in advance
yuri
dexterUC
I've seen one post where an admin running windows did this with a Windows batch file and I could do the same with a CronTab job and an sh file if it is do-able.
I have a test server and I've been experimenting with it, and although it does trigger it seems to be hit or miss on hitting the 10 minutes to log out an idle user.
I saw a post from Yuri and verified the following:
Administration > Authentication
* Auth Token Lifetime (hours) - Set for 2 hours
* Auth Token Max Idle Time (hours) - Set for .1 (10 minutes)
Administration > Scheduled Job - check whether "Auth Token Control" is Active - done, it's active
Not sure if it matters but we also use 2-factor.
Do we know if this is do-able or am I like the dog chasing his tail ?
Any tips/suggestions/advice most welcome.
Even a 'It dosen't work that way' would be welcome if that's the case.
Thank You in advance
yuri
dexterUC
Comment