User Timeout, Interface and Logs

[mcit]

Hello, I have installed a fresh copy of OpenEFA and have set up a test domain so that I can familiarise myself with it.
I have a few starting questions:

1. Whilst I am learning / testing, I am finding that 30 minute session idle time is a little restrictive. Is there a way that I can set a longer [or even disable the] timeout?

2. I am very used to the EFA Mailscanner interface, this interface is very different and I am not sure I understand it yet. For example, I can see 9 messages in the User Messages screen, but only 2 in All Emails [these 2 are also shown in User Messages]. Can someone give me some idea of the interface logic?

3. Finally, at the end of the installer, it defines email logs are being located at /var/log/mail.log, however, this file does not exist, I did choose yes for verbose logging in the setup phase.

It looks interesting so far, clearly a lot of work has been put into this, looking forward to seeing how it performs.

Thanks
Matthew

[mcit]

I seem to have answered question #1:

In /opt/spacyserver/web/app.py I changed the 'admin' timeout to 300 minutes. However, it seems that the larger the number I put here, the longer the login time takes; on a 300 minute setting, the login is taking a full 2 mins after the password is entered.
Out of interest, when I set 300 minutes, the top corner of the GUI shows 5hr timeout rather than 6.

Also, when settings like this are changed, is there a way to reload the configuration without a reboot?

Matthew

[mattch]

I found the mail log. Mine was missing until a reboot lol

[adrastosefa]

I seem to have answered question #1:

In /opt/spacyserver/web/app.py I changed the 'admin' timeout to 300 minutes. However, it seems that the larger the number I put here, the longer the login time takes; on a 300 minute setting, the login is taking a full 2 mins after the password is entered.
Out of interest, when I set 300 minutes, the top corner of the GUI shows 5hr timeout rather than 6.

Also, when settings like this are changed, is there a way to reload the configuration without a reboot?

Matthew

You should be able to run systemctl reload spacyweb. Or systemctl restart spacyweb

[adrastosefa]

To extend the timeout:

1. Edit the file:
sudo nano /opt/spacyserver/web/app.py
2. Find the ROLE_SESSION_TIMEOUTS dictionary (around line 316)
3. Change the timeout values (in minutes) for the role(s) you want:
ROLE_SESSION_TIMEOUTS = {
'admin': 120, # Extended to 2 hours
'domain_admin': 120,
'client': 120,
'default': 120
}
4. Save the file and restart the web service:
sudo systemctl restart spacyweb

I seem to have answered question #1:

In /opt/spacyserver/web/app.py I changed the 'admin' timeout to 300 minutes. However, it seems that the larger the number I put here, the longer the login time takes; on a 300 minute setting, the login is taking a full 2 mins after the password is entered.
Out of interest, when I set 300 minutes, the top corner of the GUI shows 5hr timeout rather than 6.

Also, when settings like this are changed, is there a way to reload the configuration without a reboot?

Matthew