Product registration management method, device, computer equipment and storage medium

Abstract

The present invention provides a product login management method, device, computer equipment and storage medium, the method comprising the following steps: a server receives a user login request sent by a client; the login request contains a unique user identifier; based on the login record of the user identifier, determines whether to allow the user login request; if it is determined that the user login request is allowed, the server receives a product login request sent by the client; the product login request contains a unique product mnemonic identifier and a product group identifier; the product mnemonic identifier is used to uniquely identify the product, and the product group identifier is used to identify the group to which the product belongs; based on the login record of the product mnemonic identifier and the product group identifier, determines whether to allow the product login request; if it is determined that the product login request is allowed, log in to the product.

Description

Technical Field

[0001] The present invention relates to the field of cloud authorization technology, and in particular to a product login management method, device, computer equipment and storage medium. Background Art

[0002] Cloud authorization product login usually refers to a specific user account first logging into the cloud authorization platform, and then further accessing different products in the cloud authorization platform. The cloud authorization platform can be an online access server developed by an enterprise that contains multiple products, and the products can be software used to implement different functions, such as product A that implements the drawing function, product B that implements the format conversion function, and product C that implements the automatic beautification function. At present, the management rules of different cloud authorization platforms for user login restrictions and product login restrictions are relatively confusing. For example, the same user account is allowed to log in on a limited number of different devices at the same time, the same user account is only allowed to log in on one device at the same time, and product A and product B are not allowed to log in on different devices at the same time. Because different enterprises have different specific login management rules, a large amount of code needs to be written according to different login management rules each time a cloud authorization platform is developed, which seriously affects the development efficiency of the cloud authorization platform. Summary of the invention

[0003] The purpose of the present invention is to provide a technical solution that can uniformly perform structured design on different login management rules in a cloud authorization platform, so as to solve the above-mentioned problems existing in the prior art.

[0004] To achieve the above object, the present invention provides a product registration management method, comprising the following steps:

[0005] The server receives a user login request sent by the client; the login request includes a unique user identifier;

[0006] Determining whether to allow the user login request according to the login record of the user identification;

[0007] In the case of determining that the user login request is allowed, the server receives a product login request sent by the client; the product login request includes a unique product mnemonic identifier and a product group identifier; the product mnemonic identifier is used to uniquely identify the product, and the product group identifier is used to identify the group to which the product belongs;

[0008] Determining whether to allow the product login request according to the login record of the product mnemonic identifier and the product group identifier;

[0009] If it is determined that the product login request is allowed, the product is logged in.

[0010] According to the product login management method provided by the present invention, the step of determining whether to allow the user login request based on the login record of the user identification includes:

[0011] Using the user identifier as a keyword, searching a login data table; the login data table contains a correspondence between the user identifier and the login identifier; the login identifier is used to uniquely characterize each user login behavior;

[0012] Obtaining the number of first login identifiers corresponding to the user identifier;

[0013] Whether to allow the user login request is determined according to the relationship between the number of the first login identifiers and a preset first threshold.

[0014] According to the product login management method provided by the present invention, the login request also includes an environment identifier; the environment identifier is used to uniquely represent the virtual system currently running by the user;

[0015] The step of determining whether to allow the user login request according to the login record of the user identification further comprises:

[0016] When the number of the first login identifiers is less than the first threshold, acquiring the number of first environment identifiers corresponding to the first login identifiers from the login data table;

[0017] When the number of the first environment identifiers is less than a preset second threshold, the user login request is allowed.

[0018] According to the product login management method provided by the present invention, the step of determining whether to allow the product login request based on the login record of the product mnemonic identifier and the product group identifier includes:

[0019] Determining whether the product belongs to a mutually exclusive group according to the product group identifier;

[0020] In the case where the product belongs to a mutually exclusive group, searching the login data table to determine whether the login data table contains a second login identifier corresponding to the product mnemonic identifier and a third login identifier corresponding to other mnemonic identifiers; the other mnemonic identifiers are other identifiers having the same product group identifier as the product mnemonic identifier;

[0021] Determine whether to allow the product login request according to the number of the second login identifiers and the number of the third login identifiers.

[0022] According to the product login management method provided by the present invention, the step of determining whether to allow the product login request according to the number of the second login identifiers and the number of the third login identifiers includes:

[0023] Determining whether the number of the second login identifiers is less than a preset third threshold;

[0024] In the case where the number of the second login identifiers is less than the third threshold, determining whether the third login identifier is zero;

[0025] When the third login identifier is zero, the product login request is allowed.

[0026] According to the product login management method provided by the present invention, the step of determining whether to allow the product login request according to the number of the second login identifiers and the number of the third login identifiers further includes:

