Automatic Logout Time

[jonwelch28323]

Thank you so much for all of your hard work on this tool. I just want to see if there was a way to increase the automatic logout time for a browser session seems that I have to login every 30 sec, no big deal if it isn't possible and I didn't really see any options to set this time in any of the documentation.

[lennartkoopmann]

Hi,

the default session time is 12 hours and the default inactivity timeout is 15 minutes. If you are logged out every 30 seconds, something else is going wrong. Are you sure it's 30 seconds?

You configure those settings on the "Authentication" page as a super administrator. The button/link is in the top right corner.

[jonwelch28323]

Oh man, yeah I did not see that option. I am not sure then why it takes me back to the login page so often. More than likely it is a me issue. I just want to say thank you again for putting in so much work on this. We do some interesting things with WIFI monitoring for the US GOV and this is by far one of the best tools that puts data in the right place for an analyst to quickly make decisions.

On another note we are going to be looking at how we can push this data out to an Elastic instance in the future as testing progresses. Any thoughts on putting alerts out into a ndjson log format?

[lennartkoopmann]

Are you running multiple Nzyme nodes? Make sure their clock is NTP-synchronized. Same for the database server. That could cause issues with sessions being cleaned at the wrong time / too early.

Would you like to see alerts in Elastic or raw data that Nzyme collects?

[jonwelch28323]

We're running a single node, I'll re-verify our NTP settings and synchronization to make sure we don't have any time slip.

Really it would be nice to have the option to do both to some degree just to have the ability to tailor it to my customer knowledge level. The alerts would be nice to set up a pivot from Elastic back to Nzyme for those that are not as comfortable looking at some of the data and having more of the radio data later to use some of the elastic ML features or Elastics ES|QL queries to do some deeper analysis and visualizations that we can more closely correlate with Ethernet traffic analysis.

[lennartkoopmann]

OK! Let me know if this problem persists.

Outputs are planned for after v2.0.0-final and I will keep this in mind! Makes total sense.