Password Manager Autofill Security via Context Identifier Matching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional password managers face challenges in securely autofilling login credentials across web pages and mobile apps, often failing to recognize domain relationships and being vulnerable to malicious websites and apps.
Innovation Solution
A computer-implemented method for securely autofilling login fields using a password manager that includes authenticating users, building an autofill security database, performing computing source autofill security checks, and matching computing sources to accounts within the database to ensure secure credential autofill.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional password managers refuse to autofill credentials on different domains (e.g., accounts.example.com vs www.example.com), then security is improved by preventing phishing, but usability deteriorates by failing to recognize legitimate domain relationships
Solution Approach 1:
The patent introduces an intermediary mechanism (context identifier matching system) that mediates between the password manager and the computing source. This intermediary analyzes domain relationships, app identifiers, and context identifiers to determine whether autofill should be permitted, thereby resolving the contradiction between security and usability by adding an intelligent decision layer rather than using simple domain matching
Solution Approach 2:
The patent changes the matching parameters from simple domain name comparison to a multi-parameter system including context identifiers, app identifiers, certificate signatures, and domain relationship analysis. This parameter change enables the system to recognize legitimate relationships between domains while maintaining security against phishing
2Ease of operation
If conventional password managers use simple domain matching for autofill, then ease of operation is improved by quickly identifying matching credentials, but security deteriorates by being vulnerable to phishing attacks on similar domains
Solution Approach 1:
The patent segments the credential matching process into multiple independent verification components: domain matching, context identifier matching, app identifier matching, and certificate signature verification. This segmentation allows the system to maintain ease of operation through automated multi-factor verification while improving security by requiring multiple matching criteria to be satisfied simultaneously
3Productivity
If conventional password managers autofill credentials on any matching domain, then productivity is improved by enabling quick login, but security deteriorates by allowing credential theft on malicious websites
Solution Approach 1:
The patent performs preliminary security verification actions before autofilling credentials. The system pre-establishes trust relationships by verifying computing source authenticity, checking certificate signatures, and validating context identifiers before credential disclosure. This preliminary action ensures quick login (productivity) while preventing credential theft (security) by blocking malicious sources in advance
4Reliability
If conventional password managers fail to recognize mobile app domain relationships, then security is maintained by not autofilling to unauthorized apps, but usability deteriorates by refusing legitimate app autofill requests
Solution Approach 1:
The patent creates a universal matching system that handles multiple types of computing sources (web browsers, mobile apps, desktop applications) through a unified approach. The system uses platform-specific identifiers (Android app IDs, iOS bundle identifiers) combined with context identifiers to universally recognize legitimate applications across different platforms, maintaining security while enabling usability for authorized apps
Data Source
AI summary
A new password manager for safely autofilling login user login credentials performs multiple layers of security check to protect users' confidential data. User interface elements of a computing source, such as a web page or a mobile app, are parsed for determining that password input fields are present. In such a case, a autofill control is displayed for activating user authentication for accessing the password manager. The password manager determines a computing source identifier of the computing source, determines a list of context identifiers corresponding to the computing source, performs computing security check, matches the computing source identifier to an account, and selects an account. The password manager then performs account security check on the selected account. When the security check is successful, the password manager autofills the login password input field with login data associated with the selected account.