[0027] When the third login identifier is not zero, receiving a logoff request for the other mnemonic identifier sent by the client;

[0028] According to the offline request, the third login identifier is deleted from the login data table.

[0029] According to the product login management method provided by the present invention, the step of logging in the product when login is allowed includes:

[0030] Randomly generate a login ID that uniquely represents the current login behavior;

[0031] A login data table is created according to the login identifier, wherein the login data table contains the association relationship between the user identifier and the login identifier, the association relationship between the product mnemonic identifier and the login identifier, and the association relationship between the environment identifier and the login identifier.

[0032] To achieve the above object, the present invention provides a product registration management device, comprising:

[0033] A user login request module, adapted for the server to receive a user login request sent by a client; the login request includes a unique user identifier;

[0034] A user login determination module, adapted to determine whether to allow the user login request according to the login record of the user identification;

[0035] A product login request module, adapted for, in the case where it is determined that the user login request is allowed, the server receiving the product login request sent by the client; the product login request includes a unique product mnemonic identifier and a product group identifier; the product mnemonic identifier is used to uniquely identify the product, and the product group identifier is used to identify the group to which the product belongs;

[0036] A product login determination module, adapted to determine whether to allow the product login request according to the login record of the product mnemonic identifier and the product group identifier;

[0037] The product login module is adapted to log in the product if it is determined that the product login request is allowed.

[0038] To achieve the above objectives, the present invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the computer program.

[0039] To achieve the above object, the present invention also provides a computer-readable storage medium on which a computer program is stored, and the computer program implements the steps of the above method when executed by a processor.

[0040] The product login management method, device, computer equipment and storage medium provided by the present invention provide a universal product login management solution for different constraint rules. The present invention defines rule factors corresponding to different login constraint conversions and a combination method of rule factors. First, it is determined whether to allow login of a specific user ID based on the association between the user ID and the login record; on this basis, it is determined whether to allow login of a specific product based on the association between the product mnemonic ID and the login record. In this way, corresponding login constraint rules can be set according to different enterprise needs, so as to flexibly decide the login restriction solutions for different products in the cloud authorization platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 A flowchart of a first embodiment of a method for managing product login of the present invention;

[0042] Figure 2 This is a schematic flow chart of determining whether to allow a user to log in according to the first embodiment of the present invention;

[0043] Figure 3 This is a schematic flow chart of determining a product registration request according to Embodiment 1 of the present invention;

[0044] Figure 4 A schematic diagram of a program module of a first embodiment of a management device for product login of the present invention;

[0045] Figure 5 This is a schematic diagram of the hardware structure of the first embodiment of the product login management device of the present invention. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical scheme and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0047] Embodiment 1

[0048] See also Figure 1 This embodiment proposes a product login management method, comprising the following steps:

[0049] S100: The server receives a user login request sent by the client; the login request includes a unique user identifier.

[0050] This embodiment is applicable to the client and server mode. The user can access the cloud authorization platform on the server side through the web address or APP in the client and send a corresponding user login request, which contains the unique identifier of the user, such as the user ID. In addition, the user login request can also contain an environment identifier, which indicates the virtual environment information of the device currently used by the user. The environment identifier can be an environment ID.

[0051] S200: Determine whether to allow the user login request based on the login record of the user identification.

[0052] In this embodiment, when a specific user needs to use a product in the cloud authorization platform, the user needs to log in first, and then log in to the product. This step is used to set the constraint rules for user login in the cloud authorization platform. Figure 2 FIG. 2 shows a schematic flow chart of determining whether to allow a user to log in according to Embodiment 1 of the present invention. Figure 2 As shown, step S200 includes:

[0053] S210: Using the user identifier as a keyword, searching a login data table; the login data table contains a correspondence between the user identifier and the login identifier; the login identifier is used to uniquely characterize each user login behavior.

[0054] This embodiment randomly generates a unique login identifier for any user's current online login behavior that has been allowed, and uses the login identifier as a KEY value for hash operation, and maps the corresponding storage address according to the hash operation result. For example, the storage area contains address A, address B, address C, etc., and the login identifier is hashed by a preset hash algorithm, and the result corresponds to the above storage address one by one. When the storage address is determined, this embodiment establishes a login data table in the storage address. The corresponding relationship between the currently logged-in user identifier and the login identifier is first stored in the login data table. And when the user logs out, the corresponding login data table is deleted. Therefore, by querying the login data table, it can be determined which user identifiers are currently logged in.

[0055] S220: Obtain the number of first login identifiers corresponding to the user identifier.

