Authentication login method and device for shared account

Abstract

The application discloses a shared account authentication login method and device, which comprises the following steps: sending a first login domain account corresponding to a second user terminal to a third-party verification code generation platform, so that the third-party verification code generation platform sends a first dynamic verification code to the second user terminal according to the first login domain account; sending a second dynamic verification code input by a first user and a login account to be logged in to an account management center, so that the account management center sends the second dynamic verification code to the third-party verification code generation platform after determining that the login account to be logged in is a system account, and sends the first login domain account to the account management center after determining that the second dynamic verification code is correct, so that the account management center feeds back first login success confirmation information when determining that the login account to be logged in is valid according to the first login domain account; compared with the prior art, the application can improve the security of the shared account, and solve the problem that the shared account is difficult to realize simultaneous login by multiple people.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of information processing, in particular to a shared account authentication login method and device. BACKGROUND

[0002] The shared account is a way to effectively and easily manage shared files for all personnel within an organization, and allows multiple people to log in for testing certain scenarios.

[0003] In the prior art, the account name of the shared account may be an entity mobile phone number or a non-entity mobile phone number, and when facing a shared account whose account name is not a non-entity mobile phone number, it is difficult to receive the verification code through the entity mobile phone, which may lead to the failure of account authentication. Even if the account name of the shared account is an entity mobile phone number, when multiple user logins are required, only a single verification code can be obtained for a single mobile phone number at a time, which can only be used for single-person verification. For multiple user logins, multiple verifications codes need to be obtained, which takes a long time and cannot achieve the simultaneous login of multiple people. SUMMARY

[0004] The technical problem to be solved by the present application is to provide a shared account authentication login method and device to improve the security of the shared account and solve the problem of difficulty in simultaneous login of multiple people.

[0005] To solve the above technical problems, the present application provides a shared account authentication login method, comprising:

[0006] Obtaining a to-be-logged-in account input by a first user;

[0007] Obtaining a second dynamic verification code input by the first user according to a first dynamic verification code displayed on a second user terminal; wherein the first dynamic verification code is obtained by sending a dynamic verification code request and a first login domain account corresponding to the second user terminal to a third-party verification code generation platform in response to a dynamic verification code request event triggered by the first user, so that the third-party verification code generation platform sends the first dynamic verification code to the second user terminal according to the first login domain account;

[0008] sending the second dynamic verification code and the to-be-logged-in account to the account management center, so that the account management center sends the second dynamic verification code to the third-party verification code generation platform after determining that the to-be-logged-in account is a system account, so that the third-party verification code generation platform returns a first login domain account to the account management center after determining that the second dynamic verification code is correct according to the first dynamic verification code, so that the account management center performs shared account authentication on the to-be-logged-in account according to the first login domain account after determining that the to-be-logged-in account is a shared account, and feeds back first login success confirmation information when the to-be-logged-in account is valid.

[0009] In a possible implementation, the account management center determines that the to-be-logged-in account is a system account, specifically comprising:

[0010] obtaining all account information in a target system, comparing the to-be-logged-in account with the all account information, and determining that the to-be-logged-in account is a system account in the target system if there is first account information consistent with the to-be-logged-in account in the all account information, wherein the all account information includes shared account information and normal entity account information.

[0011] By determining whether the to-be-logged-in account is a system account, non-system account to-be-logged-in accounts can be screened out in advance before to-be-logged-in account authentication, thereby improving the login efficiency of the account.

[0012] In a possible implementation, before the account management center determines that the to-be-logged-in account is a shared account, the account management center further comprises:

[0013] The account management center establishes a shared account management module, wherein the shared account management module is used to record a shared account name corresponding to a shared account, a login domain account allowed to log in by the shared account, and a login domain account state.

[0014] Based on the established shared account management module, an account management personnel can manage shared accounts, and the identification efficiency of to-be-logged-in accounts can be improved when the to-be-logged-in accounts are identified as shared accounts subsequently.

[0015] In a possible implementation, the account management center determines that the to-be-logged-in account is a shared account, specifically comprising:

[0016] The account management center obtains a login account name in the to-be-logged-in account, traverses the shared account management module, determines whether there is a shared account name consistent with the login account name in the shared account management module, determines that the to-be-logged-in account is a normal entity account if not, and determines that the to-be-logged-in account is a shared account if yes.

[0017] Since the shared account management module is used to store all shared account information, when the shared account management module is used to identify the shared account of the to-be-logged-in account, it is only necessary to determine whether the to-be-logged-in account exists in the shared account management module to determine whether the to-be-logged-in account is a shared account, thereby improving the identification efficiency of the to-be-logged-in account.

[0018] In a possible implementation, the shared account authentication of the to-be-logged-in account according to the first login domain account specifically includes:

[0019] When the to-be-logged-in account is a shared account, all login domain accounts allowed to be logged in by the to-be-logged-in account are obtained, and the first login domain account is obtained, and it is determined whether a second login domain account consistent with the first login domain account exists in the all login domain accounts, if not, it is determined that the to-be-logged-in account is invalid, and if yes, a login domain account state corresponding to the second login domain account is obtained.

[0020] If the login domain account state corresponding to the second login domain account is valid, it is determined that the to-be-logged-in account is valid, and if the login domain account state corresponding to the second login domain account is invalid, it is determined that the to-be-logged-in account is invalid.

[0021] Since the shared account management module records the login domain accounts allowed to be logged in by the shared account and the login domain account state, based on this, by comparing the obtained first login domain account with the login domain accounts allowed to be logged in by the shared account and the login domain account state recorded in the shared account management module, it can be quickly known whether the first login domain account is allowed to be logged in and whether the first login domain account state is valid, thereby improving the authentication efficiency of the to-be-logged-in account.

[0022] In a possible implementation, after the account management center establishes the shared account management module, the account management center further includes:

[0023] The account management center sets a role for each login domain account in the shared account, and sets a corresponding role permission for the role.

[0024] Since the shared account allows multiple people to log in, different roles are set for different first users logging in the shared account, i.e., each login domain account in the shared account, and a corresponding role permission is set for the role, thereby improving the management efficiency of the shared account in the case of allowing multiple people to log in.

[0025] The application further provides a shared account authentication login method, which includes:

[0026] receive the third dynamic verification code and the to-be-logged-in account sent by the first user terminal, and receive the fourth dynamic verification code and the first login domain account sent by the third-party verification code generation platform; wherein the third dynamic verification code and the to-be-logged-in account are obtained by the first user terminal according to the input of the first user;

[0027] after determining that the to-be-logged-in account is a system account, send the third dynamic verification code to the third-party verification code generation platform, so that the third-party verification code generation platform feeds back the first login domain account after determining that the third dynamic verification code is correct according to the generated fourth dynamic verification code;

[0028] receive the first login domain account sent by the third-party verification code generation platform;

[0029] after determining that the to-be-logged-in account is a shared account, perform shared account authentication on the to-be-logged-in account according to the first login domain account, and feed back first login success confirmation information to the first user terminal after determining that the to-be-logged-in account is valid.

[0030] In a possible implementation, the third dynamic verification code is obtained by the first user terminal according to the input of the first user, specifically:

[0031] the second user terminal sends a dynamic verification code request and the first login domain account corresponding to the second user terminal to the third-party verification code generation platform in response to the dynamic verification code request event triggered by the first user, so that the third-party verification code generation platform sends a fourth dynamic verification code to the second user terminal according to the first login domain account;

[0032] the second user terminal displays the fourth dynamic verification code, so that the first user inputs the third dynamic verification code in the first user terminal according to the fourth dynamic verification code.

[0033] The third-party verification code generation platform sends a fourth dynamic verification code to the second user terminal according to the first login domain account, which is different from the existing single mobile phone number or email bound to a shared account, so that multiple first user terminals can receive corresponding fourth verification codes based on multiple second user terminals in the case of multiple simultaneous logins, which is conducive to realizing the simultaneous login of multiple people for a shared account.

[0034] In a possible implementation, before determining that the to-be-logged-in account is a shared account, the method further includes:

[0035] establishing a shared account management module, wherein the shared account management module is configured to record a shared account name corresponding to a shared account, a login domain account allowed to log in by the shared account, and a login domain account state.

[0036] In a possible implementation, the determining that the to-be-logged-in account is a shared account specifically includes:

[0037] Obtaining a login account name in the to-be-logged-in account, traversing the shared account management module, judging whether there is a shared account name consistent with the login account name in the shared account management module, if not, determining that the to-be-logged-in account is a normal entity account, if yes, determining that the to-be-logged-in account is a shared account.

[0038] In a possible implementation, the performing shared account authentication on the to-be-logged-in account according to the first login domain account and determining that the to-be-logged-in account is valid specifically includes:

[0039] When the to-be-logged-in account is a shared account, obtaining all login domain accounts allowed to be logged in by the to-be-logged-in account, and obtaining the first login domain account, judging whether there is a second login domain account consistent with the first login domain account in the all login domain accounts, if not, determining that the to-be-logged-in account is invalid, if yes, obtaining a login domain account state corresponding to the second login domain account;

[0040] If the login domain account state corresponding to the second login domain account is valid, it is determined that the to-be-logged-in account is valid, if the login domain account state corresponding to the second login domain account is invalid, it is determined that the to-be-logged-in account is invalid.

[0041] In a possible implementation, after the shared account management module is established, the method further includes:

[0042] Roles are set for each login domain account in the shared account, and corresponding role permissions are set for the roles.

[0043] The application further provides a shared account authentication login method, which includes:

[0044] Receiving a dynamic verification code request sent by a second user terminal and a first login domain account corresponding to the second user terminal, wherein the dynamic verification code request is generated by the second user terminal in response to a dynamic verification code request event triggered by a first user;

[0045] According to the first login domain account, a fifth dynamic verification code generated by the second user terminal is sent to the second user terminal, so that the first user terminal obtains a to-be-logged-in account input by the first user, and after obtaining a sixth dynamic verification code input by the first user according to the fifth dynamic verification code displayed in the second user terminal, the sixth dynamic verification code is sent to the account management center;

[0046] receive the sixth dynamic verification code sent by the account management center, and return a first login domain account to the account management center after determining that the sixth dynamic verification code is correct according to the fifth dynamic verification code, so that the account management center performs shared account authentication on the to-be-logged-in account according to the first login domain account after determining that the to-be-logged-in account is a shared account, and feeds back first login success confirmation information when determining that the to-be-logged-in account is valid.

[0047] The application further provides a user terminal, comprising: a first information acquisition module, a second information acquisition module and a shared account authentication module.

[0048] The first information acquisition module is configured to acquire a to-be-logged-in account input by a first user.

[0049] The second information acquisition module is configured to acquire a second dynamic verification code input by the first user according to a first dynamic verification code displayed in a second user terminal; wherein the first dynamic verification code is acquired by sending a dynamic verification code request and a first login domain account corresponding to the second user terminal to a third-party verification code generation platform in response to a dynamic verification code request event triggered by the first user, so that the third-party verification code generation platform sends the first dynamic verification code to the second user terminal according to the first login domain account.

[0050] The shared account authentication module is configured to send the second dynamic verification code and the to-be-logged-in account to an account management center, so that the account management center sends the second dynamic verification code to the third-party verification code generation platform after determining that the to-be-logged-in account is a system account, so that the third-party verification code generation platform returns a first login domain account to the account management center after determining that the second dynamic verification code is correct according to the first dynamic verification code, so that the account management center performs shared account authentication on the to-be-logged-in account according to the first login domain account after determining that the to-be-logged-in account is a shared account, and feeds back first login success confirmation information when determining that the to-be-logged-in account is valid.

[0051] The application further provides an account management center, comprising: a user terminal information receiving module, a first account authentication module, a third-party verification code generation platform information receiving module and a second account authentication module.

[0052] The user terminal information receiving module is configured to receive a third dynamic verification code and a to-be-logged-in account sent by a first user terminal, and receive a fourth dynamic verification code and a first login domain account sent by a third-party verification code generation platform; wherein the third dynamic verification code and the to-be-logged-in account are acquired by the first user terminal according to the input of a first user.

[0053] The first account authentication module is configured to send the third dynamic verification code to the third-party verification code generation platform after determining that the account to be logged in is a system account, so that the third-party verification code generation platform feeds back the first login domain account after determining that the third dynamic verification code is correct according to the fourth dynamic verification code generated.

[0054] The third-party verification code generation platform information receiving module is configured to receive the first login domain account sent by the third-party verification code generation platform

[0055] The second account authentication module is configured to perform shared account authentication on the account to be logged in according to the first login domain account after determining that the account to be logged in is a shared account, and feed back first login success confirmation information to the first user terminal after determining that the account to be logged in is valid.

[0056] The application further provides a third-party verification code generation platform, which comprises a second user terminal information receiving module, a dynamic verification code sending module and a dynamic verification code verification module.

[0057] The second user terminal information receiving module is configured to receive a dynamic verification code request sent by a second user terminal and a first login domain account corresponding to the second user terminal, wherein the dynamic verification code request is generated by the second user terminal in response to a dynamic verification code request event triggered by a first user.

[0058] The dynamic verification code sending module is configured to send a fifth dynamic verification code generated according to the first login domain account to the second user terminal, so that the first user terminal acquires an account to be logged in input by the first user and acquires a sixth dynamic verification code input by the first user according to the fifth dynamic verification code displayed in the second user terminal, and then sends the sixth dynamic verification code to the account management center.

[0059] The dynamic verification code verification module is configured to receive the sixth dynamic verification code sent by the account management center, and return the first login domain account to the account management center after determining that the sixth dynamic verification code is correct according to the fifth dynamic verification code, so that the account management center performs shared account authentication on the account to be logged in according to the first login domain account after determining that the account to be logged in is a shared account, and feeds back first login success confirmation information after determining that the account to be logged in is valid.

[0060] The application further provides a login system, which comprises a user terminal, an account management center and a third-party verification code generation platform.

[0061] The user terminal is in communication connection with the account management center and the third-party verification code generation platform, the account management center is in communication connection with the third-party verification code generation platform;

[0062] The user terminal executes the shared account authentication login method as described above.

[0063] The account management center executes the shared account authentication login method as described above.

[0064] The third-party verification code generation platform executes the shared account authentication login method as described above.

[0065] The application further provides a terminal device, comprising a processor, a memory and a computer program stored in the memory and configured to be executed by the processor, and the processor executes the computer program to realize the shared account authentication login method as described above.

[0066] The application further provides a computer readable storage medium comprising a stored computer program, wherein the computer readable storage medium controls a device where the computer readable storage medium is located to execute the shared account authentication login method as described above when the computer program runs.

[0067] The application further provides a computer program product, which, when running on a computer device, enables the computer device to realize the shared account authentication login method as described above.

[0068] The shared account authentication login method and device of the application embodiment have the following beneficial effects compared with the prior art.

[0069] By acquiring the to-be-logged-in account input by the first user; acquiring the second dynamic verification code input by the first user according to the first dynamic verification code displayed in the second user terminal; wherein the first dynamic verification code is acquired by the second user terminal sending a dynamic verification code request to a third-party verification code generation platform in response to the first user triggering a dynamic verification code request event, and the first login domain account corresponding to the second user terminal, so that the third-party verification code generation platform sends the first dynamic verification code to the second user terminal according to the first login domain account; sending the second dynamic verification code and the to-be-logged-in account to the account management center, so that the account management center sends the second dynamic verification code to the third-party verification code generation platform after determining that the to-be-logged-in account is a system account, so that the third-party verification code generation platform returns the first login domain account to the account management center after determining that the second dynamic verification code is correct according to the first dynamic verification code, so that the account management center performs shared account authentication on the to-be-logged-in account according to the first login domain account after determining that the to-be-logged-in account is a shared account, and feeds back first login success confirmation information when determining that the to-be-logged-in account is valid; compared with the prior art, the technical scheme of the present application authenticates the to-be-logged-in account input by the user through the account management center, and authenticates the second dynamic verification code through the third-party verification code generation platform, realizes double-factor authentication of the shared account, improves the security of the shared account, and in the multi-user login scenario, based on the third-party verification code generation platform, the first dynamic verification code is sent to the user terminal corresponding to the first login domain account according to the first login domain account, so that multiple first users can receive multiple corresponding second verification codes based on the different first login domain accounts used, realize multi-person simultaneous login of the shared account, and improve the efficiency of multi-person simultaneous login. BRIEF DESCRIPTION OF DRAWINGS

[0070] Figure 1 is a flowchart of an embodiment of a shared account authentication login method provided by the present application;

[0071] Figure 2 is a flowchart of another embodiment of a shared account authentication login method provided by the present application;

[0072] Figure 3 is a flowchart of another embodiment of a shared account authentication login method provided by the present application;

[0073] Figure 4 is a structural diagram of an embodiment of a user terminal provided by the present application;

[0074] Figure 5 is a structural diagram of an embodiment of an account management center provided by the present application;

[0075] Figure 6 is a structural schematic diagram of an embodiment of a third-party verification code generation platform provided by the present application;

[0076] Figure 7 is a structural schematic diagram of an embodiment of a system provided by the present application;

[0077] Figure 8 is a system login interface schematic diagram of an embodiment provided by the present application;

[0078] Figure 9 is a shared account management module schematic diagram of an embodiment provided by the present application;

[0079] Figure 10 is a shared account role representation schematic diagram of an embodiment provided by the present application. DETAILED DESCRIPTION

[0080] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without any creative work fall within the scope of protection of the present application.

[0081] Embodiment 1

