Previously, only the Shell would participate in implementing session idle timeouts. This means that a session was not guaranteed to time out when the browser decided to suspend JavaScript execution. Now the main actor for session idle timeout is the bridge: When JavaScript starts, it will instruct the bridge to start the session idle timeout timer. When it expires, the bridge will exit and end the session even if JavaScript has been stopped. While waiting for the timers to elapse, the bridge will send events out over a new "session-control" channel type that inform the pages when the final countdown has started, and when it is time to logout. User activity is also reported over such a channel.
Cockpit
A sysadmin login session in a web browser
Cockpit is an interactive server admin interface. It is easy to use and very lightweight. Cockpit interacts directly with the operating system from a real Linux session in a browser.
Using Cockpit
You can install Cockpit on many Linux operating systems including Debian, Fedora and RHEL.
Cockpit makes Linux discoverable, allowing sysadmins to easily perform tasks such as starting containers, storage administration, network configuration, inspecting logs and so on.
Jumping between the terminal and the web tool is no problem. A service started via Cockpit can be stopped via the terminal. Likewise, if an error occurs in the terminal, it can be seen in the Cockpit journal interface.
You can also easily add other machines that have Cockpit installed and are accessible via SSH and jump between these hosts.