[0056] The first login identifier in this embodiment refers to all login identifiers stored in the login data table and associated with the user identifier. The number of first login identifiers shows the number of simultaneous logins of the user, and corresponding restriction rules can be specified based on the number of simultaneous logins.

[0057] S230: Determine whether to allow the user login request according to the relationship between the number of the first login identifiers and a preset first threshold.

[0058] For example, assuming that the preset first threshold is 10, it means that the user account is allowed to log in 10 times at the same time. When the number of the first login identifier exceeds 10 times, the current login request is rejected. In addition to rejecting the current login request, this embodiment can also determine the login behavior corresponding to other login identifiers to force log out according to the user return value. The user return value is a logout command input by the user through the client, such as determining to force log out of other login identifiers. In this case, other login identifiers can be forced to log out according to the preset settings, such as the earliest login identifier at the login time, so as to meet the login needs of the current login request.

[0059] In addition to considering the number of first login identifiers, this embodiment may also consider the number of environment identifiers, for example, limiting the same user account to log in only in a limited number of virtual environments at the same time. Specifically, the number of first environment identifiers corresponding to the first login identifier may be obtained from the above login data table; if the number of the first environment identifiers is less than a preset second threshold, the user login request is allowed.

[0060] Through the above steps, this embodiment can set login constraints for user accounts based on different rules according to different needs to meet the needs of different enterprises.

[0061] S300: When it is determined that the user login request is allowed, the server receives a product login request sent by the client; the product login request includes a unique product mnemonic identifier and a product group identifier; the product mnemonic identifier is used to uniquely identify the product, and the product group identifier is used to identify the group to which the product belongs.

[0062] This step is used to further log in to the product. The skilled and technical personnel understand that, considering issues such as computing resources, some cloud preferred platforms do not allow some different products to log in at the same time. In order to meet this requirement, this embodiment sets a product mnemonic identifier and a product group identifier, wherein the product mnemonic identifier is used to uniquely represent the corresponding product, and the product group identifier is used to represent the group to which the product belongs, wherein different groups correspond to different product mutual exclusion rules. Specifically, some groups belong to mutually exclusive groups, which means that any two or more products belonging to the group have a mutually exclusive relationship and are not allowed to log in at the same time; some groups belong to non-mutually exclusive groups, which means that any two or more products in the group do not have a mutually exclusive relationship and are allowed to log in at the same time. The product mnemonic identifier and the product group identifier can be pre-stored in the group data table, and the corresponding product group identifier can be obtained by retrieving the product mnemonic identifier in the group data table. In addition, the mutually exclusive value corresponding to each product group identifier can also be stored in the group data table. For example, when the mutually exclusive value is 1, it means that the product group identifier is a mutually exclusive group, and when the mutually exclusive value is 0, it means that the product group identifier is a non-mutually exclusive group.

[0063] S400: Determine whether to allow the product login request according to the login record of the product mnemonic identifier and the product group identifier.

[0064] Figure 3 FIG. 1 is a schematic flow chart of determining a product login request according to Embodiment 1 of the present invention. Figure 3 As shown, step S400 includes:

[0065] S410: Determine whether the product belongs to a mutually exclusive group according to the product group identifier.

[0066] As mentioned above, the grouping data table may store mutually exclusive values ​​corresponding to each product grouping identifier. By querying the mutually exclusive values ​​in the preset grouping data table, it may be determined whether the corresponding grouping identifier is a mutually exclusive group.

[0067] S420: In the case where the product belongs to a mutually exclusive group, the login data table is retrieved to determine whether the login data table contains a second login identifier corresponding to the product mnemonic identifier and a third login identifier corresponding to other mnemonic identifiers; the other mnemonic identifiers are other identifiers that have the same product group identifier as the product mnemonic identifier.

[0068] The login data table in this embodiment can store the corresponding relationship between the login identifier and the user identifier, the corresponding relationship between the login identifier and the environment identifier, and can also store the corresponding relationship between the login identifier and the product mnemonic identifier. For any product, once it is allowed to log in online, a data record of the association between the login identifier and the product mnemonic identifier will be stored in the login data table. For the same mutually exclusive group, for example, group A, assuming that the product mnemonic identifiers belonging to group A include product A, product B and product C, if product A is selected as the mnemonic identifier of the product to be logged in, then product B and product C are other mnemonic identifiers.

[0069] S430: Determine whether to allow the product login request according to the number of the second login identifiers and the number of the third login identifiers.