[0082] Reference is made to Figure 1 , Figure 1 is a flow schematic diagram of an embodiment of a shared account authentication login method provided by the present application, as shown in Figure 1 , the method comprises steps 101-103, and specifically as follows:

[0083] Step 101: obtaining a to-be-logged-in account input by a first user.

[0084] In an embodiment, when the first user needs to log in to a target system, the first user inputs a to-be-logged-in account in a system login interface, wherein the to-be-logged-in account comprises a login account and a password of the system, as shown in Figure 8 , Figure 8 is a system login interface schematic diagram.

[0085] In an embodiment, the first user terminal used by the first user when logging in to the target system can detect the operation performed by the user in the system login interface in real time, and can directly obtain the to-be-logged-in account input by the first user when detecting that the first user inputs the to-be-logged-in account.

[0086] Specifically, the first user terminal system performs real-time identification on a login account input box and a password input box of a system login interface, and when detecting that the first user triggers an input event of the login account input box, the first user terminal system responds and identifies first content input by the first user in the login account input box, and when detecting that the input state of the login account input box is closed, the first user terminal system generates first content data; when detecting that the first user triggers an input event of the password input box, the first user terminal system identifies second content input by the first user in the password input box, and when detecting that the input state of the password input box is closed, the first user terminal system generates second content data; and the first user terminal system integrates and takes the identified first content data and second content data as a login account to be input by the first user.

[0087] Step 102: obtaining a second dynamic verification code input by the first user according to a first dynamic verification code displayed in the second user terminal; wherein the first dynamic verification code is obtained by sending, by the second user terminal, a dynamic verification code request to a third-party verification code generation platform in response to the first user triggering the dynamic verification code request event, and a first login domain account corresponding to the second user terminal, so that the third-party verification code generation platform sends the first dynamic verification code to the second user terminal according to the first login domain account.

[0088] In an embodiment, the second user terminal has a user mobile phone OTP program installed therein, and the user mobile phone OTP program is logged in by using the first login domain account; wherein the first login domain account is a mobile phone number; and OTP is One Time Password dynamic verification code.

[0089] In an embodiment, the second user terminal responds to the dynamic verification code request event triggered by the first user; specifically, the second user terminal generates a dynamic verification code generation request based on the user mobile phone OTP program in the second user terminal, and after obtaining the first login domain account corresponding to the second user terminal, the second user terminal sends the dynamic verification code generation request to the third-party verification code generation platform and the first login domain account corresponding to the second user terminal.

[0090] In an embodiment, the third-party verification code generation platform generates a first dynamic verification code according to the dynamic verification code generation request after receiving the dynamic verification code generation request and the first login domain account.

[0091] Specifically, the third-party dynamic verification code generation platform generates the first dynamic verification code by using a preset dynamic verification code generation algorithm, wherein the preset dynamic verification code generation algorithm includes but is not limited to a timestamp algorithm, and the generated first dynamic verification code can include at least one of data, characters and a timestamp.

[0092] In an embodiment, the third-party verification code generation platform further records a first time of generating the first dynamic verification code.

[0093] In an embodiment, the third-party verification code generation platform sends the first dynamic verification code to the second user terminal based on the first login domain account.

[0094] In an embodiment, the first user terminal and the second user terminal can be the same user terminal, and the first user terminal and the second user terminal can also be different user terminals.

[0095] In an embodiment, when the first user terminal and the second user terminal are the same user terminal, the first user terminal directly sends a dynamic verification code request and a first login domain account corresponding to the first user terminal to the third-party verification code generation platform in response to a dynamic verification code request event triggered by the first user on the first user terminal, so that the third-party verification code generation platform sends a first dynamic verification code to the first user terminal based on the first login domain account.

[0096] In an embodiment, when the second user terminal receives the first dynamic verification code sent by the third-party verification code generation platform, the second user terminal displays the first dynamic verification code to the first user through a display interface of the second user terminal, so that the first user can quickly obtain the content of the first dynamic verification code.

[0097] In an embodiment, the first user inputs a second dynamic verification code into a dynamic verification code input box of the system login interface of the first user terminal according to the first dynamic verification code displayed by the second user terminal.

[0098] In an embodiment, when it is detected that the first user inputs the second dynamic verification code, the second dynamic verification code input by the first user is directly obtained.

[0099] Specifically, the first user terminal system performs real-time identification on the dynamic verification code input box of the system login interface, detects an input event of the first user triggering the dynamic verification code input box, responds to and identifies third content input by the first user in the dynamic verification code input box, generates third content data when it is detected that the input state of the dynamic verification code input box is closed, and takes the identified third content data as the second dynamic verification code input by the first user.

[0100] Step 103: sending the second dynamic verification code and the to-be-logged-in account to the account management center, so that the account management center sends the second dynamic verification code to the third-party verification code generation platform after determining that the to-be-logged-in account is a system account, so that the third-party verification code generation platform returns a first login domain account to the account management center after determining that the second dynamic verification code is correct according to the first dynamic verification code, so that the account management center performs shared account authentication on the to-be-logged-in account according to the first login domain account after determining that the to-be-logged-in account is a shared account, and feeds back first login success confirmation information when determining that the to-be-logged-in account is valid.

[0101] In an embodiment, after the first user terminal obtains the to-be-logged-in account and the second dynamic verification code input by the first user on the system login interface, the first user terminal sends the second dynamic verification code and the to-be-logged-in account to the account management center based on the communication connection relationship between the first user terminal and the account management center.

[0102] Preferably, if the first user terminal only obtains any one of the to-be-logged-in account and the second dynamic verification code, it is considered that the input information of the first user is incomplete, and at this time, the obtained data is not sent to the account management center.

[0103] In an embodiment, after the account management center receives the second dynamic verification code and the to-be-logged-in account sent by the first user terminal, the account management center needs to determine whether the to-be-logged-in account is a system account in the target system.

[0104] Specifically, by obtaining all account information in the target system, the to-be-logged-in account is compared with the all account information, if there is first account information consistent with the to-be-logged-in account in the all account information, it is determined that the to-be-logged-in account is an account in the target system, wherein the all account information includes shared account information and ordinary entity account information, the shared account information includes shared account and shared account password, and the ordinary entity account includes ordinary entity account and ordinary entity account password.

[0105] Specifically, the login account in the to-be-logged-in account is compared with all shared account information and ordinary entity account information in the all account information, if there is first account information same as the login account in the to-be-logged-in account in the shared account information or the ordinary entity account information, the first account password corresponding to the first account is further obtained, and the first account password is compared with the password in the to-be-logged-in account, if they are same, it is determined that the to-be-logged-in account is an account in the target system, if not, it is determined that the to-be-logged-in account is not an account in the target system.

[0106] In an embodiment, when it is determined that the to-be-logged-in account is not a system account in the target system, the account management center directly feeds back an account information error prompt to the first user terminal, so as to remind the user to check the to-be-logged-in account, and terminate the subsequent to-be-logged-in account authentication operation.

[0107] Based on the determination by the account management center of whether the to-be-logged-in account is a system account in the target system, the first user input of an error account or an account of a non-target system can be quickly identified, and the case that the account authentication operation is continued when an error account or an account of a non-target system is input is avoided, thereby improving the authentication efficiency of the to-be-logged-in account.

[0108] In an embodiment, after the account management center determines that the to-be-logged-in account is a system account in the target system, the account management center sends the second dynamic verification code to the third-party verification code generation platform, so that the third-party verification code generation platform determines whether the second dynamic verification code is correct according to the first dynamic verification code.

[0109] In an embodiment, the third-party verification code generation platform determines whether the second dynamic verification code is correct according to the first dynamic verification code. Specifically, when the third-party verification code generation platform receives the second dynamic verification code sent by the account management center, the third-party verification code generation platform acquires a current receiving time, compares the current receiving time with a first time recorded when the first dynamic verification code is generated, determines whether the first dynamic verification code and the second dynamic verification code are consistent after determining that the current receiving time is within a valid time range, confirms that the second dynamic verification code is correct if the first dynamic verification code and the second dynamic verification code are consistent, and confirms that the second dynamic verification code is not correct if the first dynamic verification code and the second dynamic verification code are not consistent.

[0110] In an embodiment, it is determined that the current receiving time is within the valid time range. Specifically, a time difference between the first time and the current receiving time is calculated, and it is determined whether the time difference is within a preset time threshold, the second time is determined to be within the valid time range if the time difference is within the preset time threshold, and the second time is determined to be not within the valid time range and the subsequent to-be-logged-in account authentication operation is terminated if the time difference is not within the preset time threshold.

[0111] In an embodiment, when the third-party verification code generation platform determines that the current receiving time is not within the valid time range, the third-party verification code generation platform feeds back verification code information error to the first user terminal.

