Unified authorization method and system adaptive to multiple third-party platforms

Abstract

The invention relates to the field of computer software information system development, and particularly provides a unified authorization method and system adaptive to a plurality of third-party platforms, and the method comprises the following steps: S1, a user enters a service system through the third-party platforms, and at the moment, the user will be redirected to a unified authorization connector for authentication; s2, the unified authorization connector inquires whether a binding relationship exists between the account information of the user on the third-party platform and the account information of the user on the business system through the acquired account information of the user on the third-party platform; s3, the service system calls an interface verification token provided by the unified authorization connector to verify whether the token is valid or not, and if yes, a session is automatically created and a related page of the service system is entered; s4, the user authenticates whether the account information of the service system is correct by interacting with the service system; and S5, creating a token, and returning the token to the service system. Compared with the prior art, the method can meet individual requirements of tobacco business systems in various regions, and is high in reusability and convenient to implement and popularize.

Description

Technical Field

[0001] The present invention relates to the field of computer software information system development, and specifically provides a unified authorization method and system adapted to multiple third-party platforms. Background Art

[0002] Since its inception, WeChat has rapidly gained widespread popularity thanks to its massive user base and ease of use. The launch of the WeChat Official Account platform has further fueled its widespread adoption within the corporate world. However, the tobacco industry, with its diverse business scenarios and significant regional differences, often requires multiple related business systems to interface with WeChat.

[0003] In today's multi-platform, multi-terminal internet environment, these business systems aren't limited to connecting with WeChat; they may also involve multiple third-party platforms like DingTalk. Faced with such a multitude of platform integration requirements, developing separate authorization login interfaces for each platform would undoubtedly significantly increase development and maintenance costs. Summary of the Invention

[0004] The present invention aims to address the deficiencies of the above-mentioned prior art and provides a highly practical unified authorization method that is adaptable to multiple third-party platforms.

[0005] A further technical task of the present invention is to provide a unified authorization system that is rationally designed, safe and applicable and adaptable to multiple third-party platforms.

[0006] The technical solution adopted by the present invention to solve its technical problem is:

[0007] A unified authorization method adapted to multiple third-party platforms has the following steps:

[0008] S1. The user enters the business system through a third-party platform and is redirected to the unified authorization connector for authentication.

[0009] S2. The unified authorization connector queries the user's account information on the third-party platform to determine whether there is a binding relationship between the user's account information on the third-party platform and the account information in the business system;

[0010] S3. The business system calls the interface provided by the unified authorization connector to verify whether the token is valid. If it is valid, it automatically creates a session and enters the relevant page of the business system;

[0011] S4. The user interacts with the business system to verify whether the business system account information is correct;

[0012] S5. Create a token and return it to the business system.

[0013] Furthermore, in step S1, the unified authorization connector interacts with the third-party platform to obtain authorization from the third-party platform and obtains a code, and connects with the third-party platform according to the code to obtain the user's account information on the third-party platform.

[0014] Furthermore, in step S2, it is determined whether a binding relationship exists. If so, a token is returned and the user is redirected to the business system to proceed to step S3. Otherwise, the user is redirected to the login page of the business system on the third-party platform to proceed to steps S4 and S5.

[0015] Furthermore, in step S3, the unified authorization connector completes the management of the authorization process for the business system to connect to the third-party platform. The enterprise only needs to provide the unique identification code appcode of the business system and the interface address for verifying the validity of the token, that is, to achieve the connection between multiple business systems and the third-party platform through the unified authorization connector.

[0016] Furthermore, in step S4, the user enters the account number, password and verification code information on the login page of the business system on the third-party platform, and authenticates whether the business system account information is correct by interacting with the business system. If the authentication is correct, the unified authorization connector is redirected.

[0017] Furthermore, in step S5, the unified authorization connector binds the user's account information on the third-party platform with the account information in the business system, creates a token, and returns the token to the business system to proceed to step S3.

[0018] A unified authorization system adapted to multiple third-party platforms. First, a user enters the business system through a third-party platform and is redirected to a unified authorization connector for authentication. The unified authorization connector uses the user's account information obtained on the third-party platform to query whether the user's account information on the third-party platform is bound to the account information in the business system.

[0019] The business system calls the interface provided by the unified authorization connector to verify whether the token is valid. If it is valid, it will create a session and enter the relevant page of the business system. The user interacts with the business system to verify whether the business system account information is correct, create a token, and return the token to the business system.

[0020] Furthermore, the unified authorization connector interacts with the third-party platform to obtain authorization from the third-party platform and obtain a code, and connects with the third-party platform according to the code to obtain the user's account information on the third-party platform.

[0021] When determining whether a binding relationship exists, if so, a token is returned and the system is redirected to the business system to perform step S3; otherwise, the system is redirected to the login page of the business system under the third-party platform to perform steps S4 and S5.