[0070] The current online login number of the above-mentioned product mnemonic identifier can be obtained by the number of the second login identifier, and the current online login number of the above-mentioned other mnemonic identifiers can be obtained by the number of the third login identifier. Therefore, different login restriction rules can be set according to the number of the second login identifier and the number of the third login identifier, for example, the above-mentioned product mnemonic identifiers with a third threshold number are allowed to log in at the same time, and other mnemonic identifiers and the above-mentioned product mnemonic identifiers are prohibited from logging in at the same time. In this case, this embodiment can first determine whether the number of the second login identifiers is less than the preset third threshold; when the number of the second login identifiers is less than the third threshold, determine whether the number of the third login identifiers is zero; when the number of the third login identifiers is zero, allow the product login request. It can be understood that the number of the third login identifier is zero, which means that there are no other product identifiers with a mutually exclusive relationship logged in at the same time. In this case, the above-mentioned product mnemonic identifier is allowed to log in. In addition, if the number of the third login identifier is not zero, it can also force other logged-in mnemonic identifiers to log out according to the logout command issued by the user, so that the current product mnemonic identifier satisfies the mutual exclusion restriction and logs in.

[0071] S500: When it is determined that the product login request is allowed, log in the product.

[0072] In this step, a unique login identifier is randomly generated according to the current login behavior, and a login data table is created according to the login identifier. Further, the association relationship between the user identifier and the login identifier, the association relationship between the product mnemonic identifier and the login identifier, and the association relationship between the environment identifier and the login identifier are recorded in the login data table. In this way, when the server receives other user login requests and product login requests in the subsequent process, it can query other user login requests and product login requests through the created login data table to see whether they meet the preset login restriction conditions, thereby realizing unified management of product login constraints.

[0073] Please continue reading Figure 4 , shows a product login management device. In this embodiment, the product login management device 40 may include or be divided into one or more program modules. One or more program modules are stored in a storage medium and executed by one or more processors to complete the present invention and implement the above-mentioned product login management method. The program module referred to in the present invention refers to a series of computer program instruction segments that can complete specific functions, which is more suitable for describing the execution process of the product login management device 40 in the storage medium than the program itself. The following description will specifically introduce the functions of each program module in this embodiment:

[0074] The user login request module 41 is adapted for the server to receive a user login request sent by a client; the login request includes a unique user identifier;

[0075] A user login determination module 42, adapted to determine whether to allow the user login request according to the login record of the user identification;

[0076] The product login request module 43 is adapted to receive, by the server, a product login request sent by the client when it is determined that the user login request is allowed; the product login request includes a unique product mnemonic identifier and a product group identifier; the product mnemonic identifier is used to uniquely identify the product, and the product group identifier is used to identify the group to which the product belongs;

[0077] A product login determination module 44, adapted to determine whether to allow the product login request according to the login record of the product mnemonic identifier and the product group identifier;

[0078] The product login module 45 is adapted to log in the product if it is determined that the product login request is allowed.

[0079] This embodiment also provides a computer device, such as a smart phone, tablet computer, laptop computer, desktop computer, rack server, blade server, tower server or cabinet server (including an independent server or a server cluster composed of multiple servers) that can execute programs. The computer device 50 of this embodiment includes at least but is not limited to: a memory 51 and a processor 52 that can communicate with each other through a system bus, such as Figure 5 It should be pointed out that Figure 5 Only a computer device 50 having components 51 - 52 is shown, but it should be understood that implementing all of the components shown is not a requirement, and more or fewer components may alternatively be implemented.

[0080] In this embodiment, the memory 51 (i.e., readable storage medium) includes flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 51 can be an internal storage unit of the computer device 50, such as a hard disk or memory of the computer device 50. In other embodiments, the memory 51 can also be an external storage device of the computer device 50, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card, etc. equipped on the computer device 50. Of course, the memory 51 can also include both the internal storage unit of the computer device 50 and its external storage device. In this embodiment, the memory 51 is generally used to store the operating system and various application software installed on the computer device 50, such as the program code of the management device 40 for product login in the first embodiment. In addition, the memory 51 can also be used to temporarily store various types of data that have been output or are to be output.

[0081] In some embodiments, the processor 52 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips. The processor 52 is generally used to control the overall operation of the computer device 50. In this embodiment, the processor 52 is used to run the program code stored in the memory 21 or process data, such as running the product login management device 40 to implement the product login management method of the first embodiment.

[0082] This embodiment also provides a computer-readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory (for example, an SD or DX memory, etc.), a random access memory (RAM), a static random access memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a disk, an optical disk, a server, an App application store, etc., on which a computer program is stored, and the program realizes corresponding functions when executed by a processor. The computer-readable storage medium of this embodiment is used to store the management device 40 for product login, and when executed by the processor, the management method for product login of the first embodiment is realized.