[0112] In an embodiment, when it is determined that the second dynamic verification code is correct, the third-party verification code generation platform generates dynamic verification code correct information, and sends the dynamic verification code correct information and the first login domain account to the account management center.

[0113] In an embodiment, the account management center establishes a shared account management module, and determines whether the to-be-logged-in account is a shared account based on the shared account management module.

[0114] In an embodiment, the shared account management module is used to record a shared account name corresponding to a shared account, login domain accounts allowed to log in the shared account, and states of the login domain accounts. Figure 9 As shown in Figure 9 FIG. 4 is a schematic diagram of a shared account management module.

[0115] In an embodiment, for the login domain accounts allowed to log in the shared account recorded in the shared account management module, specifically, since there are multiple people allowed to log in the shared account, for example, the shared account a can test a scenario authorized by an administrator, if the test involves the scenario, it can be that employee A or other employee B tests different use cases respectively, therefore, for the employee A or other employee B who can use the shared account, the login domain account of the employee can be managed based on the shared account management module, so that it can be determined based on the login domain account whether the employee has the permission to log in the shared account, which facilitates the management of the system administrator.

[0116] In an embodiment, after the shared account management module is established, a role is set for each login domain account in the shared account, and the role is set with corresponding role permissions. Figure 10 As shown in Figure 10 FIG. 5 is a schematic diagram of a shared account role.

[0117] As an example in the embodiment, for the employee A or other employee B who can use the shared account, since the operations performed by different employees using the shared account can be different, in order to more intuitively understand the use of the shared account by different employees and ensure that the use conforms to the operation regulations, different roles and corresponding role permissions are set for different login domain accounts under the same shared account, for example, for the employee A, a role A is set, and the corresponding role permission is account creation and deletion; for the employee B, a role B is set, and the corresponding role permission is account authorization.

[0118] In an embodiment, the shared account is managed and maintained by the system administrator through the shared account management module in the account management center, including adding, deleting, modifying, querying, and adjusting the login domain account state of the shared account.

[0119] In an embodiment, the shared account management module stores all shared accounts in the system, and preferably, the shared account management module can also store virtual accounts; for ordinary entity accounts in the system, they are not stored in the shared account management module.

[0120] In an embodiment, the account management center determines the to-be-logged-in account as a shared account. Specifically, the account management center acquires a login account name in the to-be-logged-in account, traverses the shared account management module, and determines whether there is a shared account name consistent with the login account name in the shared account management module. If not, the to-be-logged-in account is determined as a normal entity account. If yes, the to-be-logged-in account is determined as a shared account. Since the normal entity account in the system is not stored in the shared account management module, the to-be-logged-in account only needs to be compared with the shared account name recorded in the shared account management module, so that the authentication efficiency of the to-be-logged-in account can be improved.

[0121] In an embodiment, when the account management center determines that the to-be-logged-in account is a normal entity account, the second login success confirmation information is directly fed back to the first user terminal.

[0122] In an embodiment, when the account management center determines that the login account information is a normal entity account, the account management center does not need to perform shared account authentication processing on the to-be-logged-in account according to the first login domain account, thereby improving the login efficiency of the normal entity account. In an embodiment, it is known from the shared account management module that for each shared account, there is a corresponding login domain account allowed to log in. Therefore, in the embodiment, the account management center determines whether the to-be-logged-in account is valid according to the first login domain account after determining that the to-be-logged-in account is a shared account, thereby further improving the security of the shared account.

[0123] In an embodiment, the account management center further performs shared account authentication on the to-be-logged-in account according to the first login domain account, and determines that the to-be-logged-in account is valid. Specifically, when the to-be-logged-in account is a shared account, all login domain accounts allowed to log in the to-be-logged-in account are acquired, and the first login domain account is acquired. It is determined whether there is a second login domain account consistent with the first login domain account in the all login domain accounts. If not, the to-be-logged-in account is determined as invalid. If yes, the login domain account state corresponding to the second login domain account is acquired. If the login domain account state corresponding to the second login domain account is valid, the to-be-logged-in account is determined as valid. If the login domain account state corresponding to the second login domain account is invalid, the to-be-logged-in account is determined as invalid.

[0124] In an embodiment, when the account management center determines that the to-be-logged-in account is a shared account and the login domain account is valid, the first login success confirmation information is fed back to the first user terminal.

[0125] In an embodiment, when the account management center confirms that the to-be-logged-in account information is a shared account, but the to-be-logged-in account is invalid, the account management center feeds back an account error prompt information.

[0126] In summary, the embodiment of the present application provides a shared account authentication login method, which authenticates the to-be-logged-in account input by the first user by the account management center, and authenticates the second dynamic verification code by the third-party verification code generation platform, thereby realizing double-factor authentication of the shared account, improving the security of the shared account, and in the multi-user login scenario, replacing the only entity mobile phone number that can be set in the existing shared account with the first login domain account used by the first user to receive the first dynamic verification code, so that multiple users can simultaneously log in to the shared account by using different first login domain accounts, and each first login domain account can simultaneously receive the subsequent first dynamic verification code, thereby realizing multi-user simultaneous login and improving the efficiency of multi-user simultaneous login.

[0127] Embodiment 2

[0128] Referring to Figure 2 , Figure 2 is a flowchart of another embodiment of a shared account authentication login method provided by the present application, as shown in Figure 2 , the method comprises steps 201-204, and specifically as follows:

[0129] Step 201: receiving a third dynamic verification code and a to-be-logged-in account sent by a first user terminal; wherein the third dynamic verification code and the to-be-logged-in account are obtained by the first user terminal according to the input of the first user.

[0130] Step 202: after determining that the to-be-logged-in account is a system account, sending the third dynamic verification code to the third-party verification code generation platform, so that the third-party verification code generation platform feeds back a first login domain account after determining that the third dynamic verification code is correct according to the generated fourth dynamic verification code.

[0131] Step 203: receiving the first login domain account sent by the third-party verification code generation platform.

[0132] Step 204: after determining that the to-be-logged-in account is a shared account, performing shared account authentication on the to-be-logged-in account according to the first login domain account, and feeding back first login success confirmation information to the first user terminal after determining that the to-be-logged-in account is valid.

[0133] In an embodiment, the third dynamic verification code is obtained by the first user terminal according to the input of the first user, specifically: the second user terminal sends a dynamic verification code request and the first login domain account corresponding to the second user terminal to a third-party verification code generation platform in response to the dynamic verification code request event triggered by the first user, so that the third-party verification code generation platform sends a fourth dynamic verification code to the second user terminal according to the first login domain account; and the second user terminal displays the fourth dynamic verification code, so that the first user inputs the third dynamic verification code in the first user terminal according to the fourth dynamic verification code.

[0134] In an embodiment, the determination that the to-be-logged-in account is a system account specifically includes: obtaining all account information in a target system, comparing the to-be-logged-in account with the all account information, and if there is first account information consistent with the to-be-logged-in account in the all account information, determining that the to-be-logged-in account is a system account in the target system, wherein the all account information includes shared account information and normal entity account information.

[0135] In an embodiment, before determining that the to-be-logged-in account is a shared account, the account management center further includes: establishing a shared account management module, wherein the shared account management module is used to record a shared account name corresponding to a shared account, login domain accounts allowed to be logged in by the shared account, and login domain account states.

[0136] In an embodiment, the account management center determines that the to-be-logged-in account is a shared account, specifically including: obtaining a login account name in the to-be-logged-in account, traversing the shared account management module, judging whether there is a shared account name consistent with the login account name in the shared account management module, if not, determining that the to-be-logged-in account is a normal entity account, and if yes, determining that the to-be-logged-in account is a shared account.

[0137] In an embodiment, the account management center performs shared account authentication on the to-be-logged-in account according to the first login domain account, and determines that the to-be-logged-in account is valid; specifically, when the to-be-logged-in account is a shared account, obtaining all login domain accounts allowed to be logged in by the to-be-logged-in account, and obtaining the first login domain account, judging whether there is a second login domain account consistent with the first login domain account in the all login domain accounts, if not, determining that the to-be-logged-in account is invalid, and if yes, obtaining a login domain account state corresponding to the second login domain account; if the login domain account state corresponding to the second login domain account is valid, determining that the to-be-logged-in account is valid, and if the login domain account state corresponding to the second login domain account is invalid, determining that the to-be-logged-in account is invalid.

[0138] In an embodiment, after the shared account management module is established, the method further includes: setting a role for each login domain account in the shared account, and setting a corresponding role permission for the role.

[0139] In summary, the authentication login method for a shared account provided by the embodiment of the present application realizes two-factor authentication for the shared account by authenticating the login account input by the first user and sending a third dynamic verification code to the third-party verification code generation platform to enable the third-party verification code generation platform to authenticate the third dynamic verification code, improves the security of the shared account, and in a multi-user login scenario, replaces the only entity mobile phone number that can be set in the existing shared account with the first login domain account used by the first user to receive a fourth dynamic verification code, so that when multiple users simultaneously log in, different first login domain accounts are used, and each first login domain account can simultaneously receive the corresponding fourth dynamic verification code, which enables multiple users to simultaneously log in to the shared account and improves the efficiency of simultaneous login by multiple users.

