09-23-2016, 03:19 PM
Well, that will be tough with only client side operations. Once the data reaches the client and displayed in the browser, it is out of the hands of the server and the server can't do anything about it. The only thing the server could do is control access on the NEXT request where the server is once again involved in the transaction.
Even things like banking sites are at the mercy of the users browser. In that case, the session gets expired on the server side, and on the client side the pages are served with an expiry in the cache so they can't be displayed after the browser is closed.
So to me, it would appear that you could do what banks or other sides do, and run a JavaScript check and logout, but that can be disabled...just as a warning.
Even things like banking sites are at the mercy of the users browser. In that case, the session gets expired on the server side, and on the client side the pages are served with an expiry in the cache so they can't be displayed after the browser is closed.
So to me, it would appear that you could do what banks or other sides do, and run a JavaScript check and logout, but that can be disabled...just as a warning.