[0022] Furthermore, after entering the relevant page of the business system, the unified authorization connector has completed the management of the authorization process of the business system docking with the third-party platform. The enterprise only needs to provide the unique identification code appcode of the business system and the interface address for verifying the validity of the token, that is, to achieve the docking of multiple business systems with the third-party platform through the unified authorization connector.

[0023] Furthermore, the user enters the account number, password, and verification code information on the login page of the business system on the third-party platform, and verifies whether the business system account information is correct by interacting with the business system. If the verification is correct, the unified authorization connector is redirected;

[0024] The unified authorization connector binds the user's account information on the third-party platform with the account information in the business system, creates a token, and returns the token to the business system.

[0025] Compared with the prior art, the unified authorization method and system adapted to multiple third-party platforms of the present invention has the following outstanding beneficial effects:

[0026] The present invention manages the authorization processes of different third-party platforms in a unified manner through a unified interface, thereby simplifying the development process and improving authorization efficiency. It can meet the individual needs of tobacco business systems in various regions, has high reusability, and is easy to implement and promote. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0028] Figure 1 It is a flowchart of a unified authorization method adapted to multiple third-party platforms. DETAILED DESCRIPTION

[0029] In order to enable those skilled in the art to better understand the solutions of the present invention, the present invention will be further described in detail below in conjunction with specific embodiments. Obviously, the embodiments described are only some embodiments of the present invention, rather than all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0030] A best embodiment is given below:

[0031] like Figure 1As shown, a unified authorization method adapted to multiple third-party platforms in this embodiment includes the following steps:

[0032] S1. The user enters the business system through a third-party platform and is redirected to the unified authorization connector for authentication.

[0033] The unified authorization connector interacts with the third-party platform to obtain authorization from the third-party platform and obtain the code, and connects with the third-party platform based on the code to obtain the user's account information on the third-party platform.

[0034] S2. The unified authorization connector uses the obtained user account information on the third-party platform to query whether there is a binding relationship between the user account information on the third-party platform and the account information in the business system;

[0035] If it exists, the token is returned and the user is redirected to the business system to proceed to step S3. Otherwise, the user is redirected to the login page of the business system on the third-party platform to proceed to steps S4 and S5.

[0036] S3. The business system calls the interface provided by the unified authorization connector to verify whether the token is valid. If it is valid, it automatically creates a session and enters the relevant page of the business system;

[0037] The unified authorization connector now manages the authorization process for connecting business systems to third-party platforms. Enterprises only need to provide the business system's unique identification code (appcode) and the interface address for verifying token validity. This allows the unified authorization connector to easily connect multiple business systems to third-party platforms, eliminating the tedious process of developing multiple authorization interfaces. Furthermore, due to the connector's high flexibility and adaptability to various third-party platforms, enterprises can quickly and conveniently integrate their business systems into different third-party platforms.

[0038] S4. The user interacts with the business system to verify whether the business system account information is correct;

[0039] The user enters their account number, password, verification code, and other information on the login page of the business system on the third-party platform. The system then interacts with the user to verify that the account information is correct. If the verification is correct, the user is redirected to the unified authorization connector.

[0040] S5. Create a token and return it to the business system;

[0041] The unified authorization connector binds the user's account information on the third-party platform with the account information in the business system, creates a token, and returns the token to the business system to proceed to step S3.

[0042] Based on the above method, in this embodiment, a unified authorization system adapted to multiple third-party platforms is provided. First, a user enters the business system through a third-party platform and is redirected to a unified authorization connector for authentication. The unified authorization connector uses the user's account information obtained on the third-party platform to query whether there is a binding relationship between the user's account information on the third-party platform and the account information in the business system.

[0043] The business system calls the interface provided by the unified authorization connector to verify whether the token is valid. If it is valid, it will create a session and enter the relevant page of the business system. The user interacts with the business system to verify whether the business system account information is correct, create a token, and return the token to the business system.

[0044] Among them, the unified authorization connector interacts with the third-party platform to obtain authorization from the third-party platform and obtain the code, and connects with the third-party platform according to the code to obtain the user's account information on the third-party platform.

[0045] When determining whether a binding relationship exists, if so, a token is returned and the system is redirected to the business system to perform step S3; otherwise, the system is redirected to the login page of the business system under the third-party platform to perform steps S4 and S5.

[0046] After entering the relevant page of the business system, the unified authorization connector has completed the management of the authorization process for the business system to connect to the third-party platform. The enterprise only needs to provide the unique identification code appcode of the business system and the interface address for verifying the validity of the token, that is, to achieve the connection between multiple business systems and third-party platforms through the unified authorization connector.

