Identifier acquisition method, apparatus, device and medium
Patent Information
- Application Number
- GB2025000811
- Authority / Receiving Office
- GB · GB
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2022-11-02
- Publication Date
- 2025-03-05
Abstract
Description
Identification acquisition method, device, equipment and medium Technical Field
[0001] The present invention relates to the field of computer technology, and in particular to an identification acquisition method, device, equipment and medium. Background Art
[0002] Microfrontends are a technology that aggregates multiple independent applications and provides a unified access point for accessing them. They are becoming increasingly popular in software development. The application that provides the unified access point is called the master application, and each independent application aggregated within the master application can be considered a slave application.
[0003] In the related art, data between the master application and the slave applications, as well as between the slave applications, are isolated from each other and cannot be shared, thereby making it impossible to perform comprehensive data analysis on the data of the master application and the slave applications.
[0004] Summary of the Invention
[0005] The present invention provides a method, device, equipment and medium for obtaining an identification to solve the deficiencies in the related art.
[0006] According to a first aspect of an embodiment of the present invention, a method for obtaining an identifier is provided, which is executed by an application management end. The method includes:
[0007] In response to receiving an authentication request from the main application client, if the identity token carried in the authentication request is verified, a first user identifier corresponding to the user information carried in the authentication request is sent to the main application client, where the first user identifier is a user identifier of the target user corresponding to the user information that has been registered in the main application client. The main application client is configured to send the first user identifier and the identity token to the micro-application client upon receiving the first user identifier, and the micro-application client is configured to send an identifier acquisition request to the main application management end based on the first user identifier and the identity token;
[0008] In response to receiving an identification acquisition request from the micro-application client, if the identity token carried in the identification acquisition request is verified, obtain a second user identification corresponding to the first user identification carried in the identification acquisition request, where the second user identification is a user identification of the target user registered in the micro-application client;
[0009] Send the second user identifier to the micro-application client.
[0010] The present invention is that when the application management end receives the identity authentication request from the main application client, if the identity token carried in the identity authentication request is verified, the application management end sends the first user identifier of the target user registered in the main application client corresponding to the user information carried in the identity authentication request to the main application client, so that the main application client can send the first user identifier and identity token to the micro-application client when receiving the first user identifier, so that the micro-application client can send an identifier acquisition request carrying the first user identifier and identity token to the micro-application client; when the application management end receives the identifier acquisition request, if the identity token is verified, the application management end obtains the second user identifier corresponding to the first user identifier in the micro-application client, and then sends the second user identifier to the micro-application client to realize the connection between the main application and micro-application user systems, so that the main application and the micro-application can realize data sharing based on the connected user system.
[0011] In some embodiments, the identity token includes at least signature information;
[0012] In response to receiving an identity authentication request from a primary application client, if the identity token carried in the identity authentication request is verified successfully, sending a first user identifier corresponding to the user information carried in the identity authentication request to the primary application client, including:
[0013] In response to receiving the identity authentication request from the primary application client, verifying the identity token based on signature information included in the identity token;
[0014] If the signature information is verified successfully, obtaining the first user identifier based on the user information carried in the identity authentication request;
[0015] Send the first user identifier to the primary application client.
[0016] In some embodiments, in response to receiving an authentication request from a primary application client, if the identity token carried in the authentication request is verified successfully, before sending the first user identifier corresponding to the user information carried in the authentication request to the primary application client, the method further includes at least one of the following:
[0017] In response to receiving an application registration request from the primary application client, generating a primary application identifier and a primary application key for the primary application client, and sending the primary application identifier and the primary application key to the primary application client;
[0018] In response to receiving the application registration request from the micro-application client, a micro-application identifier and a micro-application key are generated for the micro-application client, and the micro-application identifier and the micro-application key are sent to the micro-application client.
[0019] In some embodiments, in response to receiving an authentication request from a primary application client, if the identity token carried in the authentication request is verified successfully, before sending the first user identifier corresponding to the user information carried in the authentication request to the primary application client, the method further includes:
[0020] In response to receiving the first application verification request from the primary application client, verifying the legitimacy of the primary application client based on the primary application identifier and the primary application key carried in the first application verification request;
[0021] If the legitimacy verification of the main application client passes, an identity token is sent to the main application client; otherwise, a prompt message is sent to the main application client, where the prompt message is used to indicate that the legitimacy verification of the main application client has failed.
[0022] In some embodiments, if the primary application client passes the legitimacy verification, after sending the identity token to the primary application client, the method further includes:
[0023] In response to receiving the second application verification request from the micro-application client, verifying the primary application client's permission to use the micro-application client based on the micro-application identifier, micro-application key, primary application identifier, and identity token carried in the second application verification request;
[0024] If it is confirmed that the main application client has the authority to use the micro application client, a permission to use message is sent to the micro application client; otherwise, a prohibition to use message is sent to the micro application client.
[0025] In some embodiments, in response to receiving a second application verification request from the micro-application client, before verifying the primary application client's permission to use the micro-application client based on the micro-application identifier, micro-application key, primary application identifier, and identity token carried in the second application verification request, the method further includes:
[0026] In response to receiving the permission acquisition request from the main application client, the permission information of the main application client is set to have permission to use the micro application client.
[0027] According to a second aspect of an embodiment of the present invention, a method for obtaining an identifier is provided, which is executed by a main application client. The method includes:
[0028] Send an authentication request to the application management end, the authentication request carries the identity token and user information. The application management end is used to obtain the first user identifier corresponding to the user information if the identity token verification is successful. The first user identifier is the user identifier of the target user corresponding to the user information that has been registered in the main application client;
[0029] When the first user identifier is received, the first user identifier is sent to the micro-application client. When the first user identifier is received, the micro-application client sends an identifier acquisition request carrying the identity token and the first user identifier to the application management end. The identifier acquisition request is used to obtain the user identifier of the target user registered in the micro-application client.
[0030] The present invention enables the main application client to send an authentication request carrying an identity token and user information to the application management end, so that the application management end can obtain the first user identifier of the target user corresponding to the user information, which has been registered in the main application client, if the identity token is verified successfully, and thus return the first user identifier to the main application client; the main application client can send the first user identifier and identity token to the micro-application client when receiving the first user identifier, so that the micro-application client can send an identifier acquisition request carrying the identity token and the first user identifier to the application management end when receiving the first user identifier, so as to obtain the user identifier of the target user registered in the micro-application client through the identifier acquisition request, so as to realize the connection between the main application and the micro-application user systems, so that the main application and the micro-application can realize data sharing based on the connected user system.
[0031] In some embodiments, before sending the identity authentication request to the application management end, the method further includes:
[0032] Sending an application registration request to the application management end, where the application management end is configured to generate a primary application identifier and a primary application key for the primary application client in response to the application registration request;
[0033] Receive the primary application ID and primary application key returned by the application management end.
[0034] In some embodiments, before sending the identity authentication request to the application management end, the method further includes:
[0035] A first application verification request is sent to the application management end. The first application verification request carries the main application identifier and the main application key. The application management end is used to verify the legitimacy of the main application client based on the main application identifier and the main application key, and send an identity token to the main application client if the legitimacy verification of the main application client passes.
[0036] In some embodiments, after sending the first application verification request to the application management end, the method further includes:
[0037] Upon receiving the identity token, the main application identifier and identity token are sent to the micro-application client. The micro-application client is used to send a second verification request carrying the micro-application identifier, micro-application key, main application identifier and identity token to the main application management end. The main application management end is used to verify the main application client's permission to use the micro-application client based on the micro-application identifier, micro-application key, main application identifier and identity token, and return the verification result to the micro-application client.
[0038] In some embodiments, before sending the identity authentication request to the application management end, the method further includes:
[0039] A permission acquisition request is sent to the application management end, and the application management end is used to respond to the permission acquisition request and set the permission information of the main application client to have the permission to use the micro application client.
[0040] According to a third aspect of an embodiment of the present invention, a method for obtaining an identifier is provided, which is executed by a micro-application client. The method includes:
[0041] Receive a first user identifier sent by the main application client, where the first user identifier is a user identifier of a target user that has been registered in the main application client;
[0042] Send an identification acquisition request carrying the identity token and the first user identification to the application management end, where the identification acquisition request is used to obtain the second user identification of the target user that has been registered in the micro-application client;
[0043] Receive the second user identifier sent by the application management end.
[0044] The present invention receives the first user identifier of the target user registered in the main application client and sent by the micro-application client, thereby sending an identifier acquisition request carrying the identity token and the first user identifier to the application management end, so as to obtain the second user identifier of the target user registered in the micro-application client through the identifier acquisition request, so as to realize the connection between the main application and the micro-application user system, so that the main application and the micro-application can realize data sharing based on the connected user system.
[0045] In some embodiments, before receiving the first user identifier sent by the primary application client, the method further includes:
[0046] Send an application registration request to the application management end, and the application management end is used to generate a micro-application identifier and a micro-application key for the micro-application customer in response to the application registration request;
[0047] Receive the micro-application ID and micro-application key returned by the application management end.
[0048] In some embodiments, before receiving the first user identifier sent by the primary application client, the method further includes:
[0049] In response to receiving the main application identifier and identity token of the main application client, a second application verification request is sent to the application management end. The second application verification request carries the micro-application identifier, micro-application key, main application identifier and identity token. The application management end is used to verify the main application client's permission to use the micro-application client based on the micro-application identifier, micro-application key, main application identifier and identity token, and return the verification result to the micro-application client.
[0050] According to a fourth aspect of an embodiment of the present invention, there is provided an identification acquisition device, which is applied to an application management terminal, and the device includes:
[0051] A sending module is configured to, in response to receiving an authentication request from a main application client, send a first user identifier corresponding to the user information carried in the authentication request to the main application client if the identity token carried in the authentication request is verified successfully. The first user identifier is a user identifier of the target user corresponding to the user information that has been registered in the main application client. The main application client is configured to, upon receiving the first user identifier, send the first user identifier and the identity token to the micro-application client. The micro-application client is configured to send an identifier acquisition request to the main application management end based on the first user identifier and the identity token.
[0052] An acquisition module is configured to, in response to receiving an identification acquisition request from a micro-application client, acquire a second user identification corresponding to the first user identification carried in the identification acquisition request if the identity token carried in the identification acquisition request is verified successfully, where the second user identification is a user identification of the target user registered in the micro-application client;
[0053] The sending module is further used to send the second user identifier to the micro-application client.
[0054] In some embodiments, the identity token includes at least signature information;
[0055] The sending module is configured to, in response to receiving an authentication request from a primary application client and if the identity token carried in the authentication request is verified successfully, send a first user identifier corresponding to the user information carried in the authentication request to the primary application client, and to:
[0056] In response to receiving the identity authentication request from the primary application client, verifying the identity token based on signature information included in the identity token;
[0057] If the signature information is verified successfully, obtaining the first user identifier based on the user information carried in the identity authentication request;
[0058] Send the first user identifier to the primary application client.
[0059] In some embodiments, the apparatus further comprises:
[0060] A generating module, configured to generate a primary application identifier and a primary application key for the primary application client in response to receiving an application registration request from the primary application client;
[0061] The generation module is further configured to generate a micro-application identifier and a micro-application key for the micro-application client in response to receiving an application registration request from the micro-application client.
[0062] In some embodiments, the apparatus further comprises:
[0063] a verification module, configured to, in response to receiving a first application verification request from the primary application client, verify the legitimacy of the primary application client based on the primary application identifier and the primary application key carried in the first application verification request;
[0064] The sending module is also used to send an identity token to the main application client if the main application client passes the legitimacy verification. Otherwise, it sends a prompt message to the main application client, which is used to prompt that the main application client fails the legitimacy verification.
[0065] In some embodiments, the verification module is further configured to, in response to receiving a second application verification request from the micro-application client, verify the primary application client's permission to use the micro-application client based on the micro-application identifier, micro-application key, primary application identifier, and identity token carried in the second application verification request;
[0066] The sending module is further configured to send permission information to the micro-application client if it is confirmed that the main application client has the authority to use the micro-application client; otherwise, send prohibition information to the micro-application client.
[0067] In some embodiments, the apparatus further comprises:
[0068] The setting module is configured to, in response to receiving a permission acquisition request from the main application client, set the permission information of the main application client to have permission to use the micro application client.
[0069] According to a fifth aspect of an embodiment of the present invention, there is provided an identification acquisition device, which is applied to a main application client, and includes:
[0070] A sending module is used to send an authentication request to the application management end. The authentication request carries an identity token and user information. The application management end is used to obtain a first user identifier corresponding to the user information if the identity token verification is successful. The first user identifier is a user identifier of the target user corresponding to the user information that has been registered in the main application client;
[0071] The sending module is also used to send the first user identifier to the micro-application client when the first user identifier is received. The micro-application client is used to send an identifier acquisition request carrying the identity token and the first user identifier to the application management end when the first user identifier is received. The identifier acquisition request is used to obtain the user identifier of the target user registered in the micro-application client.
[0072] In some embodiments, the sending module is further configured to send an application registration request to the application management end, and the application management end is configured to generate a primary application identifier and a primary application key for the primary application client in response to the application registration request;
[0073] The device also includes:
[0074] The receiving module is used to receive the main application identifier and the main application key returned by the application management end.
[0075] In some embodiments, the sending module is also used to send a first application verification request to the application management end, where the first application verification request carries a main application identifier and a main application key. The application management end is used to verify the legitimacy of the main application client based on the main application identifier and the main application key, and to send an identity token to the main application client if the legitimacy verification of the main application client passes.
[0076] In some embodiments, the sending module is also used to send the main application identifier and identity token to the micro-application client when the identity token is received. The micro-application client is used to send a second verification request carrying the micro-application identifier, micro-application key, main application identifier and identity token to the main application management end. The main application management end is used to verify the main application client's permission to use the micro-application client based on the micro-application identifier, micro-application key, main application identifier and identity token, and return the verification result to the micro-application client.
[0077] In some embodiments, the sending module is further used to send a permission acquisition request to the application management end, and the application management end is used to respond to the permission acquisition request and set the permission information of the main application client to have the permission to use the micro application client.
[0078] According to a sixth aspect of an embodiment of the present invention, there is provided an identification acquisition device, which is applied to a micro-application client, and the device includes:
[0079] A receiving module, configured to receive a first user identifier sent by the main application client, where the first user identifier is a user identifier of a target user corresponding to the user information and registered in the main application client;
[0080] A sending module is used to send an identification acquisition request carrying an identity token and a first user identification to the application management end, where the identification acquisition request is used to obtain a second user identification registered by the target user in the micro-application client;
[0081] The receiving module is further configured to receive a second user identifier sent by the application management terminal.
[0082] In some embodiments, the sending module is further configured to send an application registration request to the application management end, and the application management end is configured to generate a micro-application identifier and a micro-application key for the micro-application client in response to the application registration request;
[0083] The receiving module is also used to receive the micro-application identifier and micro-application key returned by the application management end.
[0084] In some embodiments, the sending module is also used to send a second application verification request to the application management end in response to receiving the main application identifier and identity token of the main application client. The second application verification request carries the micro-application identifier, micro-application key, main application identifier and identity token. The application management end is used to verify the main application client's permission to use the micro-application client based on the micro-application identifier, micro-application key, main application identifier and identity token, and return the verification result to the micro-application client.
[0085] According to the seventh aspect of an embodiment of the present invention, a computing device is provided, which includes a memory, a processor, and a computer program stored in the memory and runnable on the processor, wherein when the processor executes the program, the operations performed by the identification acquisition method provided in the first aspect and any one of the first aspects are implemented.
[0086] According to an eighth aspect of an embodiment of the present invention, a computing device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the operations performed by the identification acquisition method provided in the second aspect and any one of the second aspects are implemented.
[0087] According to the ninth aspect of an embodiment of the present invention, a computing device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the operations performed by the identification acquisition method provided in the third aspect and any one of the third aspects are implemented.
[0088] According to the tenth aspect of an embodiment of the present invention, a computer-readable storage medium is provided, on which a program is stored, and the program is executed by a processor to perform the operations performed by the identification acquisition method provided in the above-mentioned first aspect and any one of the first aspects.
[0089] According to the eleventh aspect of an embodiment of the present invention, a computer-readable storage medium is provided, on which a program is stored, and the program is executed by a processor to perform the operations performed by the identification acquisition method provided in the second aspect and any one of the second aspects.
[0090] According to the twelfth aspect of an embodiment of the present invention, a computer-readable storage medium is provided, on which a program is stored, and the program is executed by a processor to perform the operations performed by the identification acquisition method provided in the third aspect and any one of the third aspects.
[0091] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention. BRIEF DESCRIPTION OF THE DRAWINGS
[0092] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.
[0093] FIG1 is a flow chart of a method for obtaining an identifier according to an embodiment of the present invention;
[0094] FIG2 is a flowchart illustrating a main application client registration process according to an embodiment of the present invention;
[0095] FIG3 is a flowchart of a micro-application client registration process according to an embodiment of the present invention;
[0096] FIG4 is a flowchart showing an initialization verification process of a main application client according to an embodiment of the present invention;
[0097] FIG5 is a flowchart of an initialization verification process of a micro-application client according to an embodiment of the present invention;
[0098] 6 is a flowchart showing a process of obtaining a first user identifier according to an embodiment of the present invention;
[0099] 7 is a flowchart showing a process of obtaining a second user identifier according to an embodiment of the present invention;
[0100] FIG8 is a block diagram of an identification acquisition device according to an embodiment of the present invention;
[0101] FIG9 is a block diagram of an identification acquisition device according to an embodiment of the present invention;
[0102] FIG10 is a block diagram of an identification acquisition device according to an embodiment of the present invention;
[0103] FIG11 is a schematic structural diagram of a computing device according to an embodiment of the present invention;
[0104] FIG12 is a schematic structural diagram of a computing device according to an embodiment of the present invention. DETAILED DESCRIPTION
[0105] Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. In the following description, when referring to the drawings, like numbers in different figures represent like or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present invention, as detailed in the appended claims.
[0106] The present invention provides an identification acquisition method for acquiring a first user identification of a corresponding target user registered in a main application client and a second user identification of the target user registered in a micro-application client based on user information, thereby connecting the main application and micro-application user systems, so that the main application and micro-application can realize data sharing based on the connected user systems.
[0107] Among them, the main application can be any type of application, such as instant messaging program, multimedia data processing program, shopping application, etc., and the micro application can be any type of customized application based on the web (Web) / mobile terminal. The micro application does not need to be downloaded from the application store, but can be directly embedded in the main application, so that the micro application can be called through the main application, and then the services provided by the micro application can be used.
[0108] Taking the main application as an instant messaging program as an example, the micro-application can be a game program, a medical service program, a government and enterprise information query program, etc. embedded in the instant messaging program. The present invention does not limit the application types of the main application and the micro-application.
[0109] After introducing the application scenarios of the present invention, the identification acquisition method provided by the present invention is introduced in detail below.
[0110] Referring to FIG. 1 , FIG. 1 is a flow chart of a method for obtaining an identifier according to an embodiment of the present invention. As shown in FIG. 1 , the method includes:
[0111] Step 101: The main application client sends an identity authentication request to the application management end. The identity authentication request carries an identity token and user information.
[0112] The user information may include the user's name, user ID number, contact information, etc. The present invention does not limit the specific content of the user information, but only needs to ensure that the user information is authorized by the user.
[0113] Step 102: In response to receiving the authentication request from the main application client, the application management end sends the first user identifier corresponding to the user information carried in the authentication request to the main application client if the identity token carried in the authentication request is verified successfully. The first user identifier is the user identifier of the target user corresponding to the user information that has been registered in the main application client.
[0114] Step 103: Upon receiving the first user identifier, the main application client sends the first user identifier to the micro application client.
[0115] Step 104: The micro-application client receives the first user identifier sent by the main application client.
[0116] Step 105: The micro-application client sends an identification acquisition request carrying the identity token and the first user identification to the application management end. The identification acquisition request is used to obtain the user identification of the target user registered in the micro-application client.
[0117] Step 106: In response to receiving the identification acquisition request from the micro-application client, the application management end obtains the second user identification corresponding to the first user identification carried in the identification acquisition request if the identity token carried in the identification request is verified successfully. The second user identification is the user identification of the target user registered in the micro-application client.
[0118] Step 107: The application management end sends the second user identifier to the micro-application client.
[0119] Step 108: The micro-application client receives the second user identifier sent by the application management end.
[0120] The present invention is achieved by having the main application client send an authentication request carrying an identity token and user information to the application management end, so that the application management end can obtain the first user identifier of the target user corresponding to the user information, which has been registered in the main application client, if the identity token verification is successful, and then return the first user identifier to the main application client, so that the main application client can send the first user identifier and identity token to the micro-application client when receiving the first user identifier, so that the micro-application client can send an identifier acquisition request carrying the first user identifier and identity token to the micro-application client; when the application management end receives the identifier acquisition request from the micro-application client, if the identity token verification is successful, it obtains the second user identifier corresponding to the first user identifier in the micro-application client, and then sends the second user identifier to the micro-application client, so that the micro-application client can obtain the second user identifier of the target user, which has been registered in the micro-application client, so as to realize the connection between the main application and micro-application user systems, so that the main application and micro-application can realize data sharing based on the connected user system.
[0121] After introducing the basic implementation process of the identification acquisition method of the present invention, various optional embodiments of the present invention are introduced below.
[0122] It should be noted that in order to achieve the connection between the main application and the micro-application user system through the solution provided by the above steps 101 to 107, the main application and the micro-application need to be registered in advance on the application management end, and the application management end must initialize and verify the main application and the micro-application. Only when the verification is passed can the main application and the micro-application user system be connected through steps 101 to 107.
[0123] First, let's introduce the registration process of the main application client and micro application client on the application management end:
[0124] For the registration process of the main application client, the main application client can send an application registration request to the application management end, and the application management end can receive the application registration request sent by the main application client. In response to receiving the application registration request from the main application client, the main application client generates a main application identifier and a main application key for the main application client, and sends the main application identifier (or main appid) and the main application key (or main appSerect) to the main application client. The main application client receives the main application identifier and the main application key returned by the application management end, and the registration of the main application client on the application management end can be realized.
[0125] For the registration process of the micro-application client, the micro-application client can send an application registration request to the application management end, and the application management end can receive the application registration request sent by the micro-application client. In response to receiving the application registration request from the micro-application client, the micro-application client generates a micro-application identifier (or micro-appid) and a micro-application key (or micro-appSerect) for the micro-application client, and sends the micro-application identifier and micro-application key to the micro-application client. The micro-application client receives the micro-application identifier and micro-application key returned by the application management end, and the registration of the micro-application client on the application management end can be realized.
[0126] It should be noted that both the main application ID and the micro-application ID can be generated based on the native 32-bit Universally Unique Identifier (UUID) of the Java programming language (Java).
[0127] In one possible implementation, a 32-bit UUID can be randomly generated. Since UUID is generally in hexadecimal, the UUID can be divided into 8 groups, each of 4 characters. Then, a modulo 62 operation is performed, and the result is used as an index to extract characters to obtain 8 characters, which can then be used as the application identifier.
[0128] The above is only an exemplary method for generating an application identifier. In other embodiments, other methods may be used to generate an application identifier, and the present invention is not limited thereto.
[0129] In addition, it should be noted that both the main application key and the micro-application key can be generated based on the application identifier and the UUID using a key generation algorithm. For example, the application key can be generated based on the application identifier and the UUID using the Secure Hash Algorithm 1 (SHA-1). Alternatively, other algorithms can be used to generate the application key, which is not limited in the present invention.
[0130] The above is only an exemplary method for generating an application key. In other embodiments, other methods may be used to generate an application key, and the present invention is not limited thereto.
[0131] It should be noted that after the application management end generates the main application identifier and main application key for the main application client, it can store the generated main application identifier and main application key so that the legitimacy of the main application client can be verified based on the stored main application identifier and main application key later; and, after the application management end generates the micro-application identifier and micro-application key for the micro-application client, it can store the generated micro-application identifier and micro-application key so that the legitimacy of the micro-application client can be verified based on the stored micro-application identifier and micro-application key later.
[0132] In addition, after the main application client is registered on the application management side, it can also apply for permission to use the micro application client on the application client.
[0133] In some embodiments, the main application client sends a permission acquisition request to the application management end. In response to receiving the permission acquisition request from the main application client, the application management end sets the permission information of the main application client to have the permission to use the micro application client.
[0134] In a possible implementation, the application management end may store the micro-application client in correspondence with the application identifier of the main application client that has the permission to use it, so that the permission information of the main application client can be set to have the permission to use the micro-application client.
[0135] It should be noted that the application management end may include a micro-application management platform and a main index platform. The above-mentioned process of generating application identifiers and application keys for the main application client and the micro-application client, and allocating usage rights of the micro-application client to the main application client can be performed by the micro-application management platform.
[0136] Refer to Figure 2, which is a flowchart of a main application client registration process according to an embodiment of the present invention. As shown in Figure 2, the main application client applies to register on the micro-application management platform. The micro-application management platform generates a main appid and a main appSecret for the main application client and returns them to the main application client. In addition, the main application client can also apply to the micro-application management platform for permission to use the micro-application client.
[0137] Refer to Figure 3, which is a flowchart of a micro-application client registration process according to an embodiment of the present invention. As shown in Figure 3, the micro-application client applies to register on the micro-application management platform, and the micro-application management platform generates a micro-appid and micro-appSecret for the micro-application client and returns them to the micro-application client.
[0138] After the application management end completes the registration and permission allocation of the main application client and the registration of the micro application client, it can initialize the verification of the main application client and the micro application client to verify the legitimacy of the main application client and the micro application client.
[0139] The following describes the initialization verification process of the main application client and micro application client on the application management side:
[0140] For the initialization verification process of the main application client on the application management end, the main application client sends a first application verification request carrying the main application identifier and the main application key to the application management end. In response to receiving the first application verification request from the main application client, the application management end verifies the legitimacy of the main application client based on the main application identifier and the main application key carried in the first application verification request; if the legitimacy verification of the main application client passes, the application management end sends an identity token to the main application client, otherwise, it sends a prompt message (such as an error code) to the main application client, and the prompt message is used to prompt that the legitimacy verification of the main application client has failed.
[0141] In one possible implementation, the application management end may compare the primary application identifier and primary application key carried in the first application verification request with the stored primary application identifier and primary application key. If the stored primary application identifier and primary application key contain the primary application identifier and primary application key carried in the first application verification request, it can be determined that the legitimacy verification of the primary application client has passed.
[0142] It should be noted that, when the legitimacy verification of the main application client is passed, the application management end can generate an identity token for the main application client and return the generated identity token to the main application client.
[0143] Optionally, a Java Web Token (JWT) may be used to generate an identity token. In addition, other methods may be used to generate an identity token, which is not limited in the present invention.
[0144] The identity token may include expiration time, user information, main application identifier and signature information. Optionally, the identity token may also include more or less content, which is not limited in the present invention.
[0145] It should be noted that after the application management end generates an identity token for the main application client, it can store the generated identity token so that the legitimacy of the micro-application client can be verified based on the stored identity token in the future.
[0146] The initialization verification process of the micro-application client on the application management side needs to be carried out after the legitimacy verification of the main application client has passed.
[0147] Upon receiving the identity token, the main application client sends the main application identifier and identity token to the micro-application client; in response to receiving the main application identifier and identity token from the main application client, the micro-application client sends a second application verification request carrying the micro-application identifier, micro-application key, main application identifier and identity token to the application management end; in response to receiving the second application verification request from the micro-application client, the application management end verifies the main application client's permission to use the micro-application client based on the micro-application identifier, micro-application key, main application identifier and identity token carried in the second application verification request; upon confirming that the main application client has the permission to use the micro-application client, the application management end sends permission information to the micro-application client, otherwise, it sends prohibition information to the micro-application client.
[0148] It should be noted that when the main application client sends the main application identifier and identity token to the micro-application client, it can pass the main application identifier and identity token to the software development kit (SDK) of the micro-application client, and the SDK of the micro-application client sends a second application verification request to the application management end.
[0149] In one possible implementation, after receiving the second application verification request, the application management end can compare the micro-application identifier, micro-application key and main application identifier carried in the second application verification request with the stored micro-application identifier, micro-application key and main application identifier, and verify the identity token based on the signature information included in the identity token. If the stored micro-application identifier, micro-application key and main application identifier contain the micro-application identifier, micro-application key and main application identifier carried in the second application verification request, and the signature information verification is passed, it can be determined that the legitimacy verification of the micro-application client has passed.
[0150] It should be noted that the above initialization verification process for the main application client and the micro-application client can be performed by the micro-application management platform.
[0151] Refer to Figure 4, which is a flowchart of the initialization verification process of a main application client according to an embodiment of the present invention. As shown in Figure 4, the main application client can send a first application verification request carrying the main appid and the main appSecret to the micro-application management platform. When the main appid and the main appSecret are verified (that is, the verification is successful), the micro-application management platform can return an identity token (that is, Token) to the main application client.
[0152] Refer to Figure 5, which is a flowchart of the initialization verification process of a micro-application client according to an embodiment of the present invention. As shown in Figure 5, the main application client can send a Token to the micro-application client, and the micro-application client can send a second application verification request carrying the Token and the micro-appid to the micro-application management platform. If the legitimacy verification of the Token and the micro-appid is passed, the micro-application management platform can return the verification pass information to the micro-application client. If the legitimacy verification of the Token and the micro-appid fails, the micro-application management platform can return an error code to the micro-application client.
[0153] After completing the initialization and verification process of the main application client and the micro application client through the above process, you can continue with the subsequent operation and the process of connecting to the user system.
[0154] In some embodiments, in response to receiving an authentication request from a primary application client, when the identity token carried in the authentication request is verified successfully, the application management end sends the first user identifier corresponding to the user information carried in the authentication request to the primary application client, which can be implemented as follows:
[0155] In response to receiving an authentication request from the main application client, the identity token is verified based on the signature information included in the identity token; if the signature information verification is successful, the first user identifier is obtained based on the user information carried in the authentication request; and the first user identifier is sent to the main application client.
[0156] It should be noted that the process of running and connecting the user system can be achieved based on the interaction between the micro-application management platform and the main index platform.
[0157] In one possible implementation, the main application client can send an authentication request carrying an identity token and user information to the main index platform on the premise that the initialization verification is passed. The main index platform requests the micro-application management platform to verify the legitimacy of the main application client. The micro-application management platform returns the legitimacy verification result of the main application client to the main index platform. After the legitimacy verification of the main application client is passed, the main index platform queries the first user identifier (denoted as globalId) registered in the main application client for the target user corresponding to the user information carried in the authentication request. After the main application client obtains the first user identifier, it passes it to the micro-application client. The micro-application client sends an identifier acquisition request carrying the first user representation and the identity token of the main application client to the main index platform. After receiving the identity token and the first user identifier, the main index platform sends a request to the micro-application management platform. The micro-application management platform requests to verify the legitimacy of the identity token, and the micro-application management platform returns the legitimacy verification result of the identity token to the main index platform. When the legitimacy verification of the identity token passes, the main index platform returns the second user ID of the target user registered in the micro-application client to the micro-application client. At this point, based on the same user information, the first user ID of the target user in the main application client and the second user ID of the target user in the micro-application client can be obtained. Furthermore, the user information and user data of the target user in the main application client can be obtained based on the first user ID, and the user information and user data of the target user in the micro-application client can be obtained based on the second user ID. The user systems of the main application and the micro-application are connected through the main index platform and the micro-application management platform, and user information and data can be shared between the main application and the micro-application.
[0158] Refer to Figure 6, which is a flowchart of a process for obtaining a first user identifier according to an embodiment of the present invention. As shown in Figure 6, the main application client sends an authentication request carrying a Token and user information to the main index platform. The main index platform passes the Token to the micro-application management platform. The micro-application management platform verifies the legitimacy of the Token. If the legitimacy verification passes, the micro-application management platform returns the verification pass information to the main index platform. When the main index platform receives the verification pass information, it can return the first user identifier to the main application client. If the legitimacy verification fails, the micro-application management platform returns an error code to the main index platform. When the main index platform receives the error code, it can return the error code to the main application client.
[0159] Refer to Figure 7, which is a flowchart of a process for obtaining a second user identifier according to an embodiment of the present invention. As shown in Figure 7, the micro-application client sends an identifier acquisition request carrying a Token and a first user identifier to the main index platform. The main index platform passes the Token to the micro-application management platform, and the micro-application management platform verifies the legitimacy of the Token. If the legitimacy verification passes, the micro-application management platform returns a verification pass message to the main index platform. Upon receiving the verification pass message, the main index platform can return the second user identifier to the micro-application client. If the legitimacy verification fails, the micro-application management platform returns an error code to the main index platform. Upon receiving the error code, the main index platform can return an error code to the micro-application client.
[0160] Corresponding to the aforementioned method embodiments, the present invention also provides embodiments of corresponding identification acquisition apparatus and computing equipment used therein.
[0161] As shown in FIG8 , FIG8 is a block diagram of an identification acquisition device according to an embodiment of the present invention, which is applied to an application management end. The device includes:
[0162] The sending module 801 is configured to, in response to receiving an authentication request from a main application client, send a first user identifier corresponding to the user information carried in the authentication request to the main application client if the identity token carried in the authentication request is verified successfully. The first user identifier is a user identifier of the target user corresponding to the user information that has been registered in the main application client. The main application client is configured to send the first user identifier and the identity token to the micro-application client upon receiving the first user identifier. The micro-application client is configured to send an identifier acquisition request to the main application management terminal based on the first user identifier and the identity token.
[0163] An acquisition module 802 is configured to, in response to receiving an identification acquisition request from a micro-application client, acquire a second user identification corresponding to the first user identification carried in the identification acquisition request if the identity token carried in the identification acquisition request is verified successfully, where the second user identification is a user identification of the target user registered in the micro-application client;
[0164] The sending module 801 is further configured to send the second user identifier to the micro-application client.
[0165] In some embodiments, the identity token includes at least signature information;
[0166] The sending module 801 is configured to, in response to receiving an authentication request from a primary application client and if the identity token carried in the authentication request is verified successfully, send a first user identifier corresponding to the user information carried in the authentication request to the primary application client, and to:
[0167] In response to receiving the identity authentication request from the primary application client, verifying the identity token based on signature information included in the identity token;
[0168] If the signature information is verified successfully, obtaining the first user identifier based on the user information carried in the identity authentication request;
[0169] Send the first user identifier to the primary application client.
[0170] In some embodiments, the apparatus further comprises:
[0171] A generating module, configured to generate a primary application identifier and a primary application key for the primary application client in response to receiving an application registration request from the primary application client;
[0172] The generation module is further configured to generate a micro-application identifier and a micro-application key for the micro-application client in response to receiving an application registration request from the micro-application client.
[0173] In some embodiments, the apparatus further comprises:
[0174] a verification module, configured to, in response to receiving a first application verification request from the primary application client, verify the legitimacy of the primary application client based on the primary application identifier and the primary application key carried in the first application verification request;
[0175] The sending module 801 is further used to send an identity token to the main application client if the main application client passes the legitimacy verification; otherwise, send a prompt message to the main application client, where the prompt message is used to prompt that the main application client fails the legitimacy verification.
[0176] In some embodiments, the verification module is further configured to, in response to receiving a second application verification request from the micro-application client, verify the primary application client's permission to use the micro-application client based on the micro-application identifier, micro-application key, primary application identifier, and identity token carried in the second application verification request;
[0177] The sending module 801 is further configured to send permission information to the micro-application client if it is confirmed that the main application client has the authority to use the micro-application client; otherwise, send prohibition information to the micro-application client.
[0178] In some embodiments, the apparatus further comprises:
[0179] The setting module is configured to, in response to receiving a permission acquisition request from the main application client, set the permission information of the main application client to have permission to use the micro application client.
[0180] As shown in FIG9 , FIG9 is a block diagram of an identification acquisition device according to an embodiment of the present invention, which is applied to a main application client, and the device includes:
[0181] A sending module 901 is configured to send an authentication request to the application management terminal. The authentication request carries an identity token and user information. The application management terminal is configured to obtain a first user identifier corresponding to the user information if the identity token is successfully verified. The first user identifier is a user identifier of the target user corresponding to the user information that has been registered in the main application client.
[0182] The sending module 901 is also used to send the first user identifier to the micro-application client when the first user identifier is received. The micro-application client is used to send an identifier acquisition request carrying the identity token and the first user identifier to the application management end when the first user identifier is received. The identifier acquisition request is used to obtain the user identifier of the target user registered in the micro-application client.
[0183] In some embodiments, the sending module 901 is further configured to send an application registration request to the application management end, and the application management end is configured to generate a primary application identifier and a primary application key for the primary application client in response to the application registration request;
[0184] The device also includes:
[0185] The receiving module is used to receive the main application identifier and the main application key returned by the application management end.
[0186] In some embodiments, the sending module 901 is also used to send a first application verification request to the application management end, where the first application verification request carries a main application identifier and a main application key. The application management end is used to verify the legitimacy of the main application client based on the main application identifier and the main application key, and to send an identity token to the main application client if the legitimacy verification of the main application client passes.
[0187] In some embodiments, the sending module 901 is also used to send the main application identifier and identity token to the micro-application client when the identity token is received. The micro-application client is used to send a second verification request carrying the micro-application identifier, micro-application key, main application identifier and identity token to the main application management end. The main application management end is used to verify the main application client's permission to use the micro-application client based on the micro-application identifier, micro-application key, main application identifier and identity token, and return the verification result to the micro-application client.
[0188] In some embodiments, the sending module 901 is further used to send a permission acquisition request to the application management end, and the application management end is used to respond to the permission acquisition request and set the permission information of the main application client to have the permission to use the micro application client.
[0189] As shown in FIG10 , FIG10 is a block diagram of an identification acquisition device according to an embodiment of the present invention, which is applied to a micro-application client. The device includes:
[0190] Receiving module 1001, configured to receive a first user identifier sent by a main application client, where the first user identifier is a user identifier of a target user corresponding to the user information, which has been registered in the main application client;
[0191] The sending module 1002 is used to send an identification acquisition request carrying the identity token and the first user identification to the application management end, where the identification acquisition request is used to obtain the second user identification of the target user that has been registered in the micro-application client;
[0192] The receiving module 1001 is further configured to receive a second user identifier sent by the application management terminal.
[0193] In some embodiments, the sending module 1002 is further configured to send an application registration request to the application management end, and the application management end is configured to generate a micro-application identifier and a micro-application key for the micro-application client in response to the application registration request;
[0194] The receiving module 1001 is further configured to receive the micro-application identifier and micro-application key returned by the application management end.
[0195] In some embodiments, the sending module 1002 is also used to send a second application verification request to the application management end in response to receiving the main application identifier and identity token of the main application client. The second application verification request carries the micro-application identifier, micro-application key, main application identifier and identity token. The application management end is used to verify the main application client's permission to use the micro-application client based on the micro-application identifier, micro-application key, main application identifier and identity token, and return the verification result to the micro-application client.
[0196] The implementation process of the functions and effects of each module in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, and will not be repeated here.
[0197] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to the partial description of the method embodiments. The device embodiments described above are merely illustrative, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this specification. A person of ordinary skill in the art can understand and implement it without paying any creative work.
[0198] The present invention also provides a computing device, see Figure 11, which is a schematic diagram of the structure of a computing device according to an embodiment of the present invention. The application management platform can run on this computing device, and the computing device can be a server, multiple servers, a server cluster, etc. As shown in Figure 11, the computing device includes a processor 1110, a memory 1120, and a network interface 1130. The memory 1120 is used to store computer instructions that can be run on the processor 1110. The processor 1110 is used to implement the identification acquisition method provided by any embodiment of the present invention when executing computer instructions. The network interface 1130 is used to implement input and output functions. In more possible implementations, the computing device may also include other hardware, which is not limited by the present invention.
[0199] The present invention also provides a computing device, see Figure 12, which is a schematic diagram of the structure of a computing device according to an embodiment of the present invention. Both the main application client and the micro-application client can run on the computing device, and the computing device can be a desktop computer, a portable computer, a notebook computer, a smart phone, a tablet computer, etc. As shown in Figure 12, the computing device includes a processor 1210, a memory 1220 and a network interface 1230. The memory 1220 is used to store computer instructions that can be run on the processor 1210. The processor 1210 is used to implement the identification acquisition method provided by any embodiment of the present invention when executing the computer instructions. The network interface 1230 is used to implement input and output functions. In more possible implementations, the computing device may also include other hardware, which is not limited by the present invention.
[0200] The present invention also provides a computer-readable storage medium, which can be in various forms. For example, in different examples, the computer-readable storage medium can be: RAM (Random Access Memory), volatile memory, non-volatile memory, flash memory, storage drive (such as a hard disk drive), solid-state drive, any type of storage disk (such as a CD, DVD, etc.), or similar storage medium, or a combination thereof. In particular, the computer-readable medium can also be paper or other suitable medium capable of printing programs. A computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor as shown in Figure 11 or Figure 12, the identification acquisition method provided by any embodiment of the present invention is implemented.
[0201] The present invention further provides a computer program product, including a computer program. When the computer program is executed by a processor as shown in FIG. 11 or FIG. 12 , the identification acquisition method provided in any embodiment of the present invention is implemented.
[0202] It should be understood by those skilled in the art that one or more embodiments of this specification may be provided as a method, apparatus, computing device, computer-readable storage medium, or computer program product. Thus, one or more embodiments of this specification may take the form of a fully hardware embodiment, a fully software embodiment, or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0203] The various embodiments in this specification are described in a progressive manner. Similar portions between the various embodiments can be referenced to each other. Each embodiment focuses on the differences between the other embodiments. In particular, the embodiments corresponding to the computing device are generally similar to the method embodiments, so the description is relatively simple. For relevant portions, refer to the description of the method embodiments.
[0204] The foregoing description of specific embodiments of this specification is intended to be a description of other embodiments. Other embodiments are within the scope of the present invention. In some cases, the actions or steps described herein may be performed in an order different from that shown in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0205] Embodiments of the subject matter and functional operations described in this specification may be implemented in the following: digital electronic circuits, tangibly embodied computer software or firmware, computer hardware including the structures disclosed in this specification and their structural equivalents, or a combination of one or more of them. Embodiments of the subject matter described in this specification may be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a tangible, non-transitory program carrier to be executed by an identification acquisition device or to control the operation of an identification acquisition device. Alternatively or additionally, the program instructions may be encoded on an artificially generated propagation signal, such as a machine-generated electrical, optical, or electromagnetic signal, which is generated to encode information and transmit it to a suitable receiver device for execution by the identification acquisition device. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of them.
[0206] The processes and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform the corresponding functions by operating on input data and generating output. The processes and logic flows can also be performed by, and the apparatus can be implemented as, special purpose logic circuitry, such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC).
[0207] Computers suitable for executing computer programs include, for example, general-purpose and / or special-purpose microprocessors, or any other type of central processing unit. Typically, the central processing unit will receive instructions and data from a read-only memory and / or random access memory. The basic components of a computer include a central processing unit for implementing or executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices for storing data, such as magnetic disks, magneto-optical disks, or optical disks, or the computer will be operably coupled to such a mass storage device to receive data from it or transmit data to it, or both. However, a computer does not necessarily have such a device. In addition, a computer can be embedded in another device, such as a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable storage device such as a universal serial bus (USB) flash drive, to name a few.
[0208] Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and storage devices, including, for example, semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices), magnetic disks (e.g., internal hard disks or removable disks), magneto-optical disks, and CD ROM and DVD-ROM disks. The processor and memory can be supplemented by, or incorporated in, special purpose logic circuitry.
[0209] Although this specification includes many specific implementation details, these should not be interpreted as limiting the scope of any invention or the scope of protection claimed, but are mainly used to describe the features of specific embodiments of specific inventions. Certain features described in multiple embodiments within this specification may also be implemented in combination in a single embodiment. On the other hand, the various features described in a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination. In addition, although features may work in certain combinations as described above and even initially claimed as such, one or more features from the claimed combination may be removed from the combination in some cases, and the claimed combination may point to a sub-combination or a variation of the sub-combination.
[0210] Similarly, although operations are depicted in a particular order in the accompanying drawings, this should not be understood as requiring that these operations be performed in the particular order shown or performed sequentially, or that all illustrated operations be performed to achieve the desired results. In some cases, multitasking and parallel processing may be advantageous. In addition, the separation of various system modules and components in the above-described embodiments should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product, or packaged into multiple software products.
[0211] Thus, specific embodiments of the subject matter have been described. Other embodiments are within the scope of the present invention. In some cases, the actions described herein can be performed in a different order and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order or sequential sequence shown to achieve the desired results. In some implementations, multitasking and parallel processing may be advantageous.
[0212] Those skilled in the art will readily appreciate other embodiments of the present invention after considering the present invention and practicing the invention claimed herein. This specification is intended to cover any variations, uses, or adaptations of the present invention that follow the general principles of this specification and include common knowledge or customary techniques in the art that are not claimed herein. That is, this specification is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and variations may be made without departing from the scope thereof.
[0213] The above description is only an optional embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.
Claims
1. A method for obtaining an identifier, characterized in that: Executed by the application management end, the method includes: In response to receiving an authentication request from a main application client, if the identity token carried in the authentication request is verified, sending a first user identifier corresponding to the user information carried in the authentication request to the main application client, where the first user identifier is a user identifier of a target user corresponding to the user information that has been registered in the main application client. The main application client is configured to send the first user identifier and the identity token to the micro-application client upon receiving the first user identifier, and the micro-application client is configured to send an identifier acquisition request to the main application management end based on the first user identifier and the identity token; In response to receiving an identification acquisition request from a micro-application client, if the identity token carried in the identification acquisition request is verified, obtaining a second user identification corresponding to the first user identification carried in the identification acquisition request, where the second user identification is a user identification of the target user registered in the micro-application client; Send the second user identifier to the micro-application client.
2. The method according to claim 1, characterized in that The identity token includes at least signature information; The step of: in response to receiving an identity authentication request from a primary application client, sending a first user identifier corresponding to user information carried in the identity authentication request to the primary application client if the identity token carried in the identity authentication request passes verification, including: In response to receiving an identity authentication request from the primary application client, verifying the identity token based on signature information included in the identity token; If the signature information is verified successfully, obtaining the first user identifier based on the user information carried in the identity authentication request; Send the first user identifier to the primary application client.
3. The method according to claim 1, characterized in that In response to receiving the identity authentication request from the primary application client, if the identity token carried in the identity authentication request is verified successfully, before sending the first user identifier corresponding to the user information carried in the identity authentication request to the primary application client, the method further includes at least one of the following: In response to receiving the application registration request from the primary application client, generating a primary application identifier and a primary application key for the primary application client, and sending the primary application identifier and the primary application key to the primary application client; In response to receiving the application registration request from the micro-application client, a micro-application identifier and a micro-application key are generated for the micro-application client, and the micro-application identifier and the micro-application key are sent to the micro-application client.
4. The method according to claim 3, characterized in that In response to receiving the identity authentication request from the primary application client, if the identity token carried in the identity authentication request is verified successfully, before sending the first user identifier corresponding to the user information carried in the identity authentication request to the primary application client, the method further includes: In response to receiving the first application verification request from the primary application client, verifying the legitimacy of the primary application client based on the primary application identifier and the primary application key carried in the first application verification request; If the legitimacy verification of the main application client passes, an identity token is sent to the main application client; otherwise, a prompt message is sent to the main application client, where the prompt message is used to prompt that the legitimacy verification of the main application client has failed.
5. The method according to claim 4, characterized in that When the legitimacy verification of the primary application client passes, after sending the identity token to the primary application client, the method further includes: In response to receiving a second application verification request from the micro-application client, verifying the master application client's permission to use the micro-application client based on the micro-application identifier, micro-application key, master application identifier, and identity token carried in the second application verification request; If it is confirmed that the main application client has the authority to use the micro-application client, permission information is sent to the micro-application client; otherwise, prohibition information is sent to the micro-application client.
6. The method according to claim 5, characterized in that In response to receiving the second application verification request from the micro-application client, before verifying the primary application client's permission to use the micro-application client based on the micro-application identifier, micro-application key, primary application identifier, and identity token carried in the second application verification request, the method further includes: In response to receiving the permission acquisition request from the main application client, the permission information of the main application client is set to have permission to use the micro-application client.
7. A method for obtaining an identifier, characterized in that: Executed by the main application client, the method includes: Send an authentication request to the application management end, the authentication request carrying an identity token and user information, and the application management end is used to obtain a first user identifier corresponding to the user information if the identity token verification is successful, where the first user identifier is a user identifier of the target user corresponding to the user information that has been registered in the main application client; Upon receiving the first user identifier, the first user identifier is sent to the micro-application client. The micro-application client is used to send an identifier acquisition request carrying the identity token and the first user identifier to the application management end upon receiving the first user identifier. The identifier acquisition request is used to obtain the user identifier of the target user registered in the micro-application client.
8. The method according to claim 7, characterized in that Before sending the identity authentication request to the application management end, the method further includes: Sending an application registration request to the application management end, wherein the application management end is configured to generate a primary application identifier and a primary application key for the primary application client in response to the application registration request; Receive the main application identifier and the main application key returned by the application management end.
9. The method according to claim 7, characterized in that Before sending the identity authentication request to the application management end, the method further includes: A first application verification request is sent to the application management end, where the first application verification request carries the main application identifier and the main application key. The application management end is used to verify the legitimacy of the main application client based on the main application identifier and the main application key, and to send an identity token to the main application client if the legitimacy verification of the main application client passes.
10. The method according to claim 9, characterized in that After sending the first application verification request to the application management end, the method further includes: Upon receiving the identity token, the main application identifier and the identity token are sent to the micro-application client, and the micro-application client is used to send a second verification request carrying the micro-application identifier, micro-application key, main application identifier and identity token to the main application management end. The main application management end is used to verify the main application client's permission to use the micro-application client based on the micro-application identifier, the micro-application key, the main application identifier and the identity token, and return the verification result to the micro-application client.
11. The method according to claim 7, characterized in that Before sending the identity authentication request to the application management end, the method further includes: A permission acquisition request is sent to the application management end, and the application management end is used to set the permission information of the main application client to have the permission to use the micro-application client in response to the permission acquisition request.
12. A method for obtaining an identifier, characterized in that: Executed by the micro-application client, the method includes: Receiving a first user identifier sent by a main application client, where the first user identifier is a user identifier of a target user registered in the main application client; Sending an identification acquisition request carrying an identity token and the first user identification to the application management end, wherein the identification acquisition request is used to obtain the second user identification of the target user registered in the micro-application client; Receive the second user identifier sent by the application management end.
13. The method according to claim 12, characterized in that Before receiving the first user identifier sent by the main application client, the method further includes: Sending an application registration request to the application management end, wherein the application management end is used to generate a micro-application identifier and a micro-application key for the micro-application client in response to the application registration request; Receive the micro-application identifier and the micro-application key returned by the application management end.
14. The method according to claim 13, characterized in that Before receiving the first user identifier sent by the main application client, the method further includes: In response to receiving the main application identifier and identity token of the main application client, a second application verification request is sent to the application management end, and the second application verification request carries the micro-application identifier, the micro-application key, the main application identifier and the identity token. The application management end is used to verify the main application client's permission to use the micro-application client based on the micro-application identifier, the micro-application key, the main application identifier and the identity token, and return the verification result to the micro-application client.
15. An identification acquisition device, characterized in that: Executed by the application management end, the device includes: A sending module, configured to, in response to receiving an authentication request from a main application client, send a first user identifier corresponding to the user information carried in the authentication request to the main application client if the identity token carried in the authentication request is verified successfully, wherein the first user identifier is a user identifier of a target user corresponding to the user information that has been registered in the main application client, and the main application client is configured to, upon receiving the first user identifier, send the first user identifier and the identity token to the micro-application client, and the micro-application client is configured to send an identifier acquisition request to the main application management end based on the first user identifier and the identity token; An acquisition module, configured to, in response to receiving an identification acquisition request from a micro-application client, acquire, when the identity token carried in the identification acquisition request is verified, a second user identification corresponding to the first user identification carried in the identification acquisition request, where the second user identification is a user identification of the target user registered in the micro-application client; The sending module is further configured to send the second user identifier to the micro-application client.
16. An identification acquisition device, characterized in that: Executed by the main application client, the device includes: A sending module, configured to send an authentication request to an application management terminal, the authentication request carrying an identity token and user information. The application management terminal is configured to obtain a first user identifier corresponding to the user information if the identity token is verified successfully, the first user identifier being a user identifier of a target user corresponding to the user information that has been registered in the primary application client; The sending module is also used to send the first user identifier to the micro-application client when the first user identifier is received. The micro-application client is used to send an identifier acquisition request carrying the identity token and the first user identifier to the application management end when the first user identifier is received. The identifier acquisition request is used to obtain the user identifier of the target user registered in the micro-application client.
17. An identification acquisition device, characterized in that: Executed by the micro-application client, the device includes: A receiving module, configured to receive a first user identifier sent by a main application client, where the first user identifier is a user identifier of a target user corresponding to the user information, which has been registered in the main application client; A sending module, configured to send an identification acquisition request carrying an identity token and the first user identification to the application management end, wherein the identification acquisition request is used to obtain the second user identification of the target user registered in the micro-application client; The receiving module is further configured to receive the second user identifier sent by the application management terminal.
18. A computing device, characterized in that The computing device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the operations performed by the identification acquisition method according to any one of claims 1 to 14 when executing the program.
19. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a program, and the processor executes the operations performed by the identification acquisition method according to any one of claims 1 to 14 through the program.