Passwordless Account Access via Dual-Token Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing process of setting up a user account for web-based services is cumbersome, deterring users due to the time-consuming registration process, which includes choosing a username and password, providing personal information, and downloading software, making it a barrier for potential users who do not want to invest the time.
Innovation Solution
A method that allows users to create a new user account without a password by using a client application that generates two tokens, a client device token and an email token, which must be possessed by the user to access the account, providing passwordless access while maintaining security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a traditional user account registration process is implemented (requiring username, password, personal information), then account security is improved, but user convenience and registration speed deteriorate
Solution Approach 1:
The patent extracts the password component from the traditional authentication system and replaces it with device-based tokens. The authentication process is divided into device-specific tokens (stored on the device) and email verification tokens, eliminating the need for users to create and remember passwords while maintaining security through multi-factor authentication.
Solution Approach 2:
The patent introduces an intermediary email verification process between device registration and account access. The email token serves as a mediator that confirms user identity without requiring password creation, bridging the gap between convenient device-based access and secure identity verification.
2Reliability
If a traditional user account registration process is implemented (requiring username, password, personal information), then account security is improved, but ease of operation deteriorates
Solution Approach 1:
The patent removes the password creation step from the account registration process, extracting this burden from the user experience. Security is maintained through device tokens and email verification, while ease of operation is significantly improved by eliminating the need for users to choose and remember complex passwords.
Solution Approach 2:
The system performs automatic device verification and token generation without requiring user intervention for password creation. The email verification process is automated, and the system self-manages the authentication token distribution, reducing the operational burden on users while maintaining security.
3Adaptability or versatility
If password-based authentication is used, then universal account access is improved, but security against unauthorized access deteriorates
Solution Approach 1:
The patent segments the authentication process into multiple independent components: device-specific tokens, email verification tokens, and server-validated credentials. This segmentation provides both universal access (through email verification) and enhanced security (through device-specific authentication), eliminating the trade-off between accessibility and protection.
Solution Approach 2:
The patent implements different authentication qualities for different access scenarios. Device-specific tokens provide high-security local access for registered devices, while email verification provides universal access for new or unrecognized devices. This local quality differentiation allows the system to adapt security levels to specific access contexts.
Data Source
Figure 1A~1B
Figure 1C~1D
Figure 2~3A
AI summary
Various embodiments of the present technology enable users to sign in to an account without a password. For example, when receiving a request to register a device with an account, a user can be prompted to enter their email address. In response, two tokens are generated. A first token is sent to the a client application on the device and the second token is sent to the user's email. The user can then only login to their account with the device if the device has both tokens. Thus, if someone intercepts the email, they will be unable to login from another device since they don't have the first token. If the client token and email token cannot be automatically joined on the same device, a web page showing a code can be displayed on a first device, which can be entered on the second device to finish login process.