[0083] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0084] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code that includes one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present invention includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present invention belong.

[0085] A person of ordinary skill in the art can understand that all or part of the steps carried out in the above-mentioned embodiment method can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable medium. When the program is executed, it includes one of the steps of the method embodiment or a combination thereof.

[0086] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example" or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0087] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method.

[0088] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A product registration management method, characterized in that: The following steps are involved: The server receives the user login request sent by the client; The login request includes a unique user identifier; Determining whether to allow the user login request according to the login record of the user identifier includes: using the user identifier as a keyword to search a login data table; the login data table contains a correspondence between the user identifier and the login identifier; the login identifier is used to uniquely characterize each user login behavior; obtaining the number of first login identifiers corresponding to the user identifier; determining whether to allow the user login request according to the relationship between the number of the first login identifiers and a preset first threshold; In the case of determining that the user login request is allowed, the server receives a product login request sent by the client; the product login request includes a unique product mnemonic identifier and a product group identifier; the product mnemonic identifier is used to uniquely identify the product, and the product group identifier is used to identify the group to which the product belongs; Determining whether to allow the product login request according to the login record of the product mnemonic identifier and the product group identifier, including: determining whether the product belongs to a mutually exclusive group according to the product group identifier; if the product belongs to a mutually exclusive group, retrieving the login data table to determine whether the login data table contains a second login identifier corresponding to the product mnemonic identifier and a third login identifier corresponding to other mnemonic identifiers; the other mnemonic identifiers are other identifiers having the same product group identifier as the product mnemonic identifier; determining whether the number of the second login identifiers is less than a preset third threshold; if the number of the second login identifiers is less than the third threshold, determining whether the third login identifier is zero; if the third login identifier is zero, allowing the product login request; If it is determined that the product login request is allowed, the product is logged in.

2. The product registration management method according to claim 1, characterized in that: The login request also includes an environment identifier; the environment identifier is used to uniquely identify the virtual system currently running by the user; The step of determining whether to allow the user login request according to the login record of the user identification further comprises: When the number of the first login identifiers is less than the first threshold, acquiring the number of first environment identifiers corresponding to the first login identifiers from the login data table; When the number of the first environment identifiers is less than a preset second threshold, the user login request is allowed.

3. The product registration management method according to claim 1, characterized in that: The step of determining whether to allow the product login request according to the number of the second login identifiers and the number of the third login identifiers further includes: When the third login identifier is not zero, receiving a logoff request for the other mnemonic identifier sent by the client; According to the offline request, the third login identifier is deleted from the login data table.

4. The product registration management method according to claim 2, characterized in that: In the case where the login request is allowed, the step of logging in to the product includes: Randomly generate a login ID that uniquely represents the current login behavior; A login data table is created according to the login identifier, wherein the login data table contains the association relationship between the user identifier and the login identifier, the association relationship between the product mnemonic identifier and the login identifier, and the association relationship between the environment identifier and the login identifier.

5. A product registration management device, characterized in that: include: User login request module, suitable for the server to receive the user login request sent by the client; The login request includes a unique user identifier; A user login determination module, adapted to determine whether to allow the user login request according to the login record of the user identification; A product login request module, adapted for, in the case where it is determined that the user login request is allowed, the server receiving the product login request sent by the client; the product login request includes a unique product mnemonic identifier and a product group identifier; the product mnemonic identifier is used to uniquely identify the product, and the product group identifier is used to identify the group to which the product belongs; A product login determination module, adapted to determine whether to allow the product login request according to the login record of the product mnemonic identifier and the product group identifier; A product login module, adapted to log in the product if it is determined that the product login request is allowed; The user login determination module is further used to retrieve the login data table using the user identifier as a keyword; The login data table contains the corresponding relationship between the user identifier and the login identifier; The login identifier is used to uniquely characterize each user login behavior; Obtaining the number of first login identifiers corresponding to the user identifier; determining whether to allow the user login request according to the relationship between the number of the first login identifiers and a preset first threshold; The product login determination module is also used to determine whether the product belongs to a mutually exclusive group based on the product grouping identifier; if the product belongs to a mutually exclusive group, retrieve the login data table to determine whether the login data table contains a second login identifier corresponding to the product mnemonic identifier, and a third login identifier corresponding to other mnemonic identifiers; the other mnemonic identifiers are other identifiers that have the same product grouping identifier as the product mnemonic identifier; determine whether the number of the second login identifiers is less than a preset third threshold; if the number of the second login identifiers is less than the third threshold, determine whether the third login identifier is zero; if the third login identifier is zero, allow the product login request.

6. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 4 are implemented.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

Images