Has anyone else noticed not being logged out after a user inactivity time period elapses? Seems that there is a frequent interaction between the ignition api and the browser that is occurring so it thinks the user is still alive.
This interaction is best seen when watching with a network dev tool open while on an ignition gateway page.
1 Like
Yes, this is a known issue. You can actually see this same behavior in 8.1 - though only on certain pages. Your intuition regarding the polling nature of the page is spot-on, and is indeed the root cause. Being such, the pages that exhibit this behavior in 8.1 are the pages which use frequent polling. With the re-write for 8.3 where every page now polls, this undesirable behavior has become far more widespread. We have a ticket to improve this behavior, though not a firm estimated date or target version.
Update:
This was identified as far back as 8.1.1 from what I can tell.
Ok. Is it all pages in the Ignition Gateway now? It seems that even the home page has the issue now as well.
Yes, every 8.3 page will exhibit this behavior because an inherent part of the re-write is that pages are constantly getting new data by way of polling, and this polling qualifies as activity as far as the Gateway is concerned.
So how does an administrator on the gateway become logged out on inactivity?
In 8.3, the only way for a session to become “inactive” is due to network disconnection for longer than the supplied inactivity timeout. I see this on my local environment whenever I put my laptop to sleep, which terminates the wi-fi processes and results in no activity from the session.
1 Like