The difference when viewing Ezekia on your mobile when compared to your web browser, primarily stems from the way mobile browsers handle sessions compared to browsers on laptops or computers, and the various factors involved in this behaviour.
Mobile devices often behave differently due to several variables that affect how sessions are maintained:
1. Background Process Handling: Mobile operating systems, such as Android or iOS, are designed to manage background processes differently from desktop systems. For instance, on your mobile browser, the session may remain active in the background unless the browser or phone specifically terminates it. This behaviour is dependent on the phone's operating system and its specific power management settings, which aim to optimise battery life by managing background applications but also balance this against page load times.
2. Session & Cookie Settings: Each browser (whether on mobile or desktop) handles cookies differently, especially concerning session cookies. Mobile browsers might retain session cookies for longer periods, allowing you to remain logged in even after closing the browser, depending on the cookie retention settings configured on your device or the browser itself.
3. Remote Access Security Policies: Your company's remote access may enforce stricter security protocols, such as automatic timeouts or forced logouts after periods of inactivity, to comply with organisational security policies. This could explain why you are automatically logged out when using Ezekia through remote access, as opposed to when accessing it via your phone.
4. Sleep Settings: Mobile devices also have different sleep and idle settings that may prevent a session from timing out if the app or browser remains semi-active in the background. This could inadvertently be keeping the session active despite no real user activity taking place on the page.
5. Browser Variations: Different browsers (Chrome, Edge, Safari, Firefox, Opera etc.) across devices have unique ways of handling session management, which can further explain the variability in behaviour.
Two-factor authentication (2FA) provides an additional layer of security designed to protect the login process itself. However, 2FA only comes into effect when you are actually logging in. Once you are logged into Ezekia, the session remains active until it is terminated (either by logging out, or automatic timeout policies). If your session has persisted, the 2FA process will not trigger again until you need to log back in.
Given that mobile phones and computers differ in their approach to background processes, security, and session handling, these factors combine to create the experience you’re observing. Without detailed knowledge of your phone’s make/model, browser, operating system, and its individual settings (such as sleep settings or background refresh processes), it’s difficult to provide an exact answer.
If security is a concern, we recommend either manually logging out of Ezekia after each session on your mobile device or adjusting your browser settings to clear cookies and sessions when closed.