Cross-Platform Authentication via Disposable Verification Codes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing user authentication methods for cross-platform access are cumbersome, particularly when users forget passwords or prefer not to disclose credentials in group settings, leading to frustrating and time-consuming login processes.
Innovation Solution
A system and method for expediting user authentication using an automated process that involves a computing platform with a user database and biometric profiles, where a verification device sends a validation code to an access device, allowing users to log in without remembering passwords, and enabling secure access across different devices without requiring password entry.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional password-based authentication is used, then user account security is ensured, but the login process becomes time-consuming and frustrating when users forget passwords or need to access from multiple devices
Solution Approach 1:
The system performs preliminary authentication by sending a verification code to the user's registered email address before the actual login process. This pre-authentication step verifies the user's identity in advance, eliminating the need for password entry during the login process and significantly reducing login time while maintaining security.
Solution Approach 2:
The patent introduces an intermediary verification code system that mediates between the user and the authentication system. Instead of directly using passwords, the system uses a temporary verification code sent to the user's email as an intermediate authentication mechanism, which simplifies the login process while maintaining security requirements.
2Reliability
If password-based authentication is required, then account security is maintained, but users cannot conveniently share access in group settings without disclosing credentials
Solution Approach 1:
The verification code serves as an intermediary that allows temporary access sharing without exposing permanent credentials. The code can be shared with group members for collaborative access, and once used, it becomes invalid, ensuring that sensitive authentication information is never disclosed or reused.
Solution Approach 2:
The authentication system uses disposable verification codes that are valid for only one use and a limited time period. These single-use codes can be safely shared among group members without compromising long-term account security, as they become invalid after use or expiration.
3Adaptability or versatility
If cross-platform authentication is enabled, then accessibility to content is improved, but the complexity of authentication mechanisms increases
Solution Approach 1:
The email-based verification system serves as a universal authentication mechanism that works across all platforms and devices. Instead of implementing platform-specific authentication methods, the system uses a single universal approach (email verification) that functions consistently across smartphones, tablets, laptops, and other devices, simplifying the overall authentication architecture.
Data Source
AI summary
A system for granting access to an account at an access device includes a computer server having a hardware processor and a memory storing a software code. The hardware processor executes the software code to receive a login request from the access device through a first communications socket, open a second communications socket between the access device and the computer server, transmit a verification request message including a required call-to-action to a verification device through a third communications socket, and receive a verification response message verifying that the required call-to-action has been completed at the verification device. Upon receiving the verification response message, the software code sends an access token for accessing the account to the access device through the second communications socket, receives the access token from the access device, and grants the access device access to the account.