In Descartes Pacejet, logging in and using an existing session are not the same thing. This is an important distinction when users report repeated Multi-Factor Authentication (MFA) prompts. Opening Pacejet in a new browser tab does not automatically mean the user is logging in again. If an active session still exists, the application reuses that session and the user can continue working without entering credentials again.
How Login and Sessions Work
When a user first accesses Pacejet, the system needs to verify their identity. That login process requires a username, password and MFA code. After those credentials are verified, the application creates a session. The session acts as temporary proof that the user has already been authenticated.
As long as that session remains valid, the user can continue working without repeating the full login process. They can open additional browser tabs, close a tab and return to the same Pacejet location later, or move through different parts of the application. In these cases, Pacejet is not asking them to log in again. It is simply recognizing the active session.
When Users Need to Log In Again
Users are only prompted to enter their username, password and MFA code again when the current session is no longer valid. That usually happens because the session expired, was cleared or was invalidated by a security policy outside the application.
The session timed out because of inactivity.
The user explicitly logged out.
The browser cleared cookies or site data.
The organization applies a security policy that requires frequent reauthentication.
The identity provider, such as Microsoft Entra ID or Okta, decided a new authentication check was required.
The key point is that opening a new tab is not the same as starting a new login. If the session is still active, Pacejet continues using it.
A Simple Way to Explain It
A useful analogy is checking into a hotel. Logging in with MFA is like checking in at the front desk and showing identification. The session is like the room key. Once the guest has the room key, they can leave the room, return later, ride the elevator or visit the lobby without showing identification again. Only when the key expires or is deactivated do they need to return to the front desk and verify their identity again.
If Users See MFA Multiple Times per Day
If users are completing MFA several times per day, that usually means their sessions are ending sooner than expected. The issue is often not that Pacejet requires MFA for every tab or page visit. More often, something is causing the existing session to expire or become invalid.
Browser settings or extensions that delete cookies
Private or incognito browsing
Conditional Access or identity provider policies that require frequent reauthentication
Clock synchronization issues on the user device
Note: Frequent MFA prompts generally point to a session ending or being invalidated, not to Pacejet requiring a fresh login every time a new browser tab is opened.
Summary
When users say they have to log in many times per day, it helps to separate authentication from session reuse. Logging in happens when the system verifies identity with a username, password and MFA. Session reuse happens after that authentication succeeds. If the session remains active, users can return to the application without logging in again.