Sub-Application Authorization Locks for Post-Deployment Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current application authorization locking methods only apply to the entire application, failing to manage authorization locks for multiple sub-applications within a whole application, and are inconvenient for developers to adjust after deployment.
Innovation Solution
Implement independent authorization locks for each sub-application, allowing the application store to package and distribute separate authorization keys for both the main and sub-applications, ensuring flexibility and stability without affecting service logic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a whole application has only one authorization lock, then the authorization management is simple, but it cannot implement authorization locking for multiple sub-applications within the whole application
Solution Approach 1:
The patent divides the authorization lock into multiple independent sub-authorization locks, each corresponding to a specific sub-application within the whole application. This segmentation allows each sub-application to have its own authorization control, enabling the system to handle complex multi-subapplication scenarios while maintaining manageable complexity through modular design
2Ease of operation
If authorization locking is performed on the entire application, then the authorization management is unified, but it is inconvenient for developers to adjust authorization locks after deployment
Solution Approach 1:
By segmenting the authorization lock into independent sub-authorization locks for each sub-application, the system enables granular control where developers can adjust individual sub-authorization locks after deployment without affecting the entire application or other sub-applications, significantly improving operational convenience
Solution Approach 2:
The patent implements dynamic authorization management where sub-authorization locks can be independently configured, adjusted, or modified after the application is deployed. This dynamic capability allows the authorization system to adapt to changing requirements without requiring re-deployment of the entire application
3Adaptability or versatility
If separate authorization locks are implemented for each sub-application, then authorization management flexibility is improved, but the system complexity increases
Solution Approach 1:
The patent applies segmentation by creating independent sub-authorization locks for each sub-application, which provides the necessary flexibility for separate authorization management. The complexity is managed through a structured approach where each sub-authorization lock is an independent unit that can be configured and controlled separately
Data Source
AI summary
The present disclosure relates to an application authorization management method, that includes: receiving an authorization request that is used to request an authorization permission of a second application downloaded from an application store, where the second application has an association relationship with a first application, and the second application is able to call the first application to implement a function of the first application; and in response to the authorization request, sending a first key and a second key; where the first application has a first authorization lock that is used to perform authorization locking on the first application, the second application has a second authorization lock that is used to perform the authorization locking on the second application, and the first key and the second key are used to release the authorization locking on the first application and the authorization locking on the second application, respectively.