[0140] Embodiment 3

[0141] Referring to Figure 3 , Figure 3 is a flowchart of another embodiment of the authentication login method for a shared account provided by the present application, as Figure 3 shown, the method includes steps 301-304, which are specifically as follows:

[0142] Step 301: receiving a dynamic verification code request sent by a second user terminal and a first login domain account corresponding to the second user terminal, wherein the dynamic verification code request is generated by the second user terminal in response to a dynamic verification code request event triggered by a first user.

[0143] Step 302: according to the first login domain account, sending a fifth dynamic verification code generated by the second user terminal to the second user terminal, so that the first user terminal acquires a login account input by a first user and acquires a sixth dynamic verification code input by the first user according to the fifth dynamic verification code displayed in the second user terminal, and then sends the sixth dynamic verification code to an account management center.

[0144] Step 303: receiving the sixth dynamic verification code sent by the account management center, and returning the first login domain account to the account management center after determining that the sixth dynamic verification code is correct according to the fifth dynamic verification code, so that the account management center performs shared account authentication on the login account according to the first login domain account after determining that the login account is a shared account, and feeds back first login success confirmation information when determining that the login account is valid.

[0145] In an embodiment, before receiving the sixth dynamic verification code sent by the account management center, the account management center further needs to determine whether the to-be-logged-in account is a system account, and when the account management center determines that the to-be-logged-in account is a system account, the account management center sends the sixth dynamic verification code to the third-party verification code generation platform, so that the third-party verification code generation platform receives the sixth dynamic verification code sent by the account management center.

[0146] In an embodiment, the account management center determining that the to-be-logged-in account is a system account specifically includes: obtaining all account information in a target system, comparing the to-be-logged-in account with the all account information, and if there is first account information consistent with the to-be-logged-in account in the all account information, determining that the to-be-logged-in account is a system account in the target system, wherein the all account information includes shared account information and normal entity account information.

[0147] In an embodiment, before the account management center determines that the to-be-logged-in account is a shared account, the account management center further includes: the account management center establishing a shared account management module, wherein the shared account management module is used to record a shared account name corresponding to a shared account, a login domain account allowed to be logged in by the shared account, and a login domain account state.

[0148] In an embodiment, the account management center determining that the to-be-logged-in account is a shared account specifically includes: the account management center obtaining a login account name in the to-be-logged-in account, traversing the shared account management module, judging whether there is a shared account name consistent with the login account name in the shared account management module, if not, determining that the to-be-logged-in account is a normal entity account, and if yes, determining that the to-be-logged-in account is a shared account.

[0149] In an embodiment, the account management center performing shared account authentication on the to-be-logged-in account according to the first login domain account and determining that the to-be-logged-in account is valid specifically includes: when the to-be-logged-in account is a shared account, obtaining all login domain accounts allowed to be logged in by the to-be-logged-in account, simultaneously obtaining the first login domain account, judging whether there is a second login domain account consistent with the first login domain account in the all login domain accounts, if not, determining that the to-be-logged-in account is invalid, and if yes, obtaining a login domain account state corresponding to the second login domain account; if the login domain account state corresponding to the second login domain account is valid, determining that the to-be-logged-in account is valid, and if the login domain account state corresponding to the second login domain account is invalid, determining that the to-be-logged-in account is invalid.

[0150] In an embodiment, after the account management center establishes the shared account management module, the account management center further includes: the account management center sets a role for each login domain account in the shared account, and sets a corresponding role permission for the role.

[0151] In summary, the authentication login method of the shared account provided by the embodiment of the application includes: the account management center authenticates the to-be-logged-in account input by the first user, and obtains the sixth dynamic verification code sent by the account management center, authenticates the sixth dynamic verification code, realizes two-factor authentication of the shared account, and improves the security of the shared account; and in the multi-user login scenario, the first login domain account used by the first user replaces the only entity mobile phone number that can be set in the existing shared account, and is used to receive the fifth dynamic verification code, so that when multiple users simultaneously log in, based on the different first login domain accounts used, each first login domain account can simultaneously receive the corresponding fifth dynamic verification code, and multiple people can simultaneously log in to the shared account, and the efficiency of simultaneous login of multiple people is improved.

[0152] Embodiment 4

[0153] Referring to Figure 4 , Figure 4 is a structural schematic diagram of an embodiment of a user terminal provided by the application, as Figure 4 shown, the device includes a first information acquisition module 401, a second information acquisition module 402, and a shared account authentication module 403, and specifically as follows:

[0154] The first information acquisition module 401 is configured to acquire a to-be-logged-in account input by a first user.

[0155] The second information acquisition module 402 is configured to acquire a second dynamic verification code input by the first user according to a first dynamic verification code displayed in a second user terminal; wherein the first dynamic verification code is acquired by the second user terminal sending a dynamic verification code request and a first login domain account corresponding to the second user terminal to a third-party verification code generation platform in response to the first user triggering a dynamic verification code request event, so that the third-party verification code generation platform sends the first dynamic verification code to the second user terminal according to the first login domain account.

[0156] The shared account authentication module 403 is configured to send the second dynamic verification code and the account to be logged in to the account management center, so that the account management center sends the second dynamic verification code to the third-party verification code generation platform after determining that the account to be logged in is a system account, so that the third-party verification code generation platform returns a first login domain account to the account management center after determining that the second dynamic verification code is correct according to the first dynamic verification code, so that the account management center performs shared account authentication on the account to be logged in according to the first login domain account after determining that the account to be logged in is a shared account, and feeds back first login success confirmation information when the account to be logged in is determined to be valid.

[0157] In an embodiment, the shared account authentication module 403 is configured to enable the account management center to further include a shared account management module before determining that the account to be logged in is a shared account, wherein the shared account management module is configured to record a shared account name corresponding to a shared account, a login domain account allowed to log in by the shared account, and a login domain account state.

[0158] In an embodiment, the shared account authentication module 403 is configured to enable the account management center to determine that the account to be logged in is a shared account, specifically including: the account management center acquires a login account name in the account to be logged in, traverses the shared account management module, judges whether there is a shared account name consistent with the login account name in the shared account management module, if not, determines that the account to be logged in is a normal entity account, and if yes, determines that the account to be logged in is a shared account.

[0159] In an embodiment, the shared account authentication module 403 is configured to perform shared account authentication on the account to be logged in according to the first login domain account, specifically including: when the account to be logged in is a shared account, acquiring all login domain accounts allowed to log in by the account to be logged in, acquiring the first login domain account at the same time, judging whether there is a second login domain account consistent with the first login domain account in the all login domain accounts, if not, determining that the account to be logged in is invalid, if yes, acquiring a login domain account state corresponding to the second login domain account; if the login domain account state corresponding to the second login domain account is valid, determining that the account to be logged in is valid, and if the login domain account state corresponding to the second login domain account is invalid, determining that the account to be logged in is invalid.

[0160] In an embodiment, the shared account authentication module 403 is further configured to determine that the to-be-logged-in account is a system account, and specifically includes: obtaining all account information in a target system, comparing the to-be-logged-in account with the all account information, and if there is first account information consistent with the to-be-logged-in account in the all account information, determining that the to-be-logged-in account is a system account in the target system, wherein the all account information includes shared account information and normal entity account information.

[0161] In an embodiment, after the shared account authentication module 403 establishes a shared account management module in the account management center, the shared account authentication module 403 is further configured to set a role for each login domain account in the shared account in the account management center, and set a corresponding role permission for the role.

[0162] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the user terminal described above can refer to the corresponding process in the foregoing method embodiment 1, and will not be repeated here.

[0163] It should be noted that the above embodiments of the user terminal are only illustrative, and the modules described as separate components can or can not be physically separated, and the components displayed as modules can or can not be physical units, i.e., they can be located in one place or distributed on multiple network units. According to actual needs, part or all of the modules can be selected to achieve the purpose of the present embodiment.

[0164] In summary, the user terminal provided by the embodiment of the present application is used to authenticate the to-be-logged-in account input by the first user through the account management center, and authenticate the second dynamic verification code through the third-party verification code generation platform, to realize double-factor authentication of the shared account, improve the security of the shared account, and in the multi-user login scenario, the first login domain account used by the first user is used to replace the only entity mobile phone number that can be set in the existing shared account based on the dynamic verification code acquisition module, to receive the first dynamic verification code, so that multiple users can simultaneously log in by using different first login domain accounts, so that each first login domain account can simultaneously receive the corresponding first dynamic verification code, to realize multi-user simultaneous login of the shared account and improve the efficiency of multi-user simultaneous login.

[0165] Embodiment 5