[0047] The user enters the account number, password, and verification code information on the login page of the business system on the third-party platform, and verifies whether the business system account information is correct by interacting with the business system. If the verification is correct, the unified authorization connector is redirected;

[0048] The unified authorization connector binds the user's account information on the third-party platform with the account information in the business system, creates a token, and returns the token to the business system.

[0049] The above-mentioned specific implementation methods are only specific cases of the present invention. The patent protection scope of the present invention includes but is not limited to the above-mentioned specific implementation methods. Any technical solutions that conform to the above-mentioned specific implementation methods of the present invention and any appropriate changes or substitutions made thereto by ordinary technicians in the relevant technical field shall fall within the patent protection scope of the present invention.

[0050] While embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions, and variations may be made to these embodiments without departing from the principles and spirit of the invention, and that the scope of the invention is defined by the appended claims and their equivalents.

Claims

1. A unified authorization method adapted to multiple third-party platforms, characterized in that: The steps are as follows: S1. The user enters the business system through a third-party platform and is redirected to the unified authorization connector for authentication. S2. The unified authorization connector queries the user's account information on the third-party platform to determine whether there is a binding relationship between the user's account information on the third-party platform and the account information in the business system; S3. The business system calls the interface provided by the unified authorization connector to verify whether the token is valid. If it is valid, it automatically creates a session and enters the relevant page of the business system; S4. The user interacts with the business system to verify whether the business system account information is correct; S5. Create a token and return it to the business system.

2. A unified authorization method adapted to multiple third-party platforms according to claim 1, characterized in that: In step S1, the unified authorization connector interacts with the third-party platform to obtain authorization from the third-party platform and obtain a code, and connects with the third-party platform according to the code to obtain the user's account information on the third-party platform.

3. A unified authorization method adapted to multiple third-party platforms according to claim 2, characterized in that: In step S2, it is determined whether a binding relationship exists. If so, a token is returned and the system is redirected to the business system to proceed to step S3. Otherwise, the system is redirected to the login page of the business system under the third-party platform to proceed to steps S4 and S5.

4. A unified authorization method adapted to multiple third-party platforms according to claim 3, characterized in that: In step S3, the unified authorization connector completes the management of the authorization process for the business system to connect to the third-party platform. The enterprise only needs to provide the unique identification code appcode of the business system and the interface address for verifying the validity of the token, that is, the connection between multiple business systems and third-party platforms is achieved through the unified authorization connector.

5. A unified authorization method adapted to multiple third-party platforms according to claim 4, characterized in that: In step S4, the user enters the account number, password and verification code information on the login page of the business system on the third-party platform, and verifies whether the business system account information is correct by interacting with the business system. If the verification is correct, the unified authorization connector is redirected.

6. A unified authorization method adapted to multiple third-party platforms according to claim 5, characterized in that: In step S5, the unified authorization connector binds the user's account information on the third-party platform with the account information in the business system, creates a token, and returns the token to the business system to proceed to step S3.

7. A unified authorization system adapted to multiple third-party platforms, characterized in that: First, the user enters the business system through the third-party platform. At this time, the user will be redirected to the unified authorization connector for authentication. The unified authorization connector uses the user's account information on the third-party platform to query whether the user's account information on the third-party platform is bound to the account information in the business system. The business system calls the interface provided by the unified authorization connector to verify whether the token is valid. If it is valid, it will create a session and enter the relevant page of the business system. The user interacts with the business system to verify whether the business system account information is correct, create a token, and return the token to the business system.

8. A unified authorization system adapted to multiple third-party platforms according to claim 7, characterized in that: The unified authorization connector interacts with the third-party platform to obtain authorization from the third-party platform and obtains the code, and connects with the third-party platform according to the code to obtain the user's account information on the third-party platform. When determining whether a binding relationship exists, if so, a token is returned and the system is redirected to the business system to perform step S3; otherwise, the system is redirected to the login page of the business system under the third-party platform to perform steps S4 and S5.

9. A unified authorization system adapted to multiple third-party platforms according to claim 8, characterized in that: After entering the relevant page of the business system, the unified authorization connector has completed the management of the authorization process for the business system to connect to the third-party platform. The enterprise only needs to provide the unique identification code appcode of the business system and the interface address for verifying the validity of the token, that is, to achieve the connection between multiple business systems and third-party platforms through the unified authorization connector.

10. A unified authorization system adapted to multiple third-party platforms according to claim 9, characterized in that: The user enters their account, password, and verification code on the login page of the business system on the third-party platform, and interacts with the business system to verify whether the account information is correct. If the authentication is correct, the unified authorization connector is redirected; The unified authorization connector binds the user's account information on the third-party platform with the account information in the business system, creates a token, and returns the token to the business system.

Images