Browser Virtual Session Launch via Native Messaging Host
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Browsers lack the secure connection and persistence capabilities of native applications, making it challenging to access and manage connection leases and authentication data, especially in browser-based launches of virtual sessions, which affects user experience and security.
Innovation Solution
The system leverages the secure connection and persistence capabilities of native applications to manage connection leases and authentication data, even after the browser is closed, by using a native messaging host and browser extensions to relay communications and perform background operations, ensuring up-to-date connection lease and authentication data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If browsers are used to initiate virtual sessions, then user experience and accessibility are improved, but security and connection persistence deteriorate due to lack of native application capabilities
Solution Approach 1:
The patent introduces a native messaging host as an intermediary component that bridges the browser and the virtual session infrastructure. The browser extension communicates with the native messaging host, which in turn communicates with the virtual session service. This intermediary maintains connection persistence and security credentials on the client device even when the browser is closed, while still allowing the browser to provide the familiar user interface for initiating sessions.
2Ease of operation
If browser-based virtual session initiation is implemented, then accessibility and ease of use are improved, but security capabilities and authentication data management worsen
Solution Approach 1:
The native messaging host acts as a secure intermediary that handles authentication data and connection credentials. Instead of the browser directly managing sensitive authentication information, the browser extension communicates requests through the native messaging host, which manages the security credentials securely on the client device. This architecture maintains security while preserving browser accessibility.
Solution Approach 2:
The system segments the virtual session initiation functionality into separate components: the browser provides the user interface, the browser extension handles communication protocols, the native messaging host manages security credentials and connection persistence, and the virtual session service provides the actual virtual desktop resources. This segmentation allows each component to specialize in its strength while mitigating the weaknesses of individual components.
3Reliability
If native application capabilities are used for connection management, then security and persistence are improved, but device compatibility and accessibility worsen
Solution Approach 1:
The system implements a universal architecture that works across multiple device types and operating systems. The native messaging host is implemented as a cross-platform component that can run on Windows, macOS, and Linux. The browser extension adapts to different browser types (Chrome, Firefox, Edge) while maintaining consistent functionality. This multi-functional design allows the system to provide native application-level security and persistence capabilities across diverse device platforms.
Data Source
AI summary
A computing device may include a memory and a processor configured to cooperate with the memory to run a browser configured to generate a user interface to display a virtual session from a host computing device, and an application configured to establish a connection with the host computing device. The processor may further run code configured to cause the browser to connect with the host computing device using the connection established by the application to display the virtual session within the user interface.