[0166] Referring to Figure 5 , Figure 5 is a structural schematic diagram of an embodiment of an account management center provided by the present application, as shown in Figure 5As shown, the device comprises a user terminal information receiving module 501, a first account authentication module 502, a third-party verification code generation platform information receiving module 503, and a second account authentication module 504, and specifically as follows:

[0167] The user terminal information receiving module 501 is configured to receive a third dynamic verification code and a to-be-logged-in account sent by a first user terminal, wherein the third dynamic verification code and the to-be-logged-in account are obtained by the first user terminal according to the input of a first user.

[0168] The first account authentication module 502 is configured to, after determining that the to-be-logged-in account is a system account, send the third dynamic verification code to the third-party verification code generation platform, so that the third-party verification code generation platform feeds back a first login domain account after determining that the third dynamic verification code is correct according to a fourth dynamic verification code generated by the third-party verification code generation platform.

[0169] The third-party verification code generation platform information receiving module 503 is configured to receive a first login domain account sent by a third-party verification code generation platform.

[0170] The second account authentication module 504 is configured to, after determining that the to-be-logged-in account is a shared account, perform shared account authentication on the to-be-logged-in account according to the first login domain account, and feed back first login success confirmation information to the first user terminal after determining that the to-be-logged-in account is valid.

[0171] In an embodiment, the third dynamic verification code in the user terminal information receiving module 501 is obtained by the first user terminal according to the input of a first user; specifically, a second user terminal sends a dynamic verification code request and a first login domain account corresponding to the second user terminal to a third-party verification code generation platform in response to a dynamic verification code request event triggered by the first user, so that the third-party verification code generation platform sends a fourth dynamic verification code to the second user terminal according to the first login domain account; and the second user terminal displays the fourth dynamic verification code, so that the first user inputs the third dynamic verification code in the first user terminal according to the fourth dynamic verification code.

[0172] In an embodiment, the first account authentication module 502 is configured to determine that the to-be-logged-in account is a system account, and specifically includes: obtaining all account information in a target system, comparing the to-be-logged-in account with the all account information, and if there is first account information consistent with the to-be-logged-in account in the all account information, determining that the to-be-logged-in account is a system account in the target system, wherein the all account information includes shared account information and ordinary entity account information.

[0173] In an embodiment, the second account authentication module 504 is further configured to, before determining that the to-be-logged-in account is a shared account, further include: establishing a shared account management module, wherein the shared account management module is configured to record a shared account name corresponding to the shared account, login domain accounts allowed to log in by the shared account, and a login domain account state.

[0174] In an embodiment, the second account authentication module 504 is configured to determine that the to-be-logged-in account is a shared account, and specifically includes: obtaining a login account name in the to-be-logged-in account, traversing the shared account management module, determining whether a shared account name in the shared account management module is consistent with the login account name, if not, determining that the to-be-logged-in account is a normal entity account, and if yes, determining that the to-be-logged-in account is a shared account.

[0175] In an embodiment, the second account authentication module 504 is configured to perform shared account authentication on the to-be-logged-in account according to the first login domain account, and determine that the to-be-logged-in account is valid, and specifically includes: when the to-be-logged-in account is a shared account, obtaining all login domain accounts allowed to log in by the to-be-logged-in account, and simultaneously obtaining the first login domain account, determining whether a second login domain account in the all login domain accounts is consistent with the first login domain account, if not, determining that the to-be-logged-in account is invalid, and if yes, obtaining a login domain account state corresponding to the second login domain account; if the login domain account state corresponding to the second login domain account is valid, determining that the to-be-logged-in account is valid, and if the login domain account state corresponding to the second login domain account is invalid, determining that the to-be-logged-in account is invalid.

[0176] In an embodiment, the second account authentication module 504, after establishing the shared account management module, is further configured to: set a role for each login domain account in the shared account, and set a corresponding role permission for the role.

[0177] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the account management center described above can refer to the corresponding process in the foregoing method embodiment 2, and will not be repeated here.

[0178] It should be noted that the embodiments of the account management center described above are only illustrative, and the modules described as separate components can or can not be physically separated, and the components displayed as modules can or can not be physical units, that is, they can be located in one place, or distributed on multiple network units. According to actual needs, part or all of the modules can be selected to achieve the purpose of the embodiment.

[0179] In summary, the account management center provided by the embodiment of the application realizes double-factor authentication of the shared account by using the second account authentication module to authenticate the to-be-logged-in account input by the first user and using the first account authentication module to authenticate the third dynamic verification code, improves the security of the shared account, and in the multi-user login scenario, the first login domain account used by the first user is used to replace the only entity mobile phone number that can be set in the existing shared account based on the user terminal information receiving module, so that the fourth dynamic verification code is received, so that when multiple users simultaneously log in, different first login domain accounts are used, so that each first login domain account can simultaneously receive the corresponding fourth dynamic verification code, and multiple people can simultaneously log in to the shared account, improving the efficiency of simultaneous login by multiple people.

[0180] Embodiment 6

[0181] Referring to Figure 6 , Figure 6 is a structural schematic diagram of an embodiment of a third-party verification code generation platform provided by the application, as Figure 6 shown, the device comprises a second user terminal information receiving module 601, a dynamic verification code sending module 602 and a dynamic verification code verification module 603, and specifically as follows:

[0182] The second user terminal information receiving module 601 is configured to receive a dynamic verification code request sent by a second user terminal and a first login domain account corresponding to the second user terminal, wherein the dynamic verification code request is generated by the second user terminal in response to a dynamic verification code request event triggered by a first user.

[0183] The dynamic verification code sending module 602 is configured to send a fifth dynamic verification code generated according to the first login domain account to the second user terminal, so that the first user terminal acquires a to-be-logged-in account input by a first user and acquires a sixth dynamic verification code input by the first user according to the fifth dynamic verification code displayed in the second user terminal, and then sends the sixth dynamic verification code to the account management center.

[0184] The dynamic verification code verification module 603 is configured to receive the sixth dynamic verification code sent by the account management center, and return the first login domain account to the account management center after determining that the sixth dynamic verification code is correct according to the fifth dynamic verification code, so that the account management center performs shared account authentication on the to-be-logged-in account according to the first login domain account after determining that the to-be-logged-in account is a shared account, and feeds back first login success confirmation information when determining that the to-be-logged-in account is valid.

[0185] In an embodiment, the dynamic verification code verification module 603 is configured to, before receiving the sixth dynamic verification code sent by the account management center, make the account management center determine whether the to-be-logged-in account is a system account, and send the sixth dynamic verification code to the third-party verification code generation platform only when the account management center determines that the to-be-logged-in account is a system account, so that the third-party verification code generation platform receives the sixth dynamic verification code sent by the account management center.

[0186] In an embodiment, the dynamic verification code verification module 603 is configured to make the account management center determine that the to-be-logged-in account is a system account specifically by: obtaining all account information in a target system, comparing the to-be-logged-in account with the all account information, and determining that the to-be-logged-in account is a system account in the target system if there is first account information consistent with the to-be-logged-in account in the all account information, wherein the all account information includes shared account information and normal entity account information.

[0187] In an embodiment, the dynamic verification code verification module 603 is configured to, before the account management center determines that the to-be-logged-in account is a shared account, further include: the account management center establishing a shared account management module, wherein the shared account management module is configured to record a shared account name corresponding to a shared account, login domain account names allowed to be logged in by the shared account, and login domain account states.

[0188] In an embodiment, the dynamic verification code verification module 603 is configured to make the account management center determine that the to-be-logged-in account is a shared account specifically by: the account management center obtaining a login account name in the to-be-logged-in account, traversing the shared account management module, determining whether there is a shared account name consistent with the login account name in the shared account management module, determining that the to-be-logged-in account is a normal entity account if not, and determining that the to-be-logged-in account is a shared account if yes.

[0189] In an embodiment, the dynamic verification code verification module 603 is configured to make the account management center perform shared account authentication on the to-be-logged-in account according to the first login domain account to determine that the to-be-logged-in account is valid specifically by: when the to-be-logged-in account is a shared account, obtaining all login domain account names allowed to be logged in by the to-be-logged-in account, simultaneously obtaining the first login domain account, determining whether there is a second login domain account consistent with the first login domain account in the all login domain account names, determining that the to-be-logged-in account is invalid if not, and determining that the to-be-logged-in account is valid if yes, obtaining a login domain account state corresponding to the second login domain account, determining that the to-be-logged-in account is valid if the login domain account state corresponding to the second login domain account is valid, and determining that the to-be-logged-in account is invalid if the login domain account state corresponding to the second login domain account is invalid.

[0190] In an embodiment, the dynamic verification code verification module 603 is configured to, after the account management center establishes the shared account management module, further include: setting a role for each login domain account in the shared account and setting a corresponding role permission for the role in the account management center.

