Agent Application Context ID Management for Shared Device Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Employees on shared or enterprise-managed devices face inefficiencies and frustrations due to repeated logins into applications, especially Line of Business (LOB) applications, and issues with application access and user data management, leading to productivity losses and security risks.
Innovation Solution
Implementing a system that uses a single sign-on (SSO) check-out process with an agent application to manage user profiles and context IDs, ensuring secure access to SDK-based applications by comparing local, agent, and server context IDs to authenticate users and manage user data, thereby eliminating the need for repeated logins and ensuring data security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If employees use shared devices with multiple applications, then device utilization and collaboration are improved, but repeated login requirements increase time loss and reduce productivity
Solution Approach 1:
The patent merges the authentication and user data management functions into a single centralized system. The agent application combines context ID generation, user profile storage, and application access control into one integrated mechanism that operates across all SDK applications, eliminating the need for separate login processes for each application.
Solution Approach 2:
The agent application serves multiple functions simultaneously: it manages device checkout/checkin, generates and stores user profiles, creates context IDs for application access control, and coordinates data sharing across applications. This multi-functional design eliminates the need for multiple separate authentication systems.
2Reliability
If applications are installed and configured for each user, then user-specific access and data security are improved, but application management complexity increases
Solution Approach 1:
The patent segments user data and application access control into distinct, manageable components. User profiles containing personal information are separated from application code, and context IDs are generated as independent tokens that link users to their specific data and permissions. This segmentation allows secure data isolation without complex user-specific application configurations.
Solution Approach 2:
The agent application acts as an intermediary between users, applications, and data. It mediates access by generating context IDs that serve as keys to user profiles and controlled data, eliminating the need for direct user-application configuration and simplifying security management.
3Reliability
If users check out devices frequently, then user access control and data privacy are improved, but application access delays increase
Solution Approach 1:
The system performs preliminary actions by pre-generating and storing context IDs along with user profiles when devices are checked out. Application context IDs are prepared in advance and cached locally, allowing applications to access user data immediately without requiring real-time authentication or network communication during actual use.
Solution Approach 2:
The patent creates copies of user profiles and application contexts locally on the device during the checkout process. These local copies include user data, preferences, and application states, enabling fast access without continuous synchronization or re-authentication, while maintaining security through encrypted storage and context ID validation.
Data Source
AI summary
Software development kit (“SDK”) applications may be implemented with user data on an enterprise end-user or shared device subsequent to a single check-out process on the device. A user profile and a context ID for a user can be accessed based on user provided credentials. An SDK application can be identified as one application of an application cluster including at least two applications. A status of a local context ID (“LCID”) of the SDK application can be determined, and a value for the LCID can be established based on the status and a value of a comparison context ID obtained from a server or an agent application. The LCID and a context ID for a keychain for the application cluster can be compared, and the SDK application can be implemented with user specific user data obtained from the agent application or the keychain based on a result of the comparison.