Server-Mediated Credential Passing for Browser Auto-Login
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Non-browser-based client applications face challenges in passing credentials to launched browser applications, leading to unnecessary re-authentication, as browser applications lack access to client application credentials, and existing solutions require special browser plugins, server technology, or Single-Sign-On functionality.
Innovation Solution
A method where a server generates a one-time-use key to cache credentials, allowing the client application to fill a URL-template and launch the browser, which then retrieves the credential from the server, setting it as a cookie for seamless access to target resources without additional login requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the user leaves the browser process running at all times to maintain login credentials, then access to target resources is facilitated, but local resources are consumed and security risks increase
Solution Approach 1:
The server performs preliminary authentication and stores credentials before the browser is launched. When the client application needs to access a target resource, the server has already prepared the authentication state, allowing the browser to inherit credentials without requiring a persistent browser session or consuming local resources continuously.
2Ease of operation
If a browser plug-in is used to communicate with the client application to retrieve credentials, then credential passing is enabled, but compatibility across different browser types requires multiple plug-ins
Solution Approach 1:
The server acts as an intermediary between the client application and the browser. Instead of requiring direct communication between the client application and browser through plug-ins, the server mediates the credential passing process by receiving credentials from the client application, storing them securely, and providing them to the browser when needed, eliminating the need for browser-specific plug-ins.
3Device complexity
If the client hosts a browser control inside its process to control authentication cookies, then credential management is centralized, but the user cannot use their favorite installed browser
Solution Approach 1:
The server serves as an intermediary that manages authentication credentials centrally without requiring the client application to host a browser control. This allows the user to freely choose any installed browser while the server handles credential management, combining centralized credential control with browser selection freedom.
4Extent of automation
If Microsoft Windows single-sign on solution is used with Internet Explorer, then credential passing is automated, but SSO support and specific browser requirements are needed
Solution Approach 1:
The server-based solution provides universal credential passing functionality that works with any browser type without requiring SSO support or specific browser features. The server handles the authentication logic centrally, making the credential passing mechanism independent of browser-specific technologies while maintaining automation.
Data Source
AI summary
A technique for automated login to a browser application from a non-browser based client application begins upon the end user taking an action to access a target resource. A credential is associated with the client application as a result of a prior login operation. The technique is implemented in a server application associated with the client application. It enables automatic and secure passing of the client application credential to the counterpart browser application that is launched by the client application.