[0191] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the third-party verification code generation platform described above can refer to the corresponding process in the foregoing method embodiment 3, which will not be repeated here.

[0192] It should be noted that the above-mentioned embodiments of the third-party verification code generation platform are only illustrative, and the modules described as separate components can or can not be physically separated, and the components displayed as modules can or can not be physical units, i.e., they can be located in one place or distributed on multiple network units; some or all of the modules can be selected to achieve the purpose of the present embodiment according to actual needs.

[0193] In summary, the third-party verification code generation platform provided by the embodiment of the present application authenticates the login account input by the first user through the account management center, obtains the sixth dynamic verification code sent by the account management center, authenticates the sixth dynamic verification code, realizes double-factor authentication of the shared account, and improves the security of the shared account; and in the multi-user login scenario, the first login domain account used by the first user replaces the only entity mobile phone number that can be set in the existing shared account, which is used to receive the fifth dynamic verification code, so that multiple users can simultaneously log in based on the different first login domain accounts used, and each first login domain account can receive the corresponding fifth dynamic verification code, which can realize multi-user simultaneous login to the shared account and improve the efficiency of multi-user simultaneous login.

[0194] Embodiment 7

[0195] Referring to Figure 7 , Figure 7 is a structural schematic diagram of an embodiment of a login system provided by the present application, as Figure 7 shown, the device includes a user terminal 701, an account management center 702, and a third-party verification code generation platform 703, specifically as follows:

[0196] The user terminal 701 is in communication connection with the account management center 702 and the third-party verification code generation platform 703, respectively, and the account management center 702 is in communication connection with the third-party verification code generation platform 703;

[0197] The user terminal 701 performs the shared account authentication login method as described in any one of the above embodiments 1.

[0198] The account management center 702 performs the shared account authentication login method as described in any one of the above embodiments 2.

[0199] The third-party verification code generation platform 703 performs the shared account authentication login method as described in the above embodiment 3.

[0200] In summary, the login system provided by the embodiments of the present application solves the problem that the account authentication cannot be effectively implemented in the case of shared account shared by multiple people, and can achieve simultaneous login of the shared account by multiple people, improve the login efficiency of multiple people, and can also perform two-factor authentication on the account to be logged in, thereby improving the security of the shared account.

[0201] Further, the embodiments of the present application also provide a terminal device, which comprises a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, and the processor implements the shared account authentication login method as described in any one of the above embodiments when executing the computer program.

[0202] Further, the embodiments of the present application also provide a computer readable storage medium, which comprises a stored computer program, wherein the computer program controls the device where the computer readable storage medium is located to perform the shared account authentication login method as described in any one of the above embodiments when running.

[0203] Further, the embodiments of the present application also provide a computer program product, which makes the computer device implement the shared account authentication login method as described in any one of the above embodiments when running on the computer device.

[0204] To sum up, the authentication login method and device of a shared account disclosed by the application, by sending the first login domain account corresponding to the second user terminal to the third-party verification code generation platform, so that the third-party verification code generation platform sends the first dynamic verification code to the second user terminal according to the first login domain account; the second dynamic verification code input by the first user and the account to be logged in are sent to the account management center, so that the account management center sends the second dynamic verification code to the third-party verification code generation platform after determining that the account to be logged in is a system account, so that the third-party verification code generation platform determines that the second dynamic verification code is correct, and sends the first login domain account to the account management center, so that the account management center determines that the account to be logged in is valid according to the first login domain account, and feeds back the first login success confirmation information; compared with the prior art, the application can realize two-factor authentication of the shared account, and improve the security of the shared account.

[0205] The above description is only the preferred embodiment of the application, and it should be pointed out that for ordinary skilled persons in the art, without departing from the technical principles of the application, a number of improvements and replacements can be made, and these improvements and replacements should be considered as the protection scope of the application.

Claims

1. A method of authenticating a login of a shared account, the method comprising: The method comprises: obtaining a login account input by a first user; obtaining a second dynamic verification code input by the first user according to a first dynamic verification code displayed on a second user terminal; wherein the first dynamic verification code is obtained by the second user terminal sending a dynamic verification code request to a third-party verification code generation platform in response to the first user triggering a dynamic verification code request event, and a first login domain account corresponding to the second user terminal, so that the third-party verification code generation platform sends the first dynamic verification code to the second user terminal according to the first login domain account; sending the second dynamic verification code and the login account to an account management center, so that the account management center sends the second dynamic verification code to the third-party verification code generation platform after determining that the login account is a system account, so that the third-party verification code generation platform returns a first login domain account to the account management center after determining that the second dynamic verification code is correct according to the first dynamic verification code, so that the account management center performs shared account authentication on the login account according to the first login domain account after determining that the login account is a shared account, and feeds back first login success confirmation information when determining that the login account is valid. The step of performing shared account authentication on the login account according to the first login domain account comprises: obtaining all login domain accounts allowed to log in by the login account, and obtaining the first login domain account at the same time; determining whether there is a second login domain account consistent with the first login domain account in the all login domain accounts; if not, determining that the login account is invalid; if yes, obtaining a login domain account state corresponding to the second login domain account; if the login domain account state corresponding to the second login domain account is valid, determining that the login account is valid; if the login domain account state corresponding to the second login domain account is invalid, determining that the login account is invalid.

2. An authentication login method of a shared account, characterized by, The method comprises: receiving a third dynamic verification code and a login account sent by a first user terminal; wherein the third dynamic verification code and the login account are obtained by the first user terminal according to the input of a first user; after determining that the login account is a system account, sending the third dynamic verification code to a third-party verification code generation platform, so that the third-party verification code generation platform feeds back a first login domain account after determining that the third dynamic verification code is correct according to a fourth dynamic verification code generated by the third-party verification code generation platform; receiving the first login domain account sent by the third-party verification code generation platform; after determining that the login account is a shared account, performing shared account authentication on the login account according to the first login domain account, and feeding back first login success confirmation information to the first user terminal when determining that the login account is valid. The step of performing shared account authentication on the to-be-logged-in account according to the first login domain account comprises: acquiring all login domain accounts allowed to be logged in by the to-be-logged-in account, acquiring the first login domain account, judging whether a second login domain account consistent with the first login domain account exists in the all login domain accounts, if not, determining that the to-be-logged-in account is invalid, and if yes, acquiring a login domain account state corresponding to the second login domain account; if the login domain account state corresponding to the second login domain account is valid, determining that the to-be-logged-in account is valid, and if the login domain account state corresponding to the second login domain account is invalid, determining that the to-be-logged-in account is invalid. The third dynamic verification code is obtained by the first user terminal according to the input of the first user, specifically: the second user terminal responds to the dynamic verification code request event triggered by the first user, sends a dynamic verification code request and the first login domain account corresponding to the second user terminal to a third-party verification code generation platform, so that the third-party verification code generation platform sends a fourth dynamic verification code to the second user terminal according to the first login domain account; and the second user terminal displays the fourth dynamic verification code, so that the first user inputs the third dynamic verification code in the first user terminal according to the fourth dynamic verification code.

3. The authentication login method of a shared account according to claim 2, wherein, The third dynamic verification code is obtained by the first user terminal according to the input of the first user, specifically: the second user terminal responds to the dynamic verification code request event triggered by the first user, sends a dynamic verification code request and the first login domain account corresponding to the second user terminal to a third-party verification code generation platform, so that the third-party verification code generation platform sends a fourth dynamic verification code to the second user terminal according to the first login domain account; and the second user terminal displays the fourth dynamic verification code, so that the first user inputs the third dynamic verification code in the first user terminal according to the fourth dynamic verification code. The step of determining that the to-be-logged-in account is a system account comprises: Acquiring all account information in a target system, comparing the to-be-logged-in account with the all account information, if first account information consistent with the to-be-logged-in account exists in the all account information, determining that the to-be-logged-in account is a system account in the target system, wherein the all account information comprises shared account information and common entity account information.

4. The authentication login method of a shared account according to claim 2, wherein, The method further comprises, before determining that the to-be-logged-in account is a shared account: Establishing a shared account management module, wherein the shared account management module is used for recording a shared account name corresponding to a shared account, login domain accounts allowed to be logged in by the shared account, and a login domain account state.

5. The authentication login method of a shared account according to claim 2, wherein, The step of determining that the to-be-logged-in account is a shared account comprises: Acquiring a login account name in the to-be-logged-in account, traversing the shared account management module, judging whether a shared account name consistent with the login account name exists in the shared account management module, if not, determining that the to-be-logged-in account is a common entity account, and if yes, determining that the to-be-logged-in account is a shared account.

6. The authentication login method of a shared account according to claim 5, wherein, ​ ​ 7. The authentication login method of a shared account according to claim 5, wherein, The shared account authentication according to the first login domain account includes: acquiring all login domain accounts allowed to be logged in by the to-be-logged-in account, acquiring the first login domain account, and judging whether a second login domain account consistent with the first login domain account exists in the all login domain accounts; if not, determining that the to-be-logged-in account is invalid; if yes, acquiring a login domain account state corresponding to the second login domain account. The shared account authentication according to the first login domain account includes: acquiring all login domain accounts allowed to be logged in by the to-be-logged-in account, acquiring the first login domain account, and judging whether a second login domain account consistent with the first login domain account exists in the all login domain accounts; if not, determining that the to-be-logged-in account is invalid; if yes, acquiring a login domain account state corresponding to the second login domain account. After the shared account management module is established, the method further includes:

8. The authentication login method of a shared account according to claim 5, wherein, Roles are set for each login domain account in the shared account, and corresponding role permissions are set for the roles. The method includes:

9. An authentication login method of a shared account, characterized by, receiving a dynamic verification code request sent by a second user terminal and a first login domain account corresponding to the second user terminal, wherein the dynamic verification code request is generated by the second user terminal in response to a dynamic verification code request event triggered by a first user; sending a fifth dynamic verification code generated according to the first login domain account to the second user terminal, so that the first user terminal acquires a to-be-logged-in account input by the first user and acquires a sixth dynamic verification code input by the first user according to the fifth dynamic verification code displayed in the second user terminal, and then sends the sixth dynamic verification code to an account management center; receiving the sixth dynamic verification code sent by the account management center, and returning the first login domain account to the account management center after determining that the sixth dynamic verification code is correct according to the fifth dynamic verification code, so that the account management center performs shared account authentication on the to-be-logged-in account according to the first login domain account after determining that the to-be-logged-in account is a shared account, and feeds back first login success confirmation information when determining that the to-be-logged-in account is valid. The shared account authentication according to the first login domain account includes: acquiring all login domain accounts allowed to be logged in by the to-be-logged-in account, acquiring the first login domain account, and judging whether a second login domain account consistent with the first login domain account exists in the all login domain accounts; if not, determining that the to-be-logged-in account is invalid; if yes, acquiring a login domain account state corresponding to the second login domain account. The method includes:

10. A user terminal, characterized by a first information acquisition module, a second information acquisition module, and a shared account authentication module; the first information acquisition module is configured to acquire a to-be-logged-in account input by a first user; ​ The second information obtaining module is configured to obtain a second dynamic verification code input by the first user according to a first dynamic verification code displayed on the second user terminal; wherein the first dynamic verification code is obtained by the second user terminal sending a dynamic verification code request to a third-party verification code generation platform in response to the first user triggering a dynamic verification code request event, and a first login domain account corresponding to the second user terminal, so that the third-party verification code generation platform sends the first dynamic verification code to the second user terminal according to the first login domain account; The shared account authentication module is configured to send the second dynamic verification code and the account to be logged in to the account management center, so that the account management center sends the second dynamic verification code to the third-party verification code generation platform after determining that the account to be logged in is a system account, so that the third-party verification code generation platform returns a first login domain account to the account management center after determining that the second dynamic verification code is correct according to the first dynamic verification code, so that the account management center performs shared account authentication on the account to be logged in according to the first login domain account after determining that the account to be logged in is a shared account, and feeds back first login success confirmation information when determining that the account to be logged in is valid. The step of performing shared account authentication on the account to be logged in according to the first login domain account comprises: obtaining all login domain accounts allowed to be logged in by the account to be logged in, obtaining the first login domain account at the same time, determining whether there is a second login domain account consistent with the first login domain account in the all login domain accounts, determining that the account to be logged in is invalid if not, and determining that the second login domain account corresponding to the login domain account state is valid if yes.

11. An account management center, characterized by Comprise: A user terminal information receiving module, a first account authentication module, a third-party verification code generation platform information receiving module, and a second account authentication module; The user terminal information receiving module is configured to receive a third dynamic verification code and an account to be logged in sent by a first user terminal; wherein the third dynamic verification code and the account to be logged in are obtained by the first user terminal according to the input of a first user; The first account authentication module is configured to send the third dynamic verification code to the third-party verification code generation platform after determining that the account to be logged in is a system account, so that the third-party verification code generation platform feeds back a first login domain account after determining that the third dynamic verification code is correct according to a fourth dynamic verification code generated by the third-party verification code generation platform; The third-party verification code generation platform information receiving module is configured to receive a first login domain account sent by a third-party verification code generation platform The second account authentication module is configured to, after determining that the to-be-logged-in account is a shared account, perform shared account authentication on the to-be-logged-in account according to the first login domain account, and feed back first login success confirmation information to the first user terminal after determining that the to-be-logged-in account is valid. The shared account authentication on the to-be-logged-in account according to the first login domain account comprises: acquiring all login domain accounts allowed to be logged in by the to-be-logged-in account, acquiring the first login domain account, determining whether there is a second login domain account consistent with the first login domain account in the all login domain accounts, determining that the to-be-logged-in account is invalid if there is no second login domain account consistent with the first login domain account, acquiring a login domain account state corresponding to the second login domain account if there is a second login domain account consistent with the first login domain account, determining that the to-be-logged-in account is valid if the login domain account state corresponding to the second login domain account is valid, and determining that the to-be-logged-in account is invalid if the login domain account state corresponding to the second login domain account is invalid. The third dynamic verification code is acquired by the first user terminal according to the input of the first user, specifically: the second user terminal responds to a dynamic verification code request event triggered by the first user, sends a dynamic verification code request and the first login domain account corresponding to the second user terminal to a third-party verification code generation platform, so that the third-party verification code generation platform sends a fourth dynamic verification code to the second user terminal according to the first login domain account; and the second user terminal displays the fourth dynamic verification code, so that the first user inputs the third dynamic verification code in the first user terminal according to the fourth dynamic verification code.

12. A third party validation code generation platform, comprising: The third dynamic verification code is acquired by the first user terminal according to the input of the first user, specifically: the second user terminal responds to a dynamic verification code request event triggered by the first user, sends a dynamic verification code request and the first login domain account corresponding to the second user terminal to a third-party verification code generation platform, so that the third-party verification code generation platform sends a fourth dynamic verification code to the second user terminal according to the first login domain account; and the second user terminal displays the fourth dynamic verification code, so that the first user inputs the third dynamic verification code in the first user terminal according to the fourth dynamic verification code. The second user terminal information receiving module is configured to receive a dynamic verification code request and the first login domain account corresponding to the second user terminal sent by the second user terminal, wherein the dynamic verification code request is generated by the second user terminal in response to a dynamic verification code request event triggered by the first user; The dynamic verification code sending module is configured to send a fifth dynamic verification code generated according to the first login domain account to the second user terminal, so that the first user terminal acquires the to-be-logged-in account input by the first user and acquires a sixth dynamic verification code input by the first user according to the fifth dynamic verification code displayed in the second user terminal, and then sends the sixth dynamic verification code to the account management center; The dynamic verification code verification module is configured to receive the sixth dynamic verification code sent by the account management center, return the first login domain account to the account management center after determining that the sixth dynamic verification code is correct according to the fifth dynamic verification code, so that the account management center performs shared account authentication on the to-be-logged-in account according to the first login domain account after determining that the to-be-logged-in account is a shared account, and feeds back first login success confirmation information after determining that the to-be-logged-in account is valid. ​ The step of performing shared account authentication on the to-be-logged-in account according to the first login domain account comprises: acquiring all login domain accounts allowed to be logged in by the to-be-logged-in account, and simultaneously acquiring the first login domain account; judging whether a second login domain account consistent with the first login domain account exists in the all login domain accounts; if not, determining that the to-be-logged-in account is invalid; if yes, acquiring a login domain account state corresponding to the second login domain account; if the login domain account state corresponding to the second login domain account is valid, determining that the to-be-logged-in account is valid; if the login domain account state corresponding to the second login domain account is invalid, determining that the to-be-logged-in account is invalid.

13. A login system, characterized by The method comprises: a user terminal, an account management center and a third-party verification code generation platform; wherein the user terminal is in communication connection with the account management center and the third-party verification code generation platform, and the account management center is in communication connection with the third-party verification code generation platform; the user terminal executes the shared account authentication login method according to claim 1; the account management center executes the shared account authentication login method according to any one of claims 2-8; the third-party verification code generation platform executes the shared account authentication login method according to claim 9.

14. A terminal device, comprising: a processor, a memory and a computer program stored in the memory and configured to be executed by the processor, wherein the processor executes the computer program to implement the shared account authentication login method according to any one of claims 1-9.

15. A computer-readable storage medium, characterized in that, The computer readable storage medium comprises a stored computer program, wherein the computer program controls a device where the computer readable storage medium is located to execute the shared account authentication login method according to any one of claims 1-9 when the computer program runs.

16. A computer program product, characterised in that, When the computer program product runs on a computer device, the computer device implements the shared account authentication login method according to any one of claims 1-9.

Images