Browser Session Account Switching with Token Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional browser cookies fail to facilitate seamless transitions between different user accounts, particularly when operating multiple sessions with the same software product, leading to unexpected behavior or denied requests due to mismatched session tokens.
Innovation Solution
A method and system that updates the session cookie with the appropriate access token corresponding to the user account as the user switches between different browser tabs or windows, using a temporary account identifier to associate each tab with the correct session token, ensuring secure and seamless access to content from multiple user accounts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional browser cookies are used to store session information, then a single user account session can be maintained, but seamless transitions between multiple user accounts are not facilitated
Solution Approach 1:
The patent segments the session management by creating separate session tokens for different user accounts. Each browser tab can have its own session token associated with a specific user account, allowing independent session management for multiple accounts without interference. This segmentation enables seamless switching between accounts by simply changing which session token is active.
Solution Approach 2:
The patent introduces session tokens as intermediary elements between the browser and the host service. These tokens act as mediators that carry account-specific authentication information, allowing the browser to switch between user accounts by presenting different tokens. This intermediary mechanism enables seamless account transitions while maintaining secure, account-specific sessions.
2Adaptability or versatility
If multiple sessions with different user accounts are operated simultaneously, then access to multiple accounts is enabled, but unexpected behavior or denied requests occur due to mismatched session tokens
Solution Approach 1:
The patent segments session information into distinct, account-specific session tokens. Each token is uniquely associated with a particular user account and is stored separately in the browser. This segmentation ensures that when multiple sessions are operated simultaneously, each tab or window maintains its own valid session token, preventing mismatched token errors and ensuring reliable account-specific access.
Solution Approach 2:
The patent applies local quality by ensuring that each session token has the specific property of being valid only for its associated user account. The session tokens are configured with account-specific credentials and permissions, so that each token locally embodies the authentication state of its parent account. This local quality guarantee prevents cross-account token mismatches and ensures reliable session management.
3Reliability
If session cookies are stored at the client device, then authentication state is maintained, but the same cookie cannot facilitate transitions between different user accounts
Solution Approach 1:
The patent segments the traditional single session cookie into multiple session tokens, each stored separately in the browser. Instead of one cookie containing a single authentication state, the system stores multiple tokens in an array or collection, with each token representing a separate user account's authentication state. This segmentation allows the client device to maintain reliable authentication for multiple accounts simultaneously.
Solution Approach 2:
The patent makes the session storage mechanism universal by designing it to handle both single-account and multi-account scenarios. The session token storage system can accommodate one or multiple tokens, automatically selecting the appropriate token based on the active user account. This multi-functional design maintains reliable authentication state while adapting to different account switching scenarios.
Data Source
AI summary
Embodiments include a method for hosting secure content between a host service and a client device. One example includes causing display of a graphical user interface on a browser application executing on the client device where the user interface includes a first tab associated with a first session between the browser application and the host service using a first account associated with a user and a second tab associated with a second session between the browser application and the host service using a second account associated with the user. In response to a user selection of the second tab while the first tab is displayed, receiving the first session token and a temporary account identifier, identifying a second token, using the temporary account identifier, and causing the browser application to display second secure content within the second tab associated with the second session.


