Application Lock Account ID Replacement for Multi-Account Encryption
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current application locks can only encrypt applications running under the main account, limiting their applicability and security, as they cannot access or encrypt applications associated with child accounts or 'double accounts' without proper authentication.
Innovation Solution
The method involves replacing the system account ID with the main account ID in foreground running requests, determining the appropriate encryption algorithm, and encrypting applications based on the main account's credentials, while also allowing decryption with a valid password and updating encryption instructions based on application state changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the application lock only reads the resource file corresponding to the main account, then the security of the main account's applications is ensured, but the applicability is limited as it cannot encrypt applications of child accounts or double accounts
Solution Approach 1:
The application lock is enhanced to support multiple account types (main account, child accounts, and double accounts) by detecting the current logged-in account and dynamically selecting the corresponding resource file for encryption operations, making the encryption mechanism universally applicable across different account scenarios while maintaining security through account-specific resource file access
2Ease of operation
If the system detects and replaces the system account ID with the main account ID, then the application lock can access the correct resource file for encryption, but additional detection and replacement operations increase system complexity
Solution Approach 1:
The system performs preliminary detection of the current logged-in account and pre-replaces the system account ID with the appropriate account ID (main account or double account) before the encryption operation is initiated. This preliminary action ensures that when the application lock requests encryption, the correct resource file is already identified and accessible, simplifying the encryption operation itself while handling the complexity upfront in the account detection and ID replacement process
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present disclosure relates to a method and a device for encrypting an application, belonging to a field of computer technology. The method includes: receiving a foreground running request sent by the application, in which the foreground running request includes a system account ID of a system account logged in a system currently; detecting whether the system account ID satisfies a preset replacing condition; replacing the system account ID with a main account ID of the system if the system account ID satisfies the preset replacing condition; and determining an encryption algorithm for the application in the system the main account logged in, and encrypting the application according to the encryption algorithm.