Premature session timeouts - Kazakh feedback

[MiriamObibi]

Describe the bug

Provider interface: If a page is accidentally closed or there is a need to go to another page, and/or refresh, login process is to be done on the same device again

To Reproduce
Login (tested as a provider on web but clients have also reported a similar issue)
Go to any other page on the web app after login in (e.g. Activity history)
Leave the tab/window, to go to another website
Return to the open usupport browser tab/window (before the inactivity timeout expires)
Click on another usupport page (continue browsing as usual) or refresh the page you left open.

Expected behavior
Users should not be required to log in again unless the inactivity time out has expired.

Screenshots
None.

Desktop (please complete the following information):

• OS: MacOS, Windows
• Browser: Chrome,Safari

Smartphone (please complete the following information):
No

Additional context
Add any other context about the problem here.

[sebastian-7DIGIT]

@MiriamObibi

Regrettably, we are unable to address situations where a user accidentally closes the browser tab. Our recommendation is to encourage users to exercise caution when performing this action, especially if the login process causes inconvenience.

From a technical standpoint, the requirement is quite clear: when a browser tab is closed, the user session should be terminated, necessitating the user to log in again. This is the expected behaviour across all platforms at this moment in time. According to requirements raised from previous conversations with Vikas.

It’s worth noting that in some specific scenarios and browsers, this implementation faces a minor issue that cannot be resolved without deviating from the requirement of destroying the user session when the tab is closed.

One such scenario arises when a user is logged in on either a single or two separate tabs within the same browser. In certain situations, refreshing the page may prompt the user to log in again.

One potential solution to this problem is to restrict the user session to a single tab. This means that when a user attempts to access any interface in separate tabs, they will need to log in every time.

Could you please confirm whether this proposed solution meets your requirements?