Third-Party App Authorization via Token Exchange for Resource Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing authorization authentication systems only omit the registering operation, preventing the continuous use of accumulated resources or information from one service provider by a third-party application.
Innovation Solution
A method involving a third-party application client, user client, and platform server, where an authorization request is sent with an application ID, resulting in an authorization code and token exchange, allowing the third-party application client to interact with the platform server for user information and resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If service provider A authorizes service provider B to use registered user name and password, then the user can log on to service provider B without registration, but other accumulated resources or information of the user for service provider A cannot be used by service provider B continuously
Solution Approach 1:
The patent introduces an authorization code and token as intermediary elements between the user's first account (service provider A) and the second account (service provider B). The authorization code is generated by service provider A's server and transmitted to service provider B's server, which then issues a token. This token enables service provider B to continuously access and use the user's accumulated resources and information from service provider A, resolving the limitation where only basic login was possible without resource continuity.
2Adaptability or versatility
If multiple service providers are used, then the user can access various services, but the user has to perform multiple registering procedures
Solution Approach 1:
The patent implements preliminary authorization action where the user performs a one-time authorization of service provider B to access service provider A's account information. The server generates an authorization code in advance that enables future access without requiring repeated registration procedures. This preliminary action establishes a continuous access mechanism that eliminates the need for multiple registration procedures across different service providers.
Data Source
AI summary
A third-party application client performs authorization authentication with a user client and a platform server. The third party application obtains an access token and an open ID. The third-party application client interacts with the platform server for information related to the user ID by using the token, calls the user client or is called by the user client according to the open ID. The third-party application client may interact with the platform server for the information related to the user ID by using the token, so that other resources or information of the user accumulated for the platform server can be used by the third-party application client continuously.


