Jump to content

Guy Steels

Members
  • Content Count

    5
  • Joined

  • Last visited

About Guy Steels

  • Rank
    IT Apprentice

Profile Information

  • Location
    Brussels, Belgium

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The web application has a "Session Timeout" setting. Since a few weeks this setting has no effect anymore. The setting we use is 120 minutes but we are always logged out of the web application after +- 5 15 minutes of inactivity. I'm not 100% sure but it seems this issue popped up since the enhanced 2FA update which was released a few weeks ago.
  2. Thank you Chris. I had overlooked that config. This already helps a lot.
  3. We would like to increase the time a loggedin session is active in the web application. Currently, you get logged out after +- 30 minutes of inactivity. As far as I know there is no config available that can be modified in the webapp itself (we currently have a team account). I tried to fix it using a browser addon/extension ("Staying alive" for Chrome or "Session alive" for Firefox) but I didn't succeed in configuring it correctly to make it work. A background request on the main url (eg. ...pulseway.com/app/main/systems) did not refresh the session. If anyone has some pointers how I should configure the stay alive extensions it would be appreciated.
  4. While inputting notes through the webapp I noticed that only 256 characters of notes are saved, allthough the interface itself accepts more input. The GUI should somehow show that there's a character limit. On the other hand, it would be nice if we could save more than 256 characters.
×
×
  • Create New...