Identity Authentication via Confirmation Device Binding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current identity authentication methods, such as two-factor authentication, face challenges in balancing security and user experience, often resulting in high security risks and poor user experience, especially in insecure environments where password leakage and misrepresentation are concerns.
Innovation Solution
A system and method for identity authentication that involves a front-end device and a confirmation device, where the authentication system determines the confirmation device associated with the front-end device based on account information, sends an authentication request, and receives confirmation information to authenticate the login request, allowing users to perform a simple confirmation operation without inputting passwords, thereby enhancing security and reducing user login time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If password+token code login is used, then authentication security is improved, but password leakage risk increases in insecure environments
Solution Approach 1:
The patent extracts the password input step from the authentication process. Instead of requiring users to input passwords, the system uses account information (such as phone number) that is already bound to the user's confirmation device. This removes the vulnerable环节 of password transmission and input, thereby eliminating password leakage risks while maintaining authentication security.
Solution Approach 2:
The patent introduces a confirmation device (such as a mobile phone) as an intermediary between the user and the authentication system. The confirmation device receives authentication requests, displays them to the user, and sends confirmation information back to the server. This intermediary mechanism allows secure authentication without exposing passwords, as the confirmation device acts as a secure channel for verifying user identity.
2Reliability
If public key login or USB card login is used, then authentication security is improved, but ease of operation deteriorates due to complex setup and device requirements
Solution Approach 1:
The patent makes the confirmation device (mobile phone) serve multiple functions: it acts as both a communication device for receiving authentication requests and as the authentication tool itself. Users leverage their existing mobile phones without needing separate authentication devices like USB cards or complex key management systems. This universal approach simplifies operations while maintaining security through the mobile network's inherent reliability.
Solution Approach 2:
The system allows users to bind their own confirmation devices to their accounts through simple self-service operations. Once bound, the confirmation device automatically receives and processes authentication requests without requiring users to manually configure complex security settings or manage cryptographic keys. This self-service mechanism greatly improves ease of operation while maintaining robust authentication security.
3Reliability
If traditional authentication methods are used, then security is improved, but user login time increases due to multiple input steps
Solution Approach 1:
The patent requires users to pre-bind their confirmation devices to their accounts during registration or account setup. This preliminary action ensures that the confirmation device is already associated with the user's identity before authentication is needed. During actual login, users only need to receive and confirm the authentication request on their pre-bound device, eliminating the need for multiple input steps and significantly reducing login time while maintaining security.
Data Source
AI summary
Embodiments of the present application relate to a method, device, and system for processing data. The method includes receiving a login request from a front-end device, the login request comprising account information of an account associated with the front-end device, determining a confirmation device associated with the front-end device based at least in part on the account information, generating an authentication request based at least in part on the account information, wherein said authentication request comprises said account information, obtaining confirmation information from the confirmation device, the confirmation information being generated based at least in part on the authentication request and confirming the login request, and authenticating, by the authentication system, the front-end device based at least in part on the confirmation information.