Bidirectional Authorization Plug-in for Cross-App Login
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Open Authorization (OAUTH) protocol for network authorization is limited by unidirectional authorization relationships, which become complex and inflexible as the number of applications increases, failing to meet user requirements for flexible use of multiple application accounts.
Innovation Solution
An authorized-login implementation method and device that uses authorization plug-ins bound to application clients and an authorization service platform to facilitate bidirectional authorization, allowing applications to request and obtain login credentials for each other through an authorized-login code, enabling flexible and abundant authorization relationships.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If unidirectional authorization relationships are used in OAUTH protocol, then security is improved by preventing consumer from accessing user account information, but authorization flexibility deteriorates as number of applications increases
Solution Approach 1:
The patent inverts the traditional OAUTH unidirectional authorization model by enabling bidirectional authorization where consumer applications can also act as service providers. This allows applications to mutually authorize each other, creating flexible authorization relationships while maintaining security through the same token-based mechanism.
Solution Approach 2:
The patent makes applications universal by enabling them to function both as consumers and service providers. The same application can initiate authorization requests and also receive authorization requests from other applications, eliminating the need for separate licensing interfaces and enabling complex cross-licensing relationships.
2Adaptability or versatility
If separate licensing program interfaces are developed for each application, then authorization relationships can be established, but device complexity increases
Solution Approach 1:
The patent eliminates the need for separate licensing interfaces by making the authorization plug-in universal. The same plug-in architecture handles both initiating and receiving authorization requests, simplifying the system while maintaining full authorization capability across all applications.
Solution Approach 2:
The patent merges the separate licensing interfaces into a single unified authorization plug-in system. By combining the consumer and service provider interfaces into one universal plug-in, the system reduces complexity while maintaining the ability to establish complex authorization relationships.
3Reliability
If traditional OAUTH protocol is used for cross-application login, then security is maintained, but user convenience deteriorates due to inability to use single account across multiple applications
Solution Approach 1:
The patent enables a single application account to be used across multiple applications by making the authorization relationship bidirectional. The account holder can authorize other applications to access their account, and those applications can subsequently be used to log in to the original application, providing convenience while maintaining security.
Solution Approach 2:
The patent inverts the traditional login flow by allowing users to log in to application B using application A's account, and then use application B to log in to application A. This bidirectional capability provides greater user convenience while maintaining the same security level through token-based authentication.
Data Source
AI summary
Provided are an authorized-login implementation method and device, an apparatus, a system, a platform and a storage medium. The method includes: receiving, by a first authorization plug-in bound to a first application client, an authorized-login request from a second authorization plug-in bound to a second application client, where the authorized-login request is used for a second application to request login by using a first application account; requesting, by the first authorization plug-in, to acquire an authorized-login code from an authorization service platform through authorization information about the first application account; and feeding back, by the first authorization plug-in, the authorized-login code to the second authorization plug-in, so as to instruct the second authorization plug-in to request to acquire a second application account from the authorization service platform according to the authorized-login code, where the second application account is used for accessing a user resource of the first application account.


