Application Download Authentication With Instance-Level Identity Checks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing authentication methods for application downloads lack the ability to verify that the user requesting the download is the authorized person, especially in cases of device theft or account takeovers, leading to potential fraud and security breaches.
Innovation Solution
A system that assigns a unique identifier to each application instance, requiring additional authentication information such as government-issued ID verification and biometrics to ensure the user's identity, and manages devices using these identifiers to track and authorize application downloads.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional username/password authentication is used for application downloads, then the authentication process is simple and fast, but the security is weak and vulnerable to stolen credentials
Solution Approach 1:
The system performs preliminary actions by assigning a unique identifier to the application instance before the download completes, and by pre-establishing the requirement for additional authentication information. This ensures that when the download occurs, the unique identifier is already in place to enable subsequent verification that the user is authorized, thereby improving security without requiring complex real-time verification processes during the actual download.
Solution Approach 2:
The patent introduces an intermediary authentication mechanism that sits between the simple username/password verification and the actual application access. This intermediary layer requires additional authentication information and uses the unique identifier to verify user authorization, thereby strengthening security without completely redesigning the authentication process.
2Reliability
If additional authentication information and unique identifiers are required for each application instance, then user authorization verification is improved, but the device complexity and authentication overhead increase
Solution Approach 1:
The authentication system is segmented into distinct components: a unique identifier assignment module, an additional authentication information verification module, and a user authorization verification module. This segmentation allows each component to perform its specific function independently, making the overall system more manageable and easier to implement while maintaining strong authorization verification.
Solution Approach 2:
The system creates a copy of the authentication process for each application instance by assigning a unique identifier. This allows the same authentication logic to be reused across multiple instances without requiring duplicate verification processes, thereby reducing overall system complexity while maintaining verification reliability.
3Reliability
If real-time verification and tracking of application instances is implemented, then account takeover prevention is improved, but the time required for authentication increases
Solution Approach 1:
The system performs the time-consuming unique identifier assignment and authentication information verification as preliminary actions before the actual authentication checkpoint. This allows the critical verification to occur in advance, reducing the time required at the actual authentication moment while maintaining strong account takeover prevention.
Solution Approach 2:
The system implements feedback mechanisms where the unique identifier and authentication verification results are fed back into the authentication process. This allows for efficient verification and reduces the need for repeated authentication attempts, thereby reducing overall authentication time while maintaining high security standards.
Data Source
AI summary
Embodiments described herein disclose technology for verifying authorization of an application download. The system can receive from a device associated with a user, a request to download an application. In response to a first instance of the application being downloaded on the device, the system can assign a unique identifier to the first instance of the application. After the application is downloaded and prior to granting the person requesting the application download access to the first instance of the application, the system can request via the first instance of the application identification information and particular authentication information to verify that the person requesting the application download is authorized to do so. In response to verifying that the person requesting the application download is authorized, the unique identifier can be associated with the account, user and/or device to result in a verified download of the first instance of the application.