Browser Tab Account Switching Using Tab-Specific Session Tokens
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional browser cookies do not 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 a specific user account and ensuring valid session tokens are used for secure content display.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional browser cookies are used to maintain session state, then the system is simple to implement, but seamless transitions between different user accounts in multiple browser tabs are not facilitated
Solution Approach 1:
The patent segments the session management by creating separate session tokens for each browser tab, allowing each tab to maintain its own account context independently. This enables multiple user accounts to coexist in the same browser session without interference, resolving the contradiction between adaptability and complexity.
Solution Approach 2:
The patent introduces a temporary account identifier as an intermediary mechanism that bridges the browser tab and the session token. This intermediary enables seamless account switching by allowing the system to identify and retrieve the appropriate session token based on the temporary identifier associated with each tab.
2Reliability
If a single session token is shared across multiple browser tabs, then device complexity is reduced, but session token mismatch and denied requests occur when switching accounts
Solution Approach 1:
The patent divides the single shared session token into multiple tab-specific session tokens, ensuring that each browser tab has its own valid session token corresponding to its associated user account. This eliminates session token mismatch errors while maintaining manageable complexity through systematic token distribution.
Solution Approach 2:
The patent changes the session token parameter from a single shared value to multiple tab-specific values. Each session token is uniquely associated with a specific user account and browser tab, ensuring validity and preventing denied requests when switching accounts.
3Productivity
If manual account switching procedures are implemented, then session security is maintained, but user productivity decreases due to additional user intervention required
Solution Approach 1:
The patent implements self-service account switching by automatically detecting when a user switches between browser tabs and autonomously retrieving the appropriate session token using the temporary account identifier. This eliminates the need for manual account switching procedures while maintaining session security through automated token validation.
Solution Approach 2:
The patent incorporates feedback mechanisms where the system monitors browser tab state changes and automatically responds by updating the session token accordingly. This closed-loop feedback system maintains both productivity and security by ensuring the correct session token is always active without requiring user intervention.
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.


