Local Authority Service for Cross-Browser Hardware Key Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing multi-factor authentication systems face difficulties in supporting hardware-protected key authentication within web browsers, as each browser has unique methods for interacting with hardware key readers, making it challenging to find a stable implementation across different browsers.
Innovation Solution
A local authority service on the user's machine interacts with the hardware key reader to obtain authentication information, generating a claim-based token signed with the hardware-protected key, which is then posted back to the web application for user authentication, without requiring custom code in the browser.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If custom code is inserted into each browser to support hardware-protected key authentication, then authentication functionality can be achieved, but device complexity and maintenance difficulty increase significantly
Solution Approach 1:
The patent introduces a server as an intermediary between the web application and the hardware key reader. The server hosts a web application that communicates with a backend service, which in turn interacts with the hardware key reader through standardized interfaces. This mediator architecture allows hardware-protected key authentication to be implemented without inserting custom code into browsers, as the authentication logic is centralized on the server side where it can access hardware resources directly.
2Adaptability or versatility
If different browser-specific implementations are used for hardware key reader interaction, then each browser can be optimized, but cross-browser compatibility and stability deteriorate
Solution Approach 1:
The patent creates a universal authentication system that works across all browsers by moving the hardware interaction logic from the client (browser) side to the server side. The web application provides a standardized interface that can be accessed by any browser, while the server handles the browser-specific or platform-specific hardware key reader interactions. This universal approach eliminates the need for browser-specific implementations, ensuring consistent authentication functionality across different browsers and platforms.
3Reliability
If hardware-protected key authentication is implemented directly in the browser, then authentication security is enhanced, but ease of operation and deployment worsen due to browser limitations
Solution Approach 1:
The server acts as an intermediary that provides secure hardware-protected key authentication without requiring direct browser-hardware integration. The web application on the server communicates with the hardware key reader through standardized backend interfaces, maintaining security while avoiding browser limitations. This approach enhances authentication security through hardware protection while improving ease of operation, as users can authenticate through any standard web browser without special plugins or custom code.
Data Source
AI summary
A web application that is attempting to access a site hosted by a system that needs authentication based on a hardware-protected key is redirected to a local authority service on the machine. The local authority service interacts with a hardware key reader to obtain authentication information from a hardware key holder. The local authority service illustratively interacts with the system being accessed in order to obtain an operation result, based on the hardware-protected key obtained through the hardware key reader. The operation result is then posted to the web application, by the local authority service, for use in authenticating the user.