WO2021098241A1 - 授权方法、辅助授权组件、管理服务器和计算机可读介质 - Google Patents
授权方法、辅助授权组件、管理服务器和计算机可读介质 Download PDFInfo
- Publication number
- WO2021098241A1 WO2021098241A1 PCT/CN2020/101795 CN2020101795W WO2021098241A1 WO 2021098241 A1 WO2021098241 A1 WO 2021098241A1 CN 2020101795 W CN2020101795 W CN 2020101795W WO 2021098241 A1 WO2021098241 A1 WO 2021098241A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- authorization
- login
- open source
- source host
- auxiliary
- Prior art date
Links
- 238000013475 authorization Methods 0.000 title claims abstract description 371
- 238000000034 method Methods 0.000 title claims abstract description 64
- 230000004044 response Effects 0.000 claims abstract description 32
- 238000012795 verification Methods 0.000 claims abstract description 12
- 238000004590 computer program Methods 0.000 claims description 3
- 238000007726 management method Methods 0.000 description 72
- 238000011161 development Methods 0.000 description 14
- 238000010586 diagram Methods 0.000 description 10
- 238000005516 engineering process Methods 0.000 description 6
- 230000003993 interaction Effects 0.000 description 6
- 230000011664 signaling Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000004888 barrier function Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000001568 sexual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/101—Access control lists [ACL]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
- H04L63/062—Network architectures or network communication protocols for network security for supporting key management in a packet data network for key distribution, e.g. centrally by trusted party
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
Definitions
- the present disclosure relates to the field of computer technology, and can be used in the field of cloud platform technology, and in particular to an authorization method, an auxiliary authorization component, a management server, and a computer-readable medium.
- developer applications for example, smart applets
- developer applications can be developed at one time and run on multiple terminals, that is, developer applications can support cross-platform operation.
- developer applications can support cross-platform operation.
- platforms use different account management systems, when a developer application runs across platforms, a new host platform is required to authorize user information. For this reason, if you want to truly realize the cross-platform operation of developer applications, you need to solve the problem of cross-platform authorization.
- the embodiments of the present disclosure provide an authorization method, an auxiliary authorization component, a management server, and a computer-readable medium.
- embodiments of the present disclosure provide an authorization method, wherein the authorization method is applied to an auxiliary authorization component, the auxiliary authorization component is integrated in an open source host application, and the authorization method includes:
- authorization success information includes: an authorization code
- the authorization code is sent to the developer application, so that the developer application exchanges the session key corresponding to the authorization code to the management server.
- the method further includes:
- the login request includes: the host identifier of the open source host application
- the method further includes:
- the account manager of the open source host application is determined according to the host identifier.
- the account management party includes: the management server or the open source host platform in the open source host application.
- embodiments of the present disclosure also provide an authorization method, wherein the authorization method is applied to a management server, and the authorization method includes:
- the session key is fed back to the developer application.
- the step of obtaining the corresponding session key according to the authorization code in the key obtaining request includes:
- the key acquisition request is forwarded to the third-party open source host platform for the third-party open source host platform to generate the session secret corresponding to the authorization code key;
- the method before the step of receiving the key acquisition request sent by the developer application, the method further includes:
- the authorization success information is fed back to the auxiliary authorization component, and the authorization success information includes the authorization code.
- the method further includes:
- the encrypted user information is fed back to the auxiliary authorization component.
- embodiments of the present disclosure also provide an auxiliary authorization component, wherein the auxiliary authorization component is integrated in an open source host application, and the auxiliary authorization component includes:
- the first obtaining module is configured to obtain login authorization information of the user in response to the login request sent by the developer application;
- the first sending module is configured to send a login authorization request to the account manager of the open source host application, where the login authorization request includes: the login authorization information;
- the first receiving module is configured to receive the authorization success information fed back by the account manager after the login authorization information is verified, where the authorization success information includes: an authorization code;
- the second sending module is configured to send the authorization code to the developer application for the developer application to exchange the session key corresponding to the authorization code to the management server.
- the auxiliary authorization component further includes:
- the third sending module is configured to forward the user information acquisition request to the account manager in response to the user information acquisition request sent by the developer application;
- the second receiving module is configured to receive the encrypted user information fed back by the account manager, and forward the user information to the developer application, so that the developer application can exchange information based on the session key. Decrypt the user information.
- the login request includes: the host identifier of the open source host application
- the auxiliary authorization component further includes:
- the determining module is configured to determine the account manager of the open source host application according to the host identifier.
- the account management party includes: the management server or the open source host platform in the open source host application.
- the embodiments of the present disclosure also provide a management server, which includes:
- the second obtaining module is configured to obtain the corresponding session key according to the authorization code in the key obtaining request in response to the key obtaining request sent by the developer application;
- the fourth sending module is configured to feed back the session key to the developer application.
- the second acquisition module includes:
- the determining unit is configured to determine the account manager of the user corresponding to the authorization code
- a generating unit configured to generate a session key corresponding to the authorization code if the account manager is the management server;
- the sending unit is configured to, if the account management party is a third-party open source host platform, forward the key acquisition request to the third-party open source host platform, so that the third-party open source host platform can generate the authorization code The corresponding session key;
- the receiving unit is configured to receive the session key fed back by the third-party open source host platform.
- the management server further includes:
- the verification module is configured to verify the login authorization information in the login authorization request in response to the login authorization request sent by the auxiliary authorization component;
- the fifth sending module is configured to feed back authorization success information to the auxiliary authorization component after the login authorization information is verified, and the authorization success information includes: the authorization code.
- the management server further includes:
- the third obtaining module is configured to obtain the requested user information in response to the user information obtaining request sent by the auxiliary authorization component;
- An encryption module configured to use the session key to encrypt the user information
- the sixth sending module is configured to feed back the encrypted user information to the auxiliary authorization component.
- embodiments of the present disclosure also provide an authorization system, including: the auxiliary authorization component provided in any embodiment of the third aspect and the management server provided in any embodiment of the fourth aspect.
- the embodiments of the present disclosure also provide a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, it realizes that any one of the embodiments of the first aspect and the second aspect provides the Authorization method.
- the embodiments of the present disclosure provide an authorization method, an auxiliary authorization component, a management server, and a computer-readable medium, which can enable users to authorize part or all of their user information in the open source host application to the developer application to ensure development Cross-platform operation of the app.
- Figure 1 is a schematic diagram of participating parties authorized across platforms in an embodiment of the disclosure
- FIG. 2 is a flowchart of an authorization method provided by an embodiment of the disclosure
- FIG. 3 is a flowchart of another authorization method provided by an embodiment of the disclosure.
- FIG. 4 is a flowchart of another authorization method provided by an embodiment of the disclosure.
- FIG. 5 is a flowchart of yet another authorization method provided by an embodiment of the disclosure.
- Figure 6 is a signaling interaction diagram for implementing an authorization method provided by an embodiment of the disclosure.
- FIG. 7 is a signaling interaction diagram for implementing another authorization method provided by an embodiment of the disclosure.
- FIG. 8 is a structural block diagram of an auxiliary authorization component provided by an embodiment of the disclosure.
- Fig. 9 is a structural block diagram of a management server provided by an embodiment of the disclosure.
- FIG 1 is a schematic diagram of parties involved in cross-platform authorization in an embodiment of the present disclosure.
- participants in the cross-platform authorization process include: developer applications, open source host applications, and management servers.
- developer refers to the developer who develops applications (App, or Mini Program) based on the open source development platform
- developer application refers to the application developed by the developer based on the open source development platform.
- Baidu Smart Mini Programs are completely open and support Baidu applications (Apps) and external App operations (such as , Qu Toutiao, Kuaishou, etc.), to achieve a single development and multi-end operation.
- An "open source host application” is a native application (Native App, also known as a third-party application) that can host the developer application to run, such as the mobile phone Baidu App and the WIFI smart key App.
- the open source host application not only includes an open source host platform supporting the functions of the application, but also integrates auxiliary authorization components. The auxiliary authorization components will be described in detail in the follow-up content.
- the “management server” is the back-end server of the open source development platform. It manages the account system of the open source development platform and can be used for open source host applications to access and register (so that the open source host application integrates auxiliary authorization components and can host development based on the open source development platform Developer applications), you can also manage the account authorization of each open source host application that has completed access registration.
- the management server can also share its own account system for open source host applications that do not have its own independent account system, that is, users can log in to the open source host application based on the account of the open source development platform.
- FIG. 2 is a flowchart of an authorization method provided by an embodiment of the present disclosure. As shown in Figure 2, the authorization method is used to enable users to authorize part or all of their user information in the open source host application to the developer application. .
- the execution subject of the authorization method is an auxiliary authorization component, which is integrated in an open source host application, and the authorization method includes:
- Step S101 In response to the login request sent by the developer application, the user's login authorization information is obtained.
- the same auxiliary authorization components are integrated in different open source host applications.
- the login request sent by the developer application includes the host identifier of the open source host application to be accessed and the authorization items requested by the user (for example, user avatar, user account, user mobile phone number, user business data, etc.).
- the auxiliary authorization component can determine whether the open source host platform to which the user is to log in is an open source host platform that belongs to the same open source host application.
- Step S102 Send a login authorization request to the account manager of the open source host application.
- the method before step S102, further includes the step of determining the account manager of the open source host application according to the host identifier.
- the account system of the open source host application there are two situations for the account system of the open source host application: First, the open source host application uses its own independent account system. At this time, the account manager of the open source host application is the open source host platform in the open source host application. The auxiliary authorization component sends a login authorization request to the open source host platform in the open source host application; second, the open source host application shares the account system of the open source development platform. At this time, the account manager of the open source host application is the management server, and the auxiliary authorization component sends the management The server sends a login authorization request.
- the auxiliary authorization component sends a login authorization request to the account manager of the open source host application for the account manager to verify the login authorization information contained in the login authorization request. Specifically, the account manager verifies whether the login information entered by the user is correct, and verifies whether the user confirms that the authorized authorization items are within the user's authority; if the user enters the login information is correct and confirms that the authorized authorization items are within its authority , It means that the login authorization information is verified, the account manager generates the authorization code, and sends the authorization success information to the auxiliary authorization component, where the authorization success information includes the authorization code, and then step S103 is executed; otherwise, it means that the login authorization information verification fails.
- the account management returns authorization failure information to the auxiliary authorization component, and the auxiliary authorization component displays the authorization failure information to the user.
- the authorization code is the identifier authorized by the user. After the user completes the authorization of the application and the authorization verification is passed, the account manager will generate a valid authorization identifier within a short time (for example, 10 minutes), and the authorization code has a valid number of uses, generally once.
- Step S103 After the login authorization information is verified, the authorization success information fed back by the account manager is received.
- step S103 the auxiliary authorization component receives the authorization success information fed back by the account manager, and the authorization success information contains the authorization code.
- the authorization success information also includes an identifier that characterizes the successful login of the user, which is the user identifier (the field name is generally UId), the open source host identifier (the field name is generally Host_Id), and the current time ( The field name is generally an identifier of a user identity formed by dimensions such as Current_Time.
- Step S104 Send the authorization code to the developer application for the developer application to exchange the session key corresponding to the authorization code to the management server.
- the auxiliary authorization component sends an authorization code (Code) to the developer application, and the developer application sends a key acquisition request to the management server in exchange for the session key (Session Key) corresponding to the authorization code.
- the key acquisition request includes: authorization code, application identification (the application name of the developer application, the field name is generally Client_ID) and the application key (the key of the developer application, the field name is generally Secret_Key).
- the management server determines whether the authorization code is generated by itself or generated by another third-party open source hosting platform.
- the management server verifies the validity of the authorization code, and generates a session key corresponding to the authorization code after the validity verification is passed, and sends back a piece of JSON to the developer application
- the text contains the user ID (the field name is generally openid, which is generated by the developer's application ID AppID and the user ID UId) and the session key (the field name is generally Session_Key); if the validity verification of the authorization code fails, the management server sends The developer application feedbacks another JSON text, which contains the error code (the field name is generally error) and the error description information (the field name is generally error_description).
- the management server forwards the key acquisition request to the open source host platform, and the open source host platform verifies the validity of the authorization code, and generates a certificate after the validity verification is passed.
- the session key corresponding to the authorization code, and a piece of JSON text is fed back to the management server, including the user ID and the session key; if the validity verification of the authorization code fails, the open source host platform will feed back another piece of JSON text to the management server, Contains error code and error description information.
- the management server forwards the received JSON text to the developer application.
- the authorization method provided by the embodiments of the present disclosure can realize the cross-platform authorization of the user to the developer's application.
- Fig. 3 is a flowchart of another authorization method provided by an embodiment of the disclosure. As shown in Fig. 3, unlike the embodiment shown in Fig. 1, the authorization method shown in Fig. 3 not only includes the above-mentioned steps S101 to S104, After step S104, step S105 and step S106 are further included. Only step S105 and step S106 will be described in detail below.
- Step S105 In response to the user information acquisition request sent by the developer application, the user information acquisition request is forwarded to the account manager.
- the developer application sends a user information acquisition request to the auxiliary authorization component.
- the user information acquisition request includes the application ID of the developer application, the user ID of the authorized user, and the user information of the user requested by the developer application (for example, user avatar , User account, user mobile phone number, user business data, etc.).
- the auxiliary authorization component sends the user information acquisition request to the account manager of the open source host application.
- the account manager determines the user information requested by the user information acquisition request from its own database, and uses the user's session key to determine the Encrypted user information, and feedback the encrypted user information to the auxiliary authorization component.
- Step S106 Receive the encrypted user information fed back by the account manager, and forward the user information to the developer application, so that the developer application can decrypt the user information based on the session key.
- the auxiliary authorization component receives the encrypted user information fed back by the account manager and forwards the user information to the developer application.
- the developer application decrypts the received user information based on the previously obtained session key to obtain the user Information in plain text.
- FIG. 4 is a flowchart of another authorization method provided by an embodiment of the disclosure.
- the execution subject of the authorization method is a management server, and the authorization method includes:
- Step S201 In response to receiving the key acquisition request sent by the developer application, acquire the corresponding session key according to the authorization code in the key acquisition request.
- the developer application After the developer application obtains the authorization code, it sends a key acquisition request to the management server.
- the key acquisition request includes the authorization code, application identification, and application key.
- the management server determines whether the authorization code is generated by itself or generated by another third-party open source hosting platform. If the authorization code is generated by the management server itself, the management server obtains the corresponding session key according to the authorization code generated by itself; if the authorization code is generated by another third-party open source hosting platform, the management server forwards the key acquisition request To the open source host platform, the open source host platform generates a session key corresponding to the authorization code, and feeds back the session key to the management server, and the management server receives the session key fed back by the open source host platform of the third party.
- Step S202 Feed back the session key to the developer application.
- the management server After the management server obtains the session key corresponding to the authorization code, it feeds back the session key to the developer application.
- FIG. 5 is a flowchart of another authorization method provided by an embodiment of the present disclosure.
- the open source host application does not have its own independent account system, and uses the account system of the open source development platform, namely The management server shares its own account system for the open source host application.
- the difference from the embodiment shown in FIG. 4 is that the authorization method not only includes the above steps S201 and S202, but also includes steps S200a and S200b before step S201, and includes step S203, step S204, and step S205 after step S202.
- Step S200a in response to the login authorization request sent by the auxiliary authorization component, verify the login authorization information in the login authorization request.
- Step S200b After the login authorization information is verified, the authorization success information is fed back to the auxiliary authorization component, and the authorization success information includes an authorization code.
- Step S201 In response to receiving the key acquisition request sent by the developer application, acquire the corresponding session key according to the authorization code in the key acquisition request.
- Step S202 Feed back the session key to the developer application.
- Step S203 In response to the user information obtaining request sent by the auxiliary authorization component, the requested user information is obtained.
- Step S204 Use the session key to encrypt the user information.
- Step S205 Feed back the encrypted user information to the auxiliary authorization component.
- Fig. 6 is a signaling interaction diagram for implementing an authorization method provided by an embodiment of the present disclosure.
- participants include: developer applications, open source host applications, and management servers; among them, developer applications include: developers The front end of the program and the back end of the developer program.
- the open source host application includes: auxiliary authorization components and open source host platform.
- the open source host application has its own independent account system, that is, the account manager of the open source host application is the open source host platform; the authorization method includes:
- the front end of the developer program sends a login request to the auxiliary authorization component.
- the auxiliary authorization component guides the user to log in and authorize, and obtain the user's login authorization information.
- the auxiliary authorization component sends a login authorization request to the open source host platform, and the login authorization request includes login authorization information.
- the open source host platform After the login authorization information is verified, the open source host platform sends authorization success information to the auxiliary authorization component, and the authorization success information includes the authorization code.
- the auxiliary authorization component forwards the authorization code to the front end of the developer program.
- the front end of the developer program forwards the authorization code to the back end of the developer program.
- the developer program backend sends a key acquisition request to the management server, and the key acquisition request includes an authorization code.
- the management server distributes the authorization code to the open source hosting platform.
- the open source host platform generates the session key corresponding to the authorization code, and sends the session key to the management server.
- the management server forwards the session key to the back end of the developer program.
- the front end of the developer program sends a user information acquisition request to the auxiliary authorization component.
- the auxiliary authorization component forwards the user information acquisition request to the open source host platform.
- the open source host platform feeds back encrypted user information to the auxiliary authorization component.
- the auxiliary authorization component forwards the user information to the front end of the developer program.
- the front end of the developer program forwards user information to the back end of the developer program.
- the developer program backend uses the session key to decrypt user information.
- FIG. 7 is a signaling interaction diagram for implementing another authorization method provided by an embodiment of the present disclosure.
- participants include: developer applications, open source host applications, and management servers; among them, developer applications include: development The front end of the developer program and the back end of the developer program.
- Open source host applications include: auxiliary authorization components and open source host platforms. Open source host applications do not have their own independent account system.
- the account management system of the open source development platform is used, that is, the account manager of the open source host application is Management server; the authorization method includes:
- the front end of the developer program sends a login request to the auxiliary authorization component.
- the auxiliary authorization component guides the user to log in and authorize, and obtain the user's login authorization information.
- the auxiliary authorization component sends a login authorization request to the management server, and the login authorization request includes login authorization information.
- the management server After the login authorization information is verified, the management server sends authorization success information to the auxiliary authorization component, and the authorization success information includes the authorization code.
- the auxiliary authorization component forwards the authorization code to the front end of the developer program.
- the front end of the developer program forwards the authorization code to the back end of the developer program.
- the developer program backend sends a key acquisition request to the management server, and the key acquisition request includes an authorization code.
- the management server generates the session key corresponding to the authorization code.
- the management server sends the session key to the back end of the developer program.
- the front end of the developer program sends a user information acquisition request to the auxiliary authorization component.
- the auxiliary authorization component forwards the user information acquisition request to the management server.
- the management server feeds back the encrypted user information to the auxiliary authorization component.
- the auxiliary authorization component forwards the user information to the front end of the developer program.
- the front end of the developer program forwards user information to the back end of the developer program.
- the developer program backend uses the session key to decrypt user information.
- FIG. 8 is a structural block diagram of an auxiliary authorization component provided by an embodiment of the disclosure.
- the auxiliary authorization component can execute the authorization method in the embodiment shown in FIG. 2 and FIG. 3, and the auxiliary authorization component is integrated
- the auxiliary authorization component includes: a first obtaining module 101, a first sending module 102, a first receiving module 103, and a second sending module 104.
- the first obtaining module 101 is configured to obtain login authorization information of the user in response to a login request sent by the developer application.
- the first sending module 102 is configured to send a login authorization request to the account manager of the open source host application, where the login authorization request includes: login authorization information.
- the first receiving module 103 is configured to receive the authorization success information fed back by the account manager after the login authorization information is verified, and the authorization success information includes an authorization code.
- the second sending module 104 is configured to send the authorization code to the developer application for the developer application to exchange the session key corresponding to the authorization code to the management server.
- the auxiliary authorization component further includes: a third sending module 105 and a second receiving module 106.
- the third sending module 105 is configured to forward the user information acquisition request to the account manager in response to the user information acquisition request sent by the developer application.
- the second receiving module 106 is configured to receive the encrypted user information fed back by the account manager, and forward the user information to the developer application, so that the developer application can decrypt the user information based on the session key.
- the login request includes: the host identifier of the open source host application; the auxiliary authorization component further includes: a determining module; the determining module is configured to determine the account manager of the open source host application according to the host identifier.
- the account management party includes: a management server or an open source host platform in an open source host application.
- FIG. 9 is a structural block diagram of a management server provided by an embodiment of the disclosure. As shown in FIG. 9, the management server can execute the authorization method in the embodiments shown in FIG. 4 and FIG. 5, and the management server includes: Obtaining module 201 and fourth sending module 202.
- the second obtaining module 201 is configured to obtain the corresponding session key according to the authorization code in the key obtaining request in response to the key obtaining request sent by the developer application.
- the fourth sending module 202 is configured to feed back the session key to the developer application.
- the second acquiring module 201 includes: a determining unit, a generating unit, a sending unit, and a receiving unit.
- the determining unit is configured to determine the account manager of the user corresponding to the authorization code.
- the generating unit is configured to generate the session key corresponding to the authorization code if the account manager is the management server.
- the sending unit is configured to forward the key acquisition request to the third-party open source host platform if the account manager is a third-party open source host platform, so that the third-party open source host platform can generate the session key corresponding to the authorization code.
- the receiving unit is configured to receive the session key fed back by the third-party open source host platform.
- the management server further includes: a verification module 200a and a fifth sending module 200b.
- the verification module 200a is configured to verify the login authorization information in the login authorization request in response to the login authorization request sent by the auxiliary authorization component.
- the fifth sending module 200b is configured to feed back authorization success information to the auxiliary authorization component after the login authorization information is verified, and the authorization success information includes an authorization code.
- the management server further includes: a third obtaining module 203, an encryption module 204, and a sixth sending module 205.
- the third obtaining module 203 is configured to obtain the requested user information in response to the user information obtaining request sent by the auxiliary authorization component.
- the encryption module 204 is configured to encrypt user information using the session key.
- the sixth sending module 205 is configured to feed back the encrypted user information to the auxiliary authorization component.
- the embodiment of the present disclosure also provides an authorization system, which includes: the auxiliary authorization component provided in the foregoing embodiment and the management server provided in the foregoing embodiment.
- the embodiments of the present disclosure also provide a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the authorization method provided in the above-mentioned embodiments is implemented.
- Such software may be distributed on a computer-readable medium
- the computer-readable medium may include a computer storage medium (or non-transitory medium) and a communication medium (or transitory medium).
- the term computer storage medium includes volatile and non-volatile memory implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data).
- Information such as computer-readable instructions, data structures, program modules, or other data.
- Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassette, tape, magnetic disk storage or other magnetic storage device, or Any other medium used to store desired information and that can be accessed by a computer.
- a communication medium usually contains computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium. .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Multimedia (AREA)
- Technology Law (AREA)
- Computer And Data Communications (AREA)
- Telephonic Communication Services (AREA)
- Information Transfer Between Computers (AREA)
Abstract
一种授权方法、辅助授权组件、管理服务器和计算机可读介质,属于计算机技术领域,可用于云平台技术领域,该授权方法应用于辅助授权组件,辅助授权组件集成于开源宿主应用内,包括:响应于开发者应用发送的登录请求,获取用户的登录授权信息;向开源宿主应用的账户管理方发送登录授权请求,登录授权请求包括:登录授权信息;在登录授权信息验证通过后,接收账户管理方反馈的授权成功信息,授权成功信息包括:授权码;将授权码发送至开发者应用,以供开发者应用向管理服务器换取授权码所对应的会话密钥。
Description
本公开涉及计算机技术领域,可用于云平台技术领域,特别涉及一种授权方法、辅助授权组件、管理服务器和计算机可读介质。
目前,基于代码转化工具或者使用统一开发框架,使得开发者应用(例如,智能小程序)一次开发多端可运行,即开发者应用能够支持跨平台运行。一般而言,由于不同的平台所使用的账户管理体系不同,因此当开发者应用在跨平台运行时,需要新宿主平台进行用户信息授权。为此,想要真正实现开发者应用的跨平台运行,则需要解决跨平台授权的问题。
发明内容
本公开实施例提供一种授权方法、辅助授权组件、管理服务器和计算机可读介质。
第一方面,本公开实施例提供了一种授权方法,其中,该授权方法应用于辅助授权组件,所述辅助授权组件集成于开源宿主应用内,所述授权方法包括:
响应于开发者应用发送的登录请求,获取用户的登录授权信息;
向所述开源宿主应用的账户管理方发送登录授权请求,所述登录授权请求包括:所述登录授权信息;
在所述登录授权信息验证通过后,接收所述账户管理方反馈的授权成功信息,所述授权成功信息包括:授权码;
将所述授权码发送至所述开发者应用,以供开发者应用向管理服务器换 取所述授权码所对应的会话密钥。
在一些实施例中,在所述将所述授权码发送至所述开发者应用的步骤之后,还包括:
响应于所述开发者应用发送的用户信息获取请求,将所述用户信息获取请求转发至所述账户管理方;
接收所述账户管理方反馈的经过加密的用户信息,并将所述用户信息转发至所述开发者应用,以供所述开发者应用基于所述会话密钥对所述用户信息进行解密。
在一些实施例中,所述登录请求包括:所述开源宿主应用的宿主标识;
在所述获取用户的登录授权信息的步骤之后,且在所述向所述开源宿主应用的账户管理方发送登录授权请求的步骤之前,还包括:
根据所述宿主标识确定所述开源宿主应用的账户管理方。
在一些实施例中,所述账户管理方包括:所述管理服务器或所述开源宿主应用内的开源宿主平台。
第二方面,本公开实施例还提供了一种授权方法,其中,所述授权方法应用于管理服务器,所述授权方法包括:
响应于接收开发者应用发送的密钥获取请求,根据所述密钥获取请求中的授权码获取对应的会话密钥;
将所述会话密钥反馈至所述开发者应用。
在一些实施例中,所述根据所述密钥获取请求中的授权码获取对应的会话密钥的步骤包括:
确定所述授权码所对应用户的账户管理方;
若所述账户管理方为所述管理服务器,则生成所述授权码所对应的会话密钥;
若所述账户管理方为第三方开源宿主平台,则将所述密钥获取请求转发 至所述第三方开源宿主平台,以供所述第三方开源宿主平台生成所述授权码所对应的会话密钥;
接收所述第三方开源宿主平台反馈的所述会话密钥。
在一些实施例中,在所述接收开发者应用发送的密钥获取请求步骤之前,还包括:
响应于辅助授权组件发送的登录授权请求,对所述登录授权请求中的登录授权信息进行验证;
在所述登录授权信息验证通过后,向所述辅助授权组件反馈授权成功信息,所述授权成功信息包括:所述授权码。
在一些实施例中,在所述将所述会话密钥反馈至所述开发者应用的步骤之后,还包括:
响应于辅助授权组件发送的用户信息获取请求,获取所请求的用户信息;
使用所述会话密钥对所述用户信息进行加密;
将经过加密的所述用户信息反馈至所述辅助授权组件。
第三方面,本公开实施例还提供了一种辅助授权组件,其中,所述辅助授权组件集成于开源宿主应用内,所述辅助授权组件包括:
第一获取模块,配置为响应于开发者应用发送的登录请求,获取用户的登录授权信息;
第一发送模块,配置为向所述开源宿主应用的账户管理方发送登录授权请求,所述登录授权请求包括:所述登录授权信息;
第一接收模块,配置为在所述登录授权信息验证通过后,接收所述账户管理方反馈的授权成功信息,所述授权成功信息包括:授权码;
第二发送模块,配置为将所述授权码发送至所述开发者应用,以供开发者应用向管理服务器换取所述授权码所对应的会话密钥。
在一些实施例中,该辅助授权组件还包括:
第三发送模块,配置为响应于所述开发者应用发送的用户信息获取请求,将所述用户信息获取请求转发至所述账户管理方;
第二接收模块,配置为接收所述账户管理方反馈的经过加密的用户信息,并将所述用户信息转发至所述开发者应用,以供所述开发者应用基于所述会话密钥对所述用户信息进行解密。
在一些实施例中,所述登录请求包括:所述开源宿主应用的宿主标识;
所述辅助授权组件还包括:
确定模块,配置为根据所述宿主标识确定所述开源宿主应用的账户管理方。
在一些实施例中,所述账户管理方包括:所述管理服务器或所述开源宿主应用内的开源宿主平台。
第四方面,本公开实施例还提供了一种管理服务器,其中,包括:
第二获取模块,配置为响应于开发者应用发送的密钥获取请求,根据所述密钥获取请求中的授权码获取对应的会话密钥;
第四发送模块,配置为将所述会话密钥反馈至所述开发者应用。
在一些实施例中,所述第二获取模块包括:
确定单元,配置为确定所述授权码所对应用户的账户管理方;
生成单元,配置为若所述账户管理方为所述管理服务器,则生成所述授权码所对应的会话密钥;
发送单元,配置为若所述账户管理方为第三方开源宿主平台,则将所述密钥获取请求转发至所述第三方开源宿主平台,以供所述第三方开源宿主平台生成所述授权码所对应的会话密钥;
接收单元,配置为接收所述第三方开源宿主平台反馈的所述会话密钥。
在一些实施例中,所述管理服务器还包括:
验证模块,配置为响应于辅助授权组件发送的登录授权请求,对所述登录授权请求中的登录授权信息进行验证;
第五发送模块,配置为在所述登录授权信息验证通过后,向所述辅助授权组件反馈授权成功信息,所述授权成功信息包括:所述授权码。
在一些实施例中,所述管理服务器还包括:
第三获取模块,配置为响应于辅助授权组件发送的用户信息获取请求,获取所请求的用户信息;
加密模块,配置为使用所述会话密钥对所述用户信息进行加密;
第六发送模块,配置为将经过加密的所述用户信息反馈至所述辅助授权组件。
第五方面,本公开实施例还提供了一种授权***,包括:上述第三方面中任一实施例提供的辅助授权组件和上述第四方面中任一实施例提供的管理服务器。
第六方面,本公开实施例还提供了一种计算机可读介质,其上存储有计算机程序,所述程序被处理器执行时实现上第一方面、第二方面中任一实施例提供所述的授权方法。
本公开实施例提供了一种授权方法、辅助授权组件、管理服务器和计算机可读介质,可实现用户能够将其在开源宿主应用中的部分或全部用户信息授权给开发者应用使用,以保障开发者应用的跨平台运行。
附图用来提供对本公开实施例的进一步理解,并且构成说明书的一部分,与本公开的实施例一起用于解释本公开,并不构成对本公开的限制。通过参考附图对详细示例实施例进行描述,以上和其它特征和优点对本领域技术人员将变得更加显而易见,在附图中:
图1为本公开实施例中跨平台授权的参与各方示意图;
图2为本公开实施例提供的一种授权方法的流程图;
图3为本公开实施例提供的另一种授权方法的流程图;
图4为本公开实施例提供的又一种授权方法的流程图;
图5为本公开实施例提供的再一种授权方法的流程图;
图6为本公开实施例提供的一种实现授权方法的信令交互图;
图7为本公开实施例提供的另一种实现授权方法的信令交互图;
图8为本公开实施例提供的一种辅助授权组件的结构框图;
图9为本公开实施例提供的一种管理服务器的结构框图。
为使本领域的技术人员更好地理解本公开的技术方案,下面结合附图对本公开提供的一种授权方法、辅助授权组件、管理服务器和计算机可读介质进行详细描述。
在下文中将参考附图更充分地描述示例实施例,但是所述示例实施例可以以不同形式来体现且不应当被解释为限于本文阐述的实施例。反之,提供这些实施例的目的在于使本公开透彻和完整,并将使本领域技术人员充分理解本公开的范围。
在不冲突的情况下,本公开各实施例及实施例中的各特征可相互组合。
如本文所使用的,术语“和/或”包括一个或多个相关列举条目的任何和所有组合。
本文所使用的术语仅用于描述特定实施例,且不意欲限制本公开。如本文所使用的,单数形式“一个”和“该”也意欲包括复数形式,除非上下文另外清楚指出。还将理解的是,当本说明书中使用术语“包括”和/或“由……制成”时,指定存在所述特征、整体、步骤、操作、元件和/或组件,但不排除存在或添加一个或多个其它特征、整体、步骤、操作、元件、组件 和/或其群组。
除非另外限定,否则本文所用的所有术语(包括技术和科学术语)的含义与本领域普通技术人员通常理解的含义相同。还将理解,诸如那些在常用字典中限定的那些术语应当被解释为具有与其在相关技术以及本公开的背景下的含义一致的含义,且将不解释为具有理想化或过度形式上的含义,除非本文明确如此限定。
图1为本公开实施例中跨平台授权的参与各方示意图,如图1所示,跨平台授权过程的参与方包括:开发者应用、开源宿主应用和管理服务器。
其中,“开发者”是指基于开源开发平台开发应用(App,也可以为小程序Mini Program)的开发方,“开发者应用”是指开发方基于开源开发平台所开发出的应用,该应用可支持跨平台运行。以“百度智能小程序”平台为例,其为开源的小程序开发平台,为了打通其与其他各平台间壁垒,百度智能小程序完全开放,支持百度系应用(App)和外部App运行(例如,趣头条、快手等),实现了一次开发多端可运行。
“开源宿主应用”为能够承载开发者应用运行,作为开发者应用的宿主的本地应用(Native App,也称为第三方应用),例如手机百度App、WIFI智能钥匙App。在本公开实施例中,开源宿主应用中不仅包含有支持本应用功能的开源宿主平台,还集成有辅助授权组件。对于辅助授权组件,将会在后续内容进行详细描述。
“管理服务器”为开源开发平台的后端服务器,其管理开源开发平台的账户体系,能够供开源宿主应用接入注册(使得该开源宿主应用集成有辅助授权组件,且能够承载基于开源开发平台开发出的开发者应用),也可以管理完成接入注册的各开源宿主应用的账户授权。此外,管理服务器也可以为没有自己独立账户体系的开源宿主应用共享自身的账户体系,即用户能够基于开源开发平台的账户来登录该开源宿主应用。
图2为本公开实施例提供的一种授权方法的流程图,如图2所示,该授权方法用于实现用户能够将其在开源宿主应用中的部分或全部用户信息授权给开发者应用使用。该授权方法的执行主体为辅助授权组件,该辅助授权组件集成于开源宿主应用内,该授权方法包括:
步骤S101、响应于开发者应用发送的登录请求,获取用户的登录授权信息。
在本公开实施例中,不同的开源宿主应用中均集成有相同的辅助授权组件。开发者应用发送的登录请求中包含有待访问的开源宿主应用的宿主标识、请求用户授权的授权项目(例如,用户头像、用户帐号、用户手机号、用户业务数据等)。其中,基于宿主标识可使得辅助授权组件确定用户待登录的开源宿主平台是否为与其属于同一开源宿主应用的开源宿主平台。若否,则直接向开发者应用反馈登录请求失败;若是,则提供预先设计的登录界面供用户输入登录帐号、密码/验证码等登录信息,以及提供授权界面,供用户确认是否授权登录请求中各授权项目给开发者应用。其中,若用户拒绝授权,则向开发者应用反馈用户拒绝授权的信息;若用户同意授权,则获取用户输入的登录信息以及确认授权的相关授权信息,以作为用户的登录授权信息,此后执行步骤S102。
步骤S102、向开源宿主应用的账户管理方发送登录授权请求。
在一些实施例中,在步骤S102之前还包括:根据宿主标识确定开源宿主应用的账户管理方的步骤。在本公开实施例中,开源宿主应用的账户体系有两种情况:其一,开源宿主应用使用自己独立的账户体系,此时开源宿主应用的账户管理方为开源宿主应用内的开源宿主平台,辅助授权组件向开源宿主应用内的开源宿主平台发送登录授权请求;其二,开源宿主应用共享使用开源开发平台的账户体系,此时开源宿主应用的账户管理方为管理服务器,辅助授权组件向管理服务器发送登录授权请求。
辅助授权组件向开源宿主应用的账户管理方发送登录授权请求,以供账户管理方对登录授权请求中所包含的登录授权信息进行验证。具体地,账户管理方验证用户输入的登录信息是否正确,以及验证用户确认授权的授权项目是否在该用户的权限范围内;若用户输入的登录信息正确且确认授权的授权项目在其权限范围内,则表示登录授权信息验证通过,账户管理方生成授权码,并向辅助授权组件发送授权成功信息,其中授权成功信息包括授权码,此后执行步骤S103;反之,则表示登录授权信息验证不通过,账户管理方向辅助授权组件反馈授权失败信息,辅助授权组件将授权失败信息展示给用户。
其中,授权码为用户授权的标识。在用户完成对应用的授权且授权验证通过后,账户管理方会生成一个很短时间(例如,10分钟)内有效的授权标识,且该授权码具有有效使用次数,一般为1次。
步骤S103、在登录授权信息验证通过后,接收账户管理方反馈的授权成功信息。
在步骤S103中,辅助授权组件接收账户管理方反馈授权成功信息,该授权成功信息中包含有授权码。
当账户管理方为管理服务器时,授权成功信息中还包括有表征用户登录成功的标识,其为采用用户标识(字段名一般为UId)、开源宿主标识(字段名一般为Host_Id)、当前时间(字段名一般为Current_Time)等维度构成的一种用户身份的标识。
步骤S104、将授权码发送至开发者应用,以供开发者应用向管理服务器换取授权码所对应的会话密钥。
在步骤S104中,辅助授权组件将授权码(Code)发送至开发者应用,开发者应用向管理服务器发送密钥获取请求,以请求换取授权码所对应的会话密钥(Session Key)。其中,密钥获取请求包括:授权码、应用标识(开 发者应用的应用名称,字段名一般为Client_ID)和应用密钥(开发者应用的密钥,字段名一般为Secret_Key)。管理服务器会根据授权码的格式,来确定该授权码为其自身所生成还是为其他第三方的开源宿主平台所生成。
若授权码为管理服务器自身所生成,则管理服务器对该授权码的有效性进行验证,并在有效性验证通过后生成与该授权码所对应的会话密钥,并向开发者应用反馈一段JSON文本,包含用户身份标识(字段名一般为openid,由开发者应用标识AppID和用户标识UId生成)和会话密钥(字段名一般为Session_Key);若授权码的有效性验证失败,则管理服务器向开发者应用反馈另一段JSON文本,包含错误码(字段名一般为error)和错误描述信息(字段名一般为error_description)。
若授权码为其他第三方的开源宿主平台所生成,则管理服务器将密钥获取请求转发至该开源宿主平台,开源宿主平台对授权码的有效性进行验证,并在有效性验证通过后生成与该授权码所对应的会话密钥,并向管理服务器反馈一段JSON文本,包含用户身份标识和会话密钥;若授权码的有效性验证失败,则开源宿主平台向管理服务器反馈另一段JSON文本,包含错误码和错误描述信息。管理服务器将接收到的JSON文本转发至开发者应用。
需要说明的是,根据授权码生成对应的会话密钥的过程为本领域的常规技术,此处不进行详细描述。
在开发者应用获取到会话密钥后,即表示用户授权成功。
本公开实施例所提供的授权方法,可实现用户对开发者应用的跨平台授权。
图3为本公开实施例提供的另一种授权方法的流程图,如图3所示,与图1所示实施例不同的是,图3所示授权方法不但包括上述步骤S101~步骤S104,在步骤S104之后还包括步骤S105和步骤S106。下面仅对步骤S105和步骤S106进行详细描述。
步骤S105、响应于开发者应用发送的用户信息获取请求,将用户信息获取请求转发至账户管理方。
开发者应用向辅助授权组件发送用户信息获取请求,用户信息获取请求包含有开发者应用的应用标识、获得授权的用户的用户标识以及开发者应用所请求的该用户的用户信息(例如,用户头像、用户帐号、用户手机号、用户业务数据等)。辅助授权组件将该用户信息获取请求发送至开源宿主应用的账户管理方,账户管理方从自身数据库中确定出用户信息获取请求所请求的用户信息,并利用该用户的会话密钥来对确定出的用户信息进行加密,且将加密后的用户信息反馈给辅助授权组件。
步骤S106、接收账户管理方反馈的经过加密的用户信息,并将用户信息转发至开发者应用,以供开发者应用基于会话密钥对用户信息进行解密。
辅助授权组件接收账户管理方反馈的经过加密的用户信息,并将该用户信息转发给开发者应用,开发者应用基于之前获取到的会话密钥来对接收到的用户信息进行解密,以获得用户信息明文。
图4为本公开实施例提供的又一种授权方法的流程图,如图4所示,该授权方法的执行主体为管理服务器,该授权方法包括:
步骤S201、响应于接收开发者应用发送的密钥获取请求,根据密钥获取请求中的授权码获取对应的会话密钥。
开发者应用获取到授权码后,向管理服务器发送密钥获取请求,密钥获取请求包括:授权码、应用标识和应用密钥。管理服务器会根据授权码的格式,来确定该授权码为其自身所生成还是为其他第三方的开源宿主平台所生成。若授权码为管理服务器自身所生成,则管理服务器根据自身生成的该授权码获取对应的会话密钥;若授权码为其他第三方的开源宿主平台所生成,则管理服务器将密钥获取请求转发至该开源宿主平台,开源宿主平台生成该授权码对应的会话密钥,并将该会话密钥反馈给管理服务器,管理服务器接 收第三方的开源宿主平台反馈的会话密钥。
步骤S202、将会话密钥反馈至开发者应用。
在管理服务器获取到授权码所对应的会话密钥后,将会话密钥反馈至开发者应用。
图5为本公开实施例提供的再一种授权方法的流程图,如图5所示,在本实施例中,开源宿主应用没有自身独立账户体系,使用的是开源开发平台的账户体系,即管理服务器为该开源宿主应用共享自身的账户体系。与图4所示实施例不同的是,该授权方法不但包括上述步骤S201和步骤S202,还在步骤S201之前包括步骤S200a和步骤S200b,在步骤S202之后包括步骤S203、步骤S204和步骤S205。
步骤S200a、响应于辅助授权组件发送的登录授权请求,对登录授权请求中的登录授权信息进行验证。
步骤S200b、在登录授权信息验证通过后,向辅助授权组件反馈授权成功信息,授权成功信息包括:授权码。
步骤S201、响应于接收开发者应用发送的密钥获取请求,根据密钥获取请求中的授权码获取对应的会话密钥。
步骤S202、将会话密钥反馈至开发者应用。
步骤S203、响应于辅助授权组件发送的用户信息获取请求,获取所请求的用户信息。
步骤S204、使用会话密钥对用户信息进行加密。
步骤S205、将经过加密的用户信息反馈至辅助授权组件。
对于上述各步骤的具体描述,可参见前述实施例中相应内容,此处不再赘述。
图6为本公开实施例提供的一种实现授权方法的信令交互图,如图6所示,参与方包括:开发者应用、开源宿主应用和管理服务器;其中,开发者 应用包括:开发者程序前端和开发者程序后端,开源宿主应用包括:辅助授权组件和开源宿主平台,开源宿主应用有自身独立账户体系,即开源宿主应用的账户管理方为开源宿主平台;该授权方法包括:
BZ101、开发者程序前端向辅助授权组件发送登录请求。
BZ102、辅助授权组件引导用户登录、授权,获取用户的登录授权信息。
BZ103、辅助授权组件向开源宿主平台发送登录授权请求,登录授权请求包括登录授权信息。
BZ104、在登录授权信息验证通过后,开源宿主平台向辅助授权组件发送授权成功信息,授权成功信息包括授权码。
BZ105、辅助授权组件将授权码转发给开发者程序前端。
BZ106、开发者程序前端将授权码转发给开发者程序后端。
BZ107、开发者程序后端向管理服务器发送密钥获取请求,密钥获取请求包括授权码。
BZ108、管理服务器将授权码分发给开源宿主平台。
BZ109、开源宿主平台生成授权码所对应的会话密钥,并将会话密钥发送给管理服务器。
BZ110、管理服务器将会话密钥转发给开发者程序后端。
BZ111、开发者程序前端向辅助授权组件发送用户信息获取请求。
BZ112、辅助授权组件将用户信息获取请求转发至开源宿主平台。
BZ113、开源宿主平台向辅助授权组件反馈经过加密的用户信息。
BZ114、辅助授权组件将用户信息转发给开发者程序前端。
BZ115、开发者程序前端将用户信息转发给开发者程序后端。
BZ116、开发者程序后端使用会话密钥对用户信息进行解密。
图7为本公开实施例提供的另一种实现授权方法的信令交互图,如图7所示,参与方包括:开发者应用、开源宿主应用和管理服务器;其中,开发 者应用包括:开发者程序前端和开发者程序后端,开源宿主应用包括:辅助授权组件和开源宿主平台,开源宿主应用没有自身独立账户体系,使用开源开发平台的账户管理体系,即开源宿主应用的账户管理方为管理服务器;该授权方法包括:
BZ201、开发者程序前端向辅助授权组件发送登录请求。
BZ202、辅助授权组件引导用户登录、授权,获取用户的登录授权信息。
BZ203、辅助授权组件向管理服务器发送登录授权请求,登录授权请求包括登录授权信息。
BZ204、在登录授权信息验证通过后,管理服务器向辅助授权组件发送授权成功信息,授权成功信息包括授权码。
BZ205、辅助授权组件将授权码转发给开发者程序前端。
BZ206、开发者程序前端将授权码转发给开发者程序后端。
BZ207、开发者程序后端向管理服务器发送密钥获取请求,密钥获取请求包括授权码。
BZ208、管理服务器生成授权码所对应的会话密钥。
BZ209、管理服务器将会话密钥发送给开发者程序后端。
BZ210、开发者程序前端向辅助授权组件发送用户信息获取请求。
BZ211、辅助授权组件将用户信息获取请求转发至管理服务器。
BZ212、管理服务器向辅助授权组件反馈经过加密的用户信息。
BZ213、辅助授权组件将用户信息转发给开发者程序前端。
BZ214、开发者程序前端将用户信息转发给开发者程序后端。
BZ215、开发者程序后端使用会话密钥对用户信息进行解密。
图8为本公开实施例提供的一种辅助授权组件的结构框图,如图8所示,该辅助授权组件能够执行前述图2和图3所示实施例中的授权方法,该辅助授权组件集成于开源宿主应用内,辅助授权组件包括:第一获取模块 101、第一发送模块102、第一接收模块103和第二发送模块104。
其中,第一获取模块101配置为响应于开发者应用发送的登录请求,获取用户的登录授权信息。
第一发送模块102配置为向开源宿主应用的账户管理方发送登录授权请求,登录授权请求包括:登录授权信息。
第一接收模块103配置为在登录授权信息验证通过后,接收账户管理方反馈的授权成功信息,授权成功信息包括:授权码。
第二发送模块104配置为将授权码发送至开发者应用,以供开发者应用向管理服务器换取授权码所对应的会话密钥。
在一些实施例中,该辅助授权组件还包括:第三发送模块105和第二接收模块106。
其中,第三发送模块105配置为响应于开发者应用发送的用户信息获取请求,将用户信息获取请求转发至账户管理方。
第二接收模块106配置为接收账户管理方反馈的经过加密的用户信息,并将用户信息转发至开发者应用,以供开发者应用基于会话密钥对用户信息进行解密。
在一些实施例中,登录请求包括:开源宿主应用的宿主标识;辅助授权组件还包括:确定模块;确定模块配置为根据宿主标识确定开源宿主应用的账户管理方。
在一些实施例中,账户管理方包括:管理服务器或开源宿主应用内的开源宿主平台。
对于上述各模块以及各模块之间交互的具体描述,可参见前述实施例中相应内容,此处不再赘述。
图9为本公开实施例提供的一种管理服务器的结构框图,如图9所示,该管理服务器能够执行前述图4和图5所示实施例中的授权方法,该管理服 务器包括:第二获取模块201和第四发送模块202。
其中,第二获取模块201配置为响应于开发者应用发送的密钥获取请求,根据密钥获取请求中的授权码获取对应的会话密钥。
第四发送模块202配置为将会话密钥反馈至开发者应用。
在一些实施例中,第二获取模块201包括:确定单元、生成单元、发送单元和接收单元。
其中,确定单元配置为确定授权码所对应用户的账户管理方。
生成单元配置为若账户管理方为管理服务器,则生成授权码所对应的会话密钥。
发送单元配置为若账户管理方为第三方开源宿主平台,则将密钥获取请求转发至第三方开源宿主平台,以供第三方开源宿主平台生成授权码所对应的会话密钥。
接收单元配置为接收第三方开源宿主平台反馈的会话密钥。
在一些实施例中,管理服务器还包括:验证模块200a和第五发送模块200b。
其中,验证模块200a配置为响应于辅助授权组件发送的登录授权请求,对登录授权请求中的登录授权信息进行验证。
第五发送模块200b配置为在登录授权信息验证通过后,向辅助授权组件反馈授权成功信息,授权成功信息包括:授权码。
在一些实施例中,管理服务器还包括:第三获取模块203、加密模块204和第六发送模块205。
其中,第三获取模块203配置为响应于辅助授权组件发送的用户信息获取请求,获取所请求的用户信息。
加密模块204配置为使用会话密钥对用户信息进行加密。
第六发送模块205配置为将经过加密的用户信息反馈至辅助授权组件。
对于上述各模块以及各模块之间交互的具体描述,可参见前述实施例中相应内容,此处不再赘述。
本公开实施例还提供了一种授权***,包括:上述实施例提供的辅助授权组件和上述实施例提供的管理服务器。
本公开实施例还提供了一种计算机可读介质,其上存储有计算机程序,程序被处理器执行时实现上述实施例所提供的授权方法。
本领域普通技术人员可以理解,上文中所公开方法中的全部或某些步骤、***、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中,在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分;例如,一个物理组件可以具有多个功能,或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器,如中央处理器、数字信号处理器或微处理器执行的软件,或者被实施为硬件,或者被实施为集成电路,如专用集成电路。这样的软件可以分布在计算机可读介质上,计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的,术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其它数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其它存储器技术、CD-ROM、数字多功能盘(DVD)或其它光盘存储、磁盒、磁带、磁盘存储或其它磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其它的介质。此外,本领域普通技术人员公知的是,通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其它传输机制之类的调制数据信号中的其它数据,并且可包括任何信息递送介质。
本文已经公开了示例实施例,并且虽然采用了具体术语,但它们仅用于 并仅应当被解释为一般说明性含义,并且不用于限制的目的。在一些实例中,对本领域技术人员显而易见的是,除非另外明确指出,否则可单独使用与特定实施例相结合描述的特征、特性和/或元素,或可与其它实施例相结合描述的特征、特性和/或元件组合使用。因此,本领域技术人员将理解,在不脱离由所附的权利要求阐明的本公开的范围的情况下,可进行各种形式和细节上的改变。
Claims (18)
- 一种授权方法,其特征在于,应用于辅助授权组件,所述辅助授权组件集成于开源宿主应用内,所述授权方法包括:响应于开发者应用发送的登录请求,获取用户的登录授权信息;向所述开源宿主应用的账户管理方发送登录授权请求,所述登录授权请求包括:所述登录授权信息;在所述登录授权信息验证通过后,接收所述账户管理方反馈的授权成功信息,所述授权成功信息包括:授权码;将所述授权码发送至所述开发者应用,以供开发者应用向管理服务器换取所述授权码所对应的会话密钥。
- 根据权利要求1所述的授权方法,其特征在于,在所述将所述授权码发送至所述开发者应用的步骤之后,还包括:响应于所述开发者应用发送的用户信息获取请求,将所述用户信息获取请求转发至所述账户管理方;接收所述账户管理方反馈的经过加密的用户信息,并将所述用户信息转发至所述开发者应用,以供所述开发者应用基于所述会话密钥对所述用户信息进行解密。
- 根据权利要求1所述的授权方法,其特征在于,所述登录请求包括:所述开源宿主应用的宿主标识;在所述获取用户的登录授权信息的步骤之后,且在所述向所述开源宿主应用的账户管理方发送登录授权请求的步骤之前,还包括:根据所述宿主标识确定所述开源宿主应用的账户管理方。
- 根据权利要求1-3中任一所述的授权方法,其特征在于,所述账户管 理方包括:所述管理服务器或所述开源宿主应用内的开源宿主平台。
- 一种授权方法,其特征在于,应用于管理服务器,所述授权方法包括:响应于接收开发者应用发送的密钥获取请求,根据所述密钥获取请求中的授权码获取对应的会话密钥;将所述会话密钥反馈至所述开发者应用。
- 根据权要求5所述的授权方法,其特征在于,所述根据所述密钥获取请求中的授权码获取对应的会话密钥的步骤包括:确定所述授权码所对应用户的账户管理方;若所述账户管理方为所述管理服务器,则生成所述授权码所对应的会话密钥;若所述账户管理方为第三方开源宿主平台,则将所述密钥获取请求转发至所述第三方开源宿主平台,以供所述第三方开源宿主平台生成所述授权码所对应的会话密钥;接收所述第三方开源宿主平台反馈的所述会话密钥。
- 根据权利要求5所述的授权方法,其特征在于,在所述接收开发者应用发送的密钥获取请求步骤之前,还包括:响应于辅助授权组件发送的登录授权请求,对所述登录授权请求中的登录授权信息进行验证;在所述登录授权信息验证通过后,向所述辅助授权组件反馈授权成功信息,所述授权成功信息包括:所述授权码。
- 根据权利要求5所述的授权方法,其特征在于,在所述将所述会话密钥反馈至所述开发者应用的步骤之后,还包括:响应于辅助授权组件发送的用户信息获取请求,获取所请求的用户信 息;使用所述会话密钥对所述用户信息进行加密;将经过加密的所述用户信息反馈至所述辅助授权组件。
- 一种辅助授权组件,其特征在于,所述辅助授权组件集成于开源宿主应用内,所述辅助授权组件包括:第一获取模块,配置为响应于开发者应用发送的登录请求,获取用户的登录授权信息;第一发送模块,配置为向所述开源宿主应用的账户管理方发送登录授权请求,所述登录授权请求包括:所述登录授权信息;第一接收模块,配置为在所述登录授权信息验证通过后,接收所述账户管理方反馈的授权成功信息,所述授权成功信息包括:授权码;第二发送模块,配置为将所述授权码发送至所述开发者应用,以供开发者应用向管理服务器换取所述授权码所对应的会话密钥。
- 根据权利要求9所述的辅助授权组件,其特征在于,还包括:第三发送模块,配置为响应于所述开发者应用发送的用户信息获取请求,将所述用户信息获取请求转发至所述账户管理方;第二接收模块,配置为接收所述账户管理方反馈的经过加密的用户信息,并将所述用户信息转发至所述开发者应用,以供所述开发者应用基于所述会话密钥对所述用户信息进行解密。
- 根据权利要求9所述的辅助授权组件,其特征在于,所述登录请求包括:所述开源宿主应用的宿主标识;所述辅助授权组件还包括:确定模块,配置为根据所述宿主标识确定所述开源宿主应用的账户管理方。
- 根据权利要求9-11中任一所述的辅助授权组件,其特征在于,所述账户管理方包括:所述管理服务器或所述开源宿主应用内的开源宿主平台。
- 一种管理服务器,其特征在于,包括:第二获取模块,配置为响应于开发者应用发送的密钥获取请求,根据所述密钥获取请求中的授权码获取对应的会话密钥;第四发送模块,配置为将所述会话密钥反馈至所述开发者应用。
- 根据权要求13所述的管理服务器,其特征在于,所述第二获取模块包括:确定单元,配置为确定所述授权码所对应用户的账户管理方;生成单元,配置为若所述账户管理方为所述管理服务器,则生成所述授权码所对应的会话密钥;发送单元,配置为若所述账户管理方为第三方开源宿主平台,则将所述密钥获取请求转发至所述第三方开源宿主平台,以供所述第三方开源宿主平台生成所述授权码所对应的会话密钥;接收单元,配置为接收所述第三方开源宿主平台反馈的所述会话密钥。
- 根据权利要求13所述的管理服务器,其特征在于,还包括:验证模块,配置为响应于辅助授权组件发送的登录授权请求,对所述登录授权请求中的登录授权信息进行验证;第五发送模块,配置为在所述登录授权信息验证通过后,向所述辅助授权组件反馈授权成功信息,所述授权成功信息包括:所述授权码。
- 根据权利要求13所述的管理服务器,其特征在于,还包括:第三获取模块,配置为响应于辅助授权组件发送的用户信息获取请求, 获取所请求的用户信息;加密模块,配置为使用所述会话密钥对所述用户信息进行加密;第六发送模块,配置为将经过加密的所述用户信息反馈至所述辅助授权组件。
- 一种授权***,其特征在于,包括:如上述权利要求9-12中任一所述的辅助授权组件和如上述权利要求13-16中任一所述的管理服务器。
- 一种计算机可读介质,其特征在于,其上存储有计算机程序,所述程序被处理器执行时实现权利要求1-8中任一所述的授权方法。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP20861986.6A EP3851983B1 (en) | 2020-02-17 | 2020-07-14 | Authorization method, auxiliary authorization component, management server and computer readable medium |
US17/276,279 US20220124096A1 (en) | 2020-02-17 | 2020-07-14 | Authorization method and non-transitory computer-readable storage medium |
JP2021516955A JP7159461B2 (ja) | 2020-02-17 | 2020-07-14 | 認可方法、補助認可コンポーネント、管理サーバ、及びコンピュータ読み取り可能な媒体 |
KR1020217007876A KR102508770B1 (ko) | 2020-02-17 | 2020-07-14 | 인증 방법, 보조 인증 컴포넌트, 관리 서버 및 컴퓨터 판독 가능 매체 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010097872.X | 2020-02-17 | ||
CN202010097872.XA CN111259356B (zh) | 2020-02-17 | 2020-02-17 | 授权方法、辅助授权组件、管理服务器和计算机可读介质 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021098241A1 true WO2021098241A1 (zh) | 2021-05-27 |
Family
ID=70949294
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/101795 WO2021098241A1 (zh) | 2020-02-17 | 2020-07-14 | 授权方法、辅助授权组件、管理服务器和计算机可读介质 |
Country Status (5)
Country | Link |
---|---|
US (1) | US20220124096A1 (zh) |
EP (1) | EP3851983B1 (zh) |
JP (1) | JP7159461B2 (zh) |
CN (1) | CN111259356B (zh) |
WO (1) | WO2021098241A1 (zh) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111259356B (zh) * | 2020-02-17 | 2022-09-02 | 北京百度网讯科技有限公司 | 授权方法、辅助授权组件、管理服务器和计算机可读介质 |
CN112968871B (zh) * | 2021-01-29 | 2022-08-02 | 北京字节跳动网络技术有限公司 | 应用程序的登录方法、装置、可读介质和电子设备 |
CN116032556A (zh) * | 2022-12-13 | 2023-04-28 | 支付宝(杭州)信息技术有限公司 | 小程序应用的密钥协商方法及装置 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102238007A (zh) * | 2010-04-20 | 2011-11-09 | 阿里巴巴集团控股有限公司 | 第三方应用获得用户的会话令牌的方法、装置及*** |
CN103347002A (zh) * | 2013-06-13 | 2013-10-09 | 百度在线网络技术(北京)有限公司 | 社会化登录方法、***和装置 |
CN103795692A (zh) * | 2012-10-31 | 2014-05-14 | 中国电信股份有限公司 | 开放授权方法、***与认证授权服务器 |
CN105207974A (zh) * | 2014-06-18 | 2015-12-30 | 中国电信股份有限公司 | 一种实现用户资源差异化开放的方法、平台、应用和*** |
CN111259356A (zh) * | 2020-02-17 | 2020-06-09 | 北京百度网讯科技有限公司 | 授权方法、辅助授权组件、管理服务器和计算机可读介质 |
Family Cites Families (33)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4423287A (en) * | 1981-06-26 | 1983-12-27 | Visa U.S.A., Inc. | End-to-end encryption system and method of operation |
US4578530A (en) * | 1981-06-26 | 1986-03-25 | Visa U.S.A., Inc. | End-to-end encryption system and method of operation |
US7739327B2 (en) * | 2001-04-05 | 2010-06-15 | Playstream Inc. | Distributed link processing system for delivering application and multi-media content on the internet |
US8855099B2 (en) * | 2007-03-19 | 2014-10-07 | Qualcomm Incorporated | Selective phase connection establishment |
US20100082372A1 (en) * | 2008-09-30 | 2010-04-01 | Microsoft Corporation | Network-based healthcare data management |
US8898318B2 (en) * | 2010-06-03 | 2014-11-25 | Microsoft Corporation | Distributed services authorization management |
US10242368B1 (en) * | 2011-10-17 | 2019-03-26 | Capital One Services, Llc | System and method for providing software-based contactless payment |
WO2013075661A1 (zh) * | 2011-11-23 | 2013-05-30 | 腾讯科技(深圳)有限公司 | 登录及开放平台标识方法、开放平台及*** |
US9106635B2 (en) * | 2012-03-01 | 2015-08-11 | Certicom Corp. | System and method for connecting client devices to a network |
CN103428166B (zh) * | 2012-05-16 | 2016-03-02 | 腾讯科技(深圳)有限公司 | 第三方应用的多sns平台统一接入方法及*** |
CA2875823C (en) * | 2012-06-29 | 2021-01-05 | Id Dataweb, Inc. | System and method for establishing and monetizing trusted identities in cyberspace with personal data service and user console |
CN103581118B (zh) * | 2012-07-24 | 2018-05-01 | 中兴通讯股份有限公司 | 一种资源汇聚网关及跨平台授权方法与*** |
US8832782B2 (en) * | 2012-08-31 | 2014-09-09 | Avaya Inc. | Single sign-on system and method |
CN104125063B (zh) * | 2013-04-28 | 2016-10-12 | 腾讯科技(深圳)有限公司 | 授权认证方法、设备及*** |
JP6248422B2 (ja) * | 2013-06-05 | 2017-12-20 | 富士通株式会社 | 情報開示システム、情報開示プログラム及び情報開示方法 |
WO2014201811A1 (en) * | 2013-06-20 | 2014-12-24 | Tencent Technology (Shenzhen) Company Limited | Method, device and system for logging in through a browser application at a client terminal |
US9118650B1 (en) * | 2013-09-23 | 2015-08-25 | Amazon Technologies, Inc. | Persistent connections for email web applications |
US9420463B2 (en) * | 2014-09-30 | 2016-08-16 | Sap Se | Authorization based on access token |
CN105763514B (zh) * | 2014-12-17 | 2019-11-29 | 华为技术有限公司 | 一种处理授权的方法、设备和*** |
WO2018209138A1 (en) * | 2017-05-10 | 2018-11-15 | Mine Zero Gmbh | Secure telecommunications and transactional platform |
GB2547676B (en) * | 2016-02-25 | 2018-03-21 | Arm Ip Ltd | Methods and resources for generating secure communications |
CN109643242B (zh) * | 2016-05-23 | 2023-06-27 | 摩根大通国家银行 | 用于多租户hadoop集群的安全设计和架构 |
US10375053B2 (en) * | 2016-09-09 | 2019-08-06 | Microsoft Technology Licensing, Llc | Cross-platform single sign-on accessibility of a productivity application within a software as a service platform |
US10158646B1 (en) * | 2016-10-10 | 2018-12-18 | Charles Schwab & Co., Inc. | System and method for providing a web service using a mobile device capturing dual images |
CN108259431A (zh) * | 2016-12-29 | 2018-07-06 | 航天信息股份有限公司 | 多应用间共享账号信息的方法、装置及*** |
US10841084B2 (en) * | 2017-02-03 | 2020-11-17 | Qualcomm Incorporated | Session management authorization token |
JP2018205840A (ja) * | 2017-05-30 | 2018-12-27 | キヤノン株式会社 | システム、その方法およびそのプログラム |
US10866963B2 (en) * | 2017-12-28 | 2020-12-15 | Dropbox, Inc. | File system authentication |
CN108712382B (zh) * | 2018-04-17 | 2021-07-06 | 新大陆(福建)公共服务有限公司 | 一种基于安全二维码的数字身份的认证方法以及*** |
US10764273B2 (en) * | 2018-06-28 | 2020-09-01 | Oracle International Corporation | Session synchronization across multiple devices in an identity cloud service |
CN109768961A (zh) * | 2018-12-12 | 2019-05-17 | 平安科技(深圳)有限公司 | 基于一账通的微信小程序登录方法、装置及存储介质 |
CN110069919B (zh) * | 2019-04-25 | 2021-08-24 | 上海连尚网络科技有限公司 | 信息获取方法和装置 |
US11699150B2 (en) * | 2019-07-25 | 2023-07-11 | Paypal, Inc. | Systems and methods for two-way account onboarding and linking across multiple service providers |
-
2020
- 2020-02-17 CN CN202010097872.XA patent/CN111259356B/zh active Active
- 2020-07-14 WO PCT/CN2020/101795 patent/WO2021098241A1/zh unknown
- 2020-07-14 EP EP20861986.6A patent/EP3851983B1/en active Active
- 2020-07-14 US US17/276,279 patent/US20220124096A1/en not_active Abandoned
- 2020-07-14 JP JP2021516955A patent/JP7159461B2/ja active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102238007A (zh) * | 2010-04-20 | 2011-11-09 | 阿里巴巴集团控股有限公司 | 第三方应用获得用户的会话令牌的方法、装置及*** |
CN103795692A (zh) * | 2012-10-31 | 2014-05-14 | 中国电信股份有限公司 | 开放授权方法、***与认证授权服务器 |
CN103347002A (zh) * | 2013-06-13 | 2013-10-09 | 百度在线网络技术(北京)有限公司 | 社会化登录方法、***和装置 |
CN105207974A (zh) * | 2014-06-18 | 2015-12-30 | 中国电信股份有限公司 | 一种实现用户资源差异化开放的方法、平台、应用和*** |
CN111259356A (zh) * | 2020-02-17 | 2020-06-09 | 北京百度网讯科技有限公司 | 授权方法、辅助授权组件、管理服务器和计算机可读介质 |
Also Published As
Publication number | Publication date |
---|---|
EP3851983A1 (en) | 2021-07-21 |
JP2022512055A (ja) | 2022-02-02 |
CN111259356A (zh) | 2020-06-09 |
EP3851983A4 (en) | 2021-10-20 |
US20220124096A1 (en) | 2022-04-21 |
EP3851983B1 (en) | 2023-03-29 |
JP7159461B2 (ja) | 2022-10-24 |
CN111259356B (zh) | 2022-09-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11736469B2 (en) | Single sign-on enabled OAuth token | |
US20210288957A1 (en) | Time-based one time password (totp) for network authentication | |
US9729537B2 (en) | System and method for identity management for mobile devices | |
WO2021098241A1 (zh) | 授权方法、辅助授权组件、管理服务器和计算机可读介质 | |
US20210385216A1 (en) | Personal identity system | |
US9660985B2 (en) | Service authorization using auxiliary device | |
US9608814B2 (en) | System and method for centralized key distribution | |
US9038138B2 (en) | Device token protocol for authorization and persistent authentication shared across applications | |
CN104954330B (zh) | 一种对数据资源进行访问的方法、装置和*** | |
US9100171B1 (en) | Computer-implemented forum for enabling secure exchange of information | |
US10382213B1 (en) | Certificate registration | |
CN105659558A (zh) | 具有单一、灵活、可插拔OAuth服务器的多个资源服务器和OAuth保护的RESTful OAuth同意管理服务,以及对OAuth服务的移动应用单点登录 | |
US20050114694A1 (en) | System and method for authentication of applications in a non-trusted network environment | |
CN111294356A (zh) | 基于区块链的组织节点上链方法和*** | |
US11907356B2 (en) | System, method, and computer-readable recording medium of creating, accessing, and recovering a user account with single sign on password hidden authentication | |
KR102508770B1 (ko) | 인증 방법, 보조 인증 컴포넌트, 관리 서버 및 컴퓨터 판독 가능 매체 | |
US20230396618A1 (en) | Token based identity verification and consent management | |
US10390229B1 (en) | Biometric subscriber account authentication | |
US12052246B2 (en) | Personal identity system | |
US20220393867A1 (en) | Techniques for user account and data recovery | |
US20240236063A1 (en) | Computing systems and methods for protecting application programming interfaces with two-factor authentication | |
US20230064529A1 (en) | User controlled identity provisioning for software applications | |
US20220019652A1 (en) | Flexible credential supported software service provisioning | |
WO2024151654A1 (en) | Computing systems and methods for protecting application programming interfaces with two-factor authentication | |
CN114266057A (zh) | 一种数据分发方法及*** |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref document number: 20217007876 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2020861986 Country of ref document: EP Effective date: 20210317 |
|
ENP | Entry into the national phase |
Ref document number: 2021516955 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |