Server management method, device, computer equipment and storage medium

Abstract

The present application relates to a server management method, device, computer equipment and storage medium, and relates to the field of information security. The method comprises: obtaining user information of each user in the target server, determining the target login password of each user according to the password generation rules corresponding to each user in the target server, and constructing a first target password file of the target server according to the user information of each user and the target login password of each user, sending a management request to the target server, wherein the management request includes the target login password of each user, and the management request is used to instruct the target server to update the initial login password of each user in the password file of the target server according to the target login password of each user, and obtain the second target password file of the target server. The use of this method can avoid management errors and irregular management phenomena, and improve the efficiency of server management.

Description

Technical Field

[0001] The present application relates to the field of information security technology, and in particular to a server management method, apparatus, computer equipment, and storage medium. Background Art

[0002] With the development of computer technology, servers have emerged. Due to their advantages over ordinary computers, such as faster operation and higher load capacity, servers have become widely used. To achieve unified management of multiple servers and ensure server data security, server management methods have emerged. These methods enable unified server login and operation.

[0003] In the traditional server management method, staff are required to manage each server one by one. Due to the large number of servers to be managed, manual management may lead to irregularities and errors, resulting in extremely low management efficiency. Summary of the Invention

[0004] Based on this, it is necessary to provide a server management method, device, computer equipment, computer-readable storage medium and computer program product that can improve management efficiency in response to the above technical problems.

[0005] In a first aspect, the present application provides a server management method. The method comprises:

[0006] Get the user information of each user in the target server;

[0007] Determine the target login password of each user according to the password generation rule corresponding to each user in the target server;

[0008] Constructing a first target password file of the target server according to the user information of each user and the target login password of each user;

[0009] A management request is sent to the target server, wherein the management request includes the target login password of each user. The management request is used to instruct the target server to update the initial login password of each user in the password file of the target server according to the target login password of each user, and obtain the second target password file of the target server.

[0010] In one embodiment, the method further comprises:

[0011] authenticating the user to be logged in, in response to an authentication request sent by the terminal side, wherein the authentication request includes user login information of the user to be logged in;

[0012] In the case that the user to be logged in is authenticated, determining the server to be logged in from each of the target servers;

[0013] Obtaining the first target password file corresponding to the server to be logged in;

[0014] According to the user login information, obtaining the target login password corresponding to the user to be logged in from the first target password file corresponding to the server to be logged in;

[0015] Sending a login request to the server to be logged in, the login request including the target login password corresponding to the user to be logged in, so that the server to be logged in performs a match in the second target password file corresponding to the server to be logged in, according to the target login password corresponding to the user to be logged in, to obtain a corresponding matching result;

[0016] When the matching result indicates a successful match, a login success feedback message for the server to be logged in is sent to the terminal side, so that the terminal side jumps to the system interface of the server to be logged in in response to the login success feedback message.

[0017] In one embodiment, the method further comprises:

[0018] Obtaining the operating status of each server to be managed, wherein the operating status includes a working state or a non-working state;

[0019] The server to be managed, whose operating state is the non-working state, is used as the target server.

[0020] In one embodiment, before determining the target login password of each user according to the password generation rule corresponding to each user in the target server, the method further includes:

[0021] For any of the users, obtaining the user attributes corresponding to the user in the target server;

[0022] Determining password generation rules corresponding to each user according to the user attributes corresponding to each user in the target server, wherein the password generation rules corresponding to different user attributes have different complexities;

[0023] Alternatively, the security level of the target server is obtained, and the password generation rule corresponding to each user is determined according to the security level of the target server and the user attributes of each user.

[0024] In one embodiment, the method further comprises:

[0025] Obtaining a locked user in each target server, wherein the user's login status includes a first status or a second status, the first status being used to indicate that the user is allowed to log in to the target server, and the second status being used to indicate that the user is prohibited from logging in to the target server, and the locked user is a user whose login status is the second status;

[0026] For any of the target servers, in response to an unlock request, determining a new target login password according to the password generation rule corresponding to the locked user in the target server;

[0027] According to the new target login password, the target login password of the locked user in the first target password file and the target login password of the locked user in the second target password file are updated, and the login status of the locked user is updated to the first status.

[0028] In one embodiment, the target server includes multiple applications, and the method further includes:

[0029] Obtaining verification information input by the user to be logged in for the target application;

[0030] Sending an application login request to the server to be logged in according to the verification information, wherein the application login request is used to instruct the server to be logged in to perform application login verification according to the verification information and obtain an application login verification result;

[0031] If the application login verification result indicates that the verification has been passed, the key corresponding to the user to be logged in is obtained, and if the key corresponding to the user to be logged in is authenticated, the application login password of the user to be logged in is obtained to log in to the target application according to the application login password.

[0032] In a second aspect, the present application further provides a server management device. The device includes:

[0033] The first acquisition module is used to obtain user information of each user in the target server;

[0034] A first determining module, configured to determine a target login password for each user according to a password generation rule corresponding to each user in the target server;

[0035] A construction module, configured to construct a first target password file of the target server according to the user information of each user and the target login password of each user;

[0036] The first sending module sends a management request to the target server, where the management request includes the target login password of each user. The management request is used to instruct the target server to update the initial login password of each user in the password file of the target server according to the target login password of each user, so as to obtain the second target password file of the target server.

[0037] In one embodiment, the apparatus further comprises:

[0038] An authentication module, configured to authenticate the user to be logged in in response to an authentication request of the user to be logged in sent by the terminal side, wherein the authentication request includes user login information of the user to be logged in;

[0039] A second determining module is configured to determine a server to be logged in from each of the target servers if the user to be logged in is authenticated;

[0040] A second acquisition module is used to obtain the first target password file corresponding to the server to be logged in;

[0041] A third acquisition module is used to obtain the target login password corresponding to the user to be logged in from the first target password file corresponding to the server to be logged in according to the user login information;

[0042] a second sending module, configured to send a login request to the server to be logged in, wherein the login request includes the target login password corresponding to the user to be logged in, so that the server to be logged in performs a match in the second target password file corresponding to the server to be logged in, according to the target login password corresponding to the user to be logged in, to obtain a corresponding matching result;

[0043] The third sending module is used to send login success feedback information for the server to be logged in to the terminal side when the matching result indicates a successful match, so that the terminal side jumps to the system interface of the server to be logged in in response to the login success feedback information.

[0044] In one embodiment, the apparatus further comprises:

[0045] A third acquisition module is used to obtain the operating status of each server to be managed, wherein the operating status includes a working state or a non-working state;

[0046] The third determining module is configured to use the server to be managed, whose operating state is the non-working state, as the target server.

[0047] In one embodiment, the apparatus further comprises:

[0048] A fourth acquisition module is configured to acquire, for any of the users, user attributes corresponding to the user in the target server;

[0049] a fourth determining module, configured to determine a password generation rule corresponding to each user according to a user attribute corresponding to each user in the target server, wherein the password generation rules corresponding to different user attributes have different complexities;

[0050] Alternatively, the fourth determining module is further configured to obtain a security level of the target server, and determine the password generation rule corresponding to each user according to the security level of the target server and the user attributes of each user.

[0051] In one embodiment, the apparatus further comprises:

[0052] a fifth acquisition module, configured to acquire a locked user in each target server, wherein the user's login status includes a first status or a second status, the first status being used to indicate that the user is allowed to log in to the target server, and the second status being used to indicate that the user is prohibited from logging in to the target server, and the locked user is a user whose login status is the second status;

[0053] a fifth determining module, configured to determine, for any of the target servers, in response to an unlock request, a new target login password according to the password generation rule corresponding to the locked user in the target server;

[0054] An updating module is used to update the target login password of the locked user in the first target password file and the target login password of the locked user in the second target password file according to the new target login password, and update the login status of the locked user to the first status.

[0055] In one embodiment, the target server includes multiple applications, and the apparatus further includes:

[0056] A sixth acquisition module, configured to acquire verification information input by the user to be logged in for the target application;

[0057] A fourth sending module is configured to send an application login request to the server to be logged in according to the verification information, wherein the application login request is used to instruct the server to be logged in to perform application login verification according to the verification information to obtain an application login verification result;

[0058] The seventh acquisition module is used to obtain the key corresponding to the user to be logged in when the application login verification result indicates that the verification has been passed, and to obtain the application login password of the user to be logged in when the key corresponding to the user to be logged in has passed the authentication, so as to log in to the target application according to the application login password.

[0059] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are performed:

[0060] Get the user information of each user in the target server;

[0061] Determine the target login password of each user according to the password generation rule corresponding to each user in the target server;

[0062] Constructing a first target password file of the target server according to the user information of each user and the target login password of each user;

[0063] A management request is sent to the target server, wherein the management request includes the target login password of each user. The management request is used to instruct the target server to update the initial login password of each user in the password file of the target server according to the target login password of each user, and obtain the second target password file of the target server.

[0064] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the following steps:

[0065] Get the user information of each user in the target server;

[0066] Determine the target login password of each user according to the password generation rule corresponding to each user in the target server;

[0067] Constructing a first target password file of the target server according to the user information of each user and the target login password of each user;

[0068] A management request is sent to the target server, wherein the management request includes the target login password of each user. The management request is used to instruct the target server to update the initial login password of each user in the password file of the target server according to the target login password of each user, and obtain the second target password file of the target server.

[0069] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the following steps:

[0070] Get the user information of each user in the target server;

[0071] Determine the target login password of each user according to the password generation rule corresponding to each user in the target server;

[0072] Constructing a first target password file of the target server according to the user information of each user and the target login password of each user;

[0073] A management request is sent to the target server, wherein the management request includes the target login password of each user. The management request is used to instruct the target server to update the initial login password of each user in the password file of the target server according to the target login password of each user, and obtain the second target password file of the target server.

[0074] The above-mentioned server management method, device, computer equipment, storage medium and computer program product obtain the user information of each user in the target server, determine the target login password of each user according to the password generation rules corresponding to each user in the target server, and construct a first target password file of the target server based on the user information of each user and the target login password of each user, and send a management request to the target server. The management request includes the target login password of each user. The management request is used to instruct the target server to update the initial login password of each user in the password file of the target server according to the target login password of each user, so as to obtain the second target password file of the target server. Based on the above-mentioned server management method, device, computer equipment, storage medium and computer program product, the method can be applied to the management server to update the initial login password known to the user to the target login password unknown to the user, and the constructed first target password file contains the target login password of each user of the target server. At this time, the user can no longer log in to the target server by entering the initial login password to the target server. The user needs to send the user's target login password to the target server through the management server storing the first target password file to log in to the target server. That is, by updating the login password, the management of each target server is achieved. Through the above-mentioned method, the standardization of server management steps is achieved, the irregular management and management errors are avoided, and the management efficiency is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0075] Figure 1 1 is a flow chart of a server management method according to an embodiment;

[0076] Figure 2 1 is a flow chart of a server management method according to another embodiment;

[0077] Figure 3 1 is a flow chart of a server management method according to another embodiment;

[0078] Figure 4 1 is a flow chart of a server management method according to another embodiment;

[0079] Figure 5 1 is a flow chart of a server management method according to another embodiment;

[0080] Figure 6 1 is a flow chart of a server management method according to another embodiment;

[0081] Figure 7 This is a structural block diagram of a server management device in one embodiment;

[0082] Figure 8 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0083] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0084] In one embodiment, Figure 1 As shown, a server management method is provided. This embodiment uses the method applied to the management server as an example for illustration. It is understandable that the method can also be applied to a terminal, or to a system including a terminal and a management server, and is implemented through interaction between the terminal and the management server. In this embodiment, the method includes the following steps:

[0085] Step 102: Obtain user information of each user in the target server.

[0086] The target server is a server to be managed, and each target server stores a password file that stores user information for each user on the target server. In this embodiment of the present application, each target server can be logged in through a communication protocol, for example, through SSH, TELNET, FTP, etc., and the password file stored in the target server can be read to obtain the user information of each user from the password file.

[0087] In this embodiment, user information is information that represents the user. Different users correspond to different user information. User information can be used to distinguish between users, and users can be identified through user information. User information can be a user name, for example, user A's user information is A, and user B's user information is B. User information can also be a user ID, for example, user A's user ID is 1, and user B's user ID is 2.

[0088] It should be noted that the above-mentioned user information is a user name or user ID, which is only an example in this embodiment. In actual application, the user information can be any information that can represent the user. The embodiment of this application does not specifically limit the specific content of the user information.

[0089] Step 104: Determine the target login password for each user according to the password generation rules corresponding to each user in the target server.

[0090] In an embodiment of the present application, the password file stored in the target server also includes the initial login password of each user, wherein the initial login password is the password that the user needs to enter into the target server when logging into the target server when the target server is not managed.

[0091] On the target server, the login passwords used by users to log in to the target server must meet certain password rules. A target login password can be generated for each user based on the password generation rules corresponding to each user on the target server. For example, if password generation rule 1 for user A and user B is: the password must be 9 characters long, with the first 3 characters being English letters (uppercase and lowercase) and the last 6 characters being Arabic numerals, then user A's target login password A can be determined to be ABC123456, and user B's target login password B can be determined to be ASx543789.

[0092] Step 106: construct a first target password file of the target server based on the user information of each user and the target login password of each user.

[0093] In this embodiment of the present application, a first target password file of the target server can be constructed based on the user information and target login password of each user, where the user information can be one of the user's username, work ID, user IP address, etc. For example, taking the above example, where the user information is the username, target server 1 includes user A and user B, where A and B are the user's usernames, respectively, user A's target login password A is ABC123456, and user B's target login password B is ASx543789. Then, the first target password file 1 constructed for target server 1 includes: A-ABC123456, B-ASx543789.

[0094] Step 108: Send a management request to the target server. The management request includes the target login password of each user. The management request is used to instruct the target server to update the initial login password of each user in the password file of the target server according to the target login password of each user, and obtain the second target password file of the target server.

[0095] In an embodiment of the present application, the management server can send a management request to the target server, wherein the management request includes the target login password of each user. After receiving the management request, the target server will respond to the management request and update the initial login password of the user in the password file stored in the target server to the target login password of the user. After completing the update of all initial login passwords, the second target password file of the target server can be obtained.

[0096] For example, taking the target server 1 as an example, the password file 1 of the target server 1 includes A-initial login password A, B-initial login password B, the target login password A of user A is ABC123456, and the target login password B of user B is ASx543789. The second target password file 1 obtained after the update includes: A-ABC123456, B-ASx543789.

[0097] In an embodiment of the present application, the content of the first target password file stored in the management server is the same as the content of the second target password file stored in the target server. At this time, the user can no longer log in to the target server with the initial login password, and the user cannot obtain the target login password. Therefore, the user needs to log in to each target server through the management server and send operation instructions to each target server through the management server. That is, by updating the password of each user to log in to the target server, the management of the target server is achieved.

[0098] In the above-mentioned server management method, the method can be applied to the managed server, updating the initial login password known to the user to the target login password unknown to the user, and the constructed first target password file contains the target login password of each user of the target server. At this time, the user can no longer log in to the target server by entering the initial login password to the target server. The user needs to send the user's target login password to the target server through the management server storing the first target password file to log in to the target server. That is, by updating the login password, the management of each target server is realized. Through the above-mentioned method, the standardization of the server management steps is realized, the irregular management and management errors are avoided, and the management efficiency is improved.

[0099] In one embodiment, Figure 2 As shown, the method further includes:

[0100] Step 202: authenticating the user to be logged in in response to the authentication request of the user to be logged in sent by the terminal side, wherein the authentication request includes the user login information of the user to be logged in.

[0101] In an embodiment of the present application, when the user to be logged in logs in to any server to be logged in, the display interface on the terminal side will display a user authentication page, and the user to be logged in needs to enter user login information on the user authentication page, where the user login information includes the user information and authentication password of the user to be logged in. The terminal side will send an authentication request for the user to be logged in to the managed server based on the authentication information.

[0102] The management server responds to the authentication request and authenticates the user to be logged in. The database of the management server stores the user information of each user and the authentication password corresponding to each user. When the database contains the user information of the user to be logged in, the authentication password corresponding to the user information in the database is compared with the authentication password entered by the user to be logged in. When the above two authentication passwords are the same, the user to be logged in passes the authentication.

[0103] Step 204: When the user to be logged in passes the authentication, a server to be logged in is determined from the target servers.

[0104] In an embodiment of the present application, when the user to be logged in passes the authentication, the management server will feedback the authentication pass information to the terminal side, and the terminal side will jump to the login page in response to the authentication pass information. The user to be logged in can enter the server information of the server to be logged in on the login page, where the server information can be the IP address of the server to be logged in or the server name of the server to be logged in.

[0105] The terminal side is used to send the server information to the management server, and the management server can determine the server to be logged in from each target server based on the server information.

[0106] Step 206: Obtain a first target password file corresponding to the server to be logged in.

[0107] In an embodiment of the present application, after determining the server to be logged in, the first target password file corresponding to the server to be logged in can be obtained from multiple first target password files stored in the managed server.

[0108] Step 208: According to the user login information, obtain the target login password corresponding to the user to be logged in from the first target password file corresponding to the server to be logged in.

[0109] In an embodiment of the present application, the target login password corresponding to the user to be logged in can be obtained from the first target password file corresponding to the server to be logged in, based on the user information in the user login information. For example, if the first target password file corresponding to the server to be logged in includes: A - target login password A, B - target login password B, and C - target login password C, and the user information of the user to be logged in is A, then the target login password obtained from the first target password file is target login password A.

[0110] Step 210: Send a login request to the server to be logged in, where the login request includes the target login password corresponding to the user to be logged in, so that the server to be logged in matches the target login password corresponding to the user to be logged in in the second target password file corresponding to the server to be logged in, and obtains a corresponding matching result.

[0111] In an embodiment of the present application, after obtaining the target login password corresponding to the user to be logged in, the managing server can send a login request to the server to be logged in, wherein the login request includes the target password file corresponding to the user to be logged in. After the target server to be logged in receives the login request, it matches the target login password corresponding to the user to be logged in in the second target password file. When the target login password is included in the second target password file, a matching result indicating a successful match is obtained.

[0112] Step 212: If the matching result indicates a successful match, a login success feedback message for the server to be logged in is sent to the terminal side, so that the terminal side jumps to the system interface of the server to be logged in in response to the login success feedback message.

[0113] In an embodiment of the present application, when the matching result indicates a successful match, it means that the user to be logged in has successfully logged in to the server to be logged in. The server to be logged in can send a login success feedback message for the server to be logged in to the terminal side through the management server. After the terminal side receives the login success feedback message, it can jump to the system interface of the server to be logged in.

[0114] In the embodiment of the present application, in response to the authentication request of the user to be logged in, the user to be logged in is authenticated. Only if the authentication is passed can the user to be logged in continue to log in to the server to be logged in, thereby ensuring the system security of each target server. Moreover, after each target server is managed, the user can log in to multiple target servers through one server and manage each target server through the server, which is conducive to the unified management of each target server.

[0115] In one embodiment, security policies can also be configured in the management server, where the security policies can be formulated by staff, and the security policies can include user authority control, high-risk command interception, etc. When a user logs in to a target server through the management server, the user needs to input the operation instructions into the management server, and the management server sends the operation instructions to the target server. In the above process, when the user's operation instructions exceed the corresponding user authority, or the operation instructions are identified as high-risk commands, the management server can directly interrupt the operation instructions (that is, the management server will not send the operation instructions to the target server).

[0116] This embodiment only requires configuring security policies on the managed server to achieve security management of multiple target servers, simplifies the workflow and steps for staff to maintain each target server, and improves the management efficiency of the target servers.

[0117] In one embodiment, a management cycle can be set (set by the staff), and each target server is managed once every management cycle. For example, if the management cycle is one week, the managed server will be managed once every week.

[0118] In one embodiment, Figure 3 As shown, the method further includes:

[0119] Step 302: Obtain the operating status of each server to be managed, where the operating status includes a working state or a non-working state.

[0120] In an embodiment of the present application, the operating status of the server to be managed includes a working status or a non-working status. When the server to be managed is in a working status (that is, the server to be managed is running a certain business), if the server to be managed is managed, it will affect the normal operation of the business. Therefore, when the server to be managed is in a non-working status, the server is managed. Then, in this embodiment, the operating status of each server to be managed can be obtained, and whether to manage the server to be managed can be determined based on the operating status.

[0121] Step 304: The server to be managed that is in a non-working state is used as the target server.

[0122] In the embodiment of the present application, the servers to be managed that are in a non-working state can be used as target servers. After the target servers are determined, each target server can be managed.

[0123] For example, the staff can input the servers to be managed into the server: server 1 to server 10. After receiving the above servers to be managed, the managing server obtains the operating status of the above 10 servers. Taking the operating status of servers 1 to 4 as the working status and the operating status of servers 5 to 10 as the non-working status as an example, the target servers are determined to be server 5, server 6, server 7...server 10.

[0124] The embodiment of the present application obtains the operating status of the server to be managed and takes the server to be managed that can be managed (i.e., the operating status is non-working) as the target server for management, thereby avoiding the business impact of the target server due to management. Compared with manual server management, the target servers can be managed in batches, thereby improving the efficiency of server management.

[0125] In one embodiment, Figure 4 As shown, in step 104, before determining the target login password of each user according to the password generation rule corresponding to each user in the target server, the method further includes:

[0126] Step 402: For any user, obtain the corresponding user attributes of the user in the target server.

[0127] In an embodiment of the present application, the user attributes corresponding to the same user in different target servers are different. For any user, the user attributes corresponding to the user in the target server can be obtained. The user attributes can be used to represent the user's permission level in the target server. In the same target server, the higher the user attribute, the more complex the password used by the user to log in to the target server. In other words, in the same target server, users with different user attributes have different corresponding password generation rules. In this embodiment, the complexity of a password can be represented by the password length. The longer the password length, the more complex the password.

[0128] For example, taking the case where target server 1 contains users A, B, and C, and target server 2 contains user A, by obtaining the corresponding user attributes of the users in the target server, it can be found that in target server 1, user attribute A of user A is level one, user attribute B of user B is level two, and user attribute C of user C is level two; in target server 2, user attribute A of user A is level one.

[0129] Step 404 : Determine password generation rules for each user based on the user attributes corresponding to each user in the target server. Password generation rules corresponding to different user attributes have different complexities.

[0130] In an embodiment of the present application, the password generation rules corresponding to each user can be determined separately based on the user attributes corresponding to each user on the target server. The complexity of the password generation rules corresponding to different user attributes is also different. The user with higher user attributes has a more complex corresponding password generation rule. The complexity of the password generation rule can be determined by the password length and the types of characters contained in the password.

[0131] For example, taking password generation rule 1 as follows: password length is 10 characters, password includes 2 uppercase English letters and 8 digits, and password generation rule 2 as follows: password length is 10 characters, password includes 2 English letters (uppercase and lowercase) and 8 digits, the complexity of password generation rule 2 is greater than the complexity of password generation rule 1.

[0132] Alternatively, in step 406, the security level of the target server is obtained, and a password generation rule corresponding to each user is determined according to the security level of the target server and the user attributes of each user.

[0133] In an embodiment of the present application, the security level of the target server can be obtained, and the password generation rules corresponding to each user can be determined according to the security level of the target server and the user attributes of each user. Since different target servers may be used to run different businesses, the security levels of different target servers may also be different. If the target server is used to run important businesses, the target server requires a higher security level; if the target server is used to run daily businesses, the target server only requires a lower security level.

[0134] For example, still taking the above example, the user attributes of user A in target server 1 and target server 2 are both level one, the security level of target server 1 is level one, and the security level of target server 2 is level two. Then, based on the security level of target server 1 and the user attributes of user A, the password generation rule 1 corresponding to user A is determined. Based on the security level of target server 2 and the user attributes of user A, the password generation rule 2 corresponding to user A is determined. The security level of target server 1 is higher than the security level of target server 1, then the complexity of password generation rule 1 is higher than the complexity of password generation rule 2.

[0135] The embodiment of the present application directly determines the password generation rules corresponding to each user through the user attributes corresponding to the user in the target server, or through the security level of the target server and the user attributes of the user. Therefore, during the management process, an accurate target login password can be generated according to the password generation rules, avoiding management failure due to the target login password not meeting the requirements of the target server, thereby improving the efficiency of target server management.

[0136] In one embodiment, Figure 5 As shown, the method further includes:

[0137] Step 502: Obtain locked users in each target server, wherein the user's login status includes a first status or a second status, the first status is used to indicate that the user is allowed to log in to the target server, and the second status is used to indicate that the user is prohibited from logging in to the target server. The locked user is a user whose login status is the second status.

[0138] Among them, the second target password file stored in each target server can also include the login status of each user, and the login status includes a first status or a second status. The first status is used to indicate that the user is allowed to log in to the target server, and the second status is used to indicate that the user is prohibited from logging in to the target server. A locked user is a user whose login status is the second status. The user whose login status is the second status (i.e., a locked user) can be obtained from the second target password file of each target server.

[0139] In an embodiment of the present application, in order to ensure the information security of the target server, the target server will lock users with abnormal behavior to prohibit the user from logging into the target server. For example, after the user logs in to the target server through the management server, if some of the user's operation instructions are identified as high-risk instructions, the user is considered an abnormal behavior user; or, if the user repeatedly attempts to perform operations that exceed his or her user authority, the user can also be considered to have abnormal behavior.

[0140] When any user logs in to the target server, the managed server first responds to the user's authentication request and authenticates the user. When the user authentication is passed, the terminal side will jump to the login page. The user can enter the target server to log in on the login page. If the user's login status in the target server is the first status, the user can log in to the target server normally; if the user's login status in the target server is the second status (that is, the user is locked), the terminal side will prompt "User locked" or "User cannot log in".

[0141] Step 504: For any target server, in response to the unlock request, a new target login password is determined according to the password generation rule corresponding to the locked user in the target server.

[0142] In an embodiment of the present application, a staff member inputs an unlock request to the management server at a preset time interval (which can be set by the staff member). In response to the unlock request, the management server generates a new target login password for any target server according to the password generation rule corresponding to the locked user in the target server. For example, taking locked user 1, locked user 2, and locked user 3 as examples, where locked user 1 is a locked user in target server 1, and locked user 2 and locked user 3 are both locked users in target server 2, for target server 1, according to password generation rule 1 corresponding to locked user 1, a new target login password 1ˊ is determined; for target server 2, according to password generation rule 2 corresponding to locked user 2, a new target login password 2ˊ is determined; and according to password generation rule 3 corresponding to locked user 3, a new target login password 3ˊ is determined.

[0143] Step 506: Update the target login password of the locked user in the first target password file and the target login password of the locked user in the second target password file according to the new target login password, and update the login status of the locked user to the first status.

[0144] In an embodiment of the present application, the target login password of the locked user in the first target password file can be updated according to the new target login password, and an unlock request can be sent to the target server according to the new target login password. The target server will update the target login password of the locked user in the second target password file according to the new target login password, and the target server will also update the login status of the locked user in the second target password file to the first status.

[0145] For example, still taking the above example, the target login password 1 for locking user 1 in the first target password file 1 corresponding to server 1 is updated to target login password 1ˊ, and the target login password 1 for locking user 1 in the second target password file 1 stored in server 1 is updated to target login password 1ˊ.

[0146] In an embodiment of the present application, the locked users in each target server can be directly determined. After receiving the unlock request, the target login password of the locked user in the first target password file and the target login password of the locked user in the second target password file can be updated in response to the unlock request. After the update is completed, the locked user can log in to the target server, thereby realizing batch unlocking of locked users and improving unlocking efficiency.

[0147] In one embodiment, Figure 6 As shown, the target server includes multiple applications, and the method further includes:

[0148] Step 602: Acquire verification information input by the user to be logged in for the target application.

[0149] A target server can include multiple applications, and one application corresponds to multiple application users. In traditional technologies, application users rely on passwords to log in to applications. Application users directly know the login passwords, which poses a risk of password leakage.

[0150] In an embodiment of the present application, after the user to be logged in logs in to the server to be logged in through the managed server, the user to be logged in can perform certain operations on the server to be logged in through the managed server, for example, logging in to an application in the server to be logged in through the managed server. When the user to be logged in logs in to any application, the verification information for the target application will be input to the managed server, and the managed server will receive the verification information. The managed server can be externally connected to a fingerprint extraction device, and the verification information can be the fingerprint information of the application user. It should be noted that the above-mentioned verification information is fingerprint information, which is only an example in the embodiment of the present application, and the verification information is not limited in the embodiment of the present application.

[0151] Step 604: Send an application login request to the server to be logged in according to the verification information. The application login request is used to instruct the server to be logged in to perform application login verification according to the verification information to obtain an application login verification result.

[0152] In an embodiment of the present application, the managing server may send an application login request to the server to be logged in based on the verification information. The server to be logged in responds to the application login request and performs application login verification on the verification information to obtain a verification result. For example, the server to be logged in may compare the fingerprint information input by the user to be logged in with the stored fingerprint information of the user to be logged in. If the comparison finds that the input fingerprint information is consistent with the stored fingerprint information, the user to be logged in has passed the application login verification.

[0153] Step 606: If the application login verification result indicates that the verification is passed, obtain the key corresponding to the user to be logged in, and if the key corresponding to the user to be logged in is authenticated, obtain the application login password of the user to be logged in, and log in to the target application according to the application login password.

[0154] If the user to be logged in passes the verification, the key corresponding to the user to be logged in will be obtained and authenticated. When the key corresponding to the user to be logged in is authenticated, the application login password of the user to be logged in can be obtained, and the target application can be logged in according to the application login password.

[0155] The embodiment of the present application changes the way in which users directly enter the application login password to log in to the target application. By setting a key, the key can be obtained only when the user passes the verification. Further authentication is performed with the key, and the application login password can be obtained only after the authentication passes. Among them, the user does not directly know the application login password, which avoids the leakage of the application login password and improves the security of the application.

[0156] In a specific embodiment, the staff inputs the servers to be managed as server 1, server 2...server 5 into the management server, obtains the operating status of the above-mentioned servers to be managed, and finds that the operating status of server 1, server 2 and server 3 is non-working, and the operating status of server 4 and server 5 is working, then determines that the target servers that can be managed are server 1, server 2 and server 3.

[0157] Obtain the password files of the above three servers. For server 1, according to password file 1 of server 1, determine that server 1 includes user A and user B, obtain user attribute A of user A and user attribute B of user B respectively, and determine password generation rule A of user A based on user attribute A of user A, and determine password generation rule B of user B based on user attribute B of user B. Then, according to the above two password generation rules, determine the target login password A of user A and the target login password B of user B respectively.

[0158] According to the user information of user A: A and target login password A, and the user information of user B: B and target login password B, the first target password file of server 1 is constructed: A-target login password A, B-target login password B.

[0159] The management server sends a management request to Server 1, which includes the target login password A and the target login password B. Server 1 responds to the management request by updating User A's initial login password A in Password File 1 to User A's target login password A, and updating User B's initial login password B in Password File 1 to User B's target login password B. This completes the management of Server 1. Repeat these steps to manage Servers 2 and 3, respectively.

[0160] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0161] Based on the same inventive concept, embodiments of the present application also provide a server management device for implementing the aforementioned server management method. The solution provided by this device is similar to the solution described in the aforementioned method. Therefore, the specific limitations in one or more server management device embodiments provided below can be found in the aforementioned limitations of the server management method and will not be further elaborated here.

[0162] In one embodiment, Figure 7 As shown, a server management device 700 is provided, comprising: a first acquisition module 702, a first determination module 704, a construction module 706 and a first sending module 708, wherein:

[0163] The first acquisition module 702 is used to obtain user information of each user in the target server;

[0164] The first determination module 704 is used to determine the target login password of each user according to the password generation rules corresponding to each user in the target server;

[0165] A construction module 706 is used to construct a first target password file of the target server according to the user information of each user and the target login password of each user;

[0166] The first sending module 708 sends a management request to the target server, where the management request includes the target login password of each user. The management request is used to instruct the target server to update the initial login password of each user in the password file of the target server according to the target login password of each user, and obtain the second target password file of the target server.

[0167] In an embodiment of the present application, the initial login password known to the user is updated to a target login password unknown to the user, and the constructed first target password file contains the target login passwords of each user of the target server. At this time, the user can no longer log in to the target server by entering the initial login password to the target server. The user needs to send the user's target login password to the target server through the management server storing the first target password file to log in to the target server. That is, by updating the login password, the management of each target server is achieved. Through the above method, the standardization of the server management steps is achieved, the irregular management and management errors are avoided, and the management efficiency is improved.

[0168] In one embodiment, the apparatus further comprises:

[0169] An authentication module, configured to authenticate the user to be logged in in response to an authentication request sent by the terminal side, wherein the authentication request includes user login information of the user to be logged in;

[0170] The second determining module is used to determine the server to be logged in from each target server when the user to be logged in is authenticated;

[0171] The second acquisition module is used to obtain a first target password file corresponding to the server to be logged in;

[0172] The third acquisition module is used to obtain the target login password corresponding to the user to be logged in from the first target password file corresponding to the server to be logged in according to the user login information;

[0173] The second sending module is used to send a login request to the server to be logged in, wherein the login request includes a target login password corresponding to the user to be logged in, so that the server to be logged in performs a match in a second target password file corresponding to the server to be logged in according to the target login password corresponding to the user to be logged in, and obtains a corresponding matching result;

[0174] The third sending module is used to send login success feedback information for the server to be logged in to the terminal side when the matching result indicates a successful match, so that the terminal side jumps to the system interface of the server to be logged in in response to the login success feedback information.

[0175] In one embodiment, the apparatus further comprises:

[0176] A third acquisition module is used to obtain the operating status of each server to be managed, wherein the operating status includes a working state or a non-working state;

[0177] The third determining module is used to select the server to be managed that is in a non-working state as the target server.

[0178] In one embodiment, the apparatus further comprises:

[0179] The fourth acquisition module is used to obtain the user attributes corresponding to any user in the target server;

[0180] A fourth determining module is used to determine a password generation rule corresponding to each user according to the user attribute corresponding to each user in the target server, wherein the complexity of the password generation rule corresponding to different user attributes is different;

[0181] Alternatively, the fourth determining module is further configured to obtain the security level of the target server, and determine a password generation rule corresponding to each user according to the security level of the target server and the user attributes of each user.

[0182] In one embodiment, the apparatus further comprises:

[0183] A fifth acquisition module is configured to acquire locked users in each target server, wherein the user's login status includes a first status or a second status, the first status being used to indicate that the user is allowed to log in to the target server, and the second status being used to indicate that the user is prohibited from logging in to the target server, and the locked user is a user whose login status is the second status;

[0184] a fifth determining module, configured to determine, for any target server, in response to an unlock request, a new target login password according to a password generation rule corresponding to a locked user in the target server;

[0185] The updating module is used to update the target login password of the locked user in the first target password file and the target login password of the locked user in the second target password file according to the new target login password, and update the login status of the locked user to the first status.

[0186] In one embodiment, the target server includes multiple applications, and the apparatus further includes:

[0187] A sixth acquisition module, configured to acquire verification information input by the user to be logged in for the target application;

[0188] A fourth sending module is used to send an application login request to the server to be logged in according to the verification information, where the application login request is used to instruct the server to be logged in to perform application login verification according to the verification information and obtain an application login verification result;

[0189] The seventh acquisition module is used to obtain the key corresponding to the user to be logged in when the application login verification result indicates that the verification has been passed, and to obtain the application login password of the user to be logged in when the key corresponding to the user to be logged in is authenticated, so as to log in to the target application according to the application login password.

[0190] Each module in the server management device described above may be implemented in whole or in part through software, hardware, or a combination thereof. Each module may be embedded in or independent of a processor in a computer device in the form of hardware, or may be stored in a memory in the computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0191] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 8 As shown. The computer device includes a processor, a memory, and a network interface connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store password data. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a server management method is implemented.

[0192] Those skilled in the art will understand that Figure 8 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0193] In one embodiment, a computer device is further provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.

[0194] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0195] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0196] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0197] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processor involved in the various embodiments provided herein may be, but are not limited to, a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, and the like.

[0198] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0199] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A server management method, the method being applied to a server management method, characterized in that: The method comprises: Get the user information of each user in the target server; Determine the target login password of each user according to the password generation rule corresponding to each user in the target server; Constructing a first target password file of the target server according to the user information of each user and the target login password of each user; Sending a management request to the target server, the management request including the target login password of each user, the management request being used to instruct the target server to update the initial login password of each user in the password file of the target server according to the target login password of each user, to obtain a second target password file of the target server; The method further includes: authenticating the user to be logged in in response to an authentication request of the user to be logged in sent by the terminal side, wherein the authentication request includes user login information of the user to be logged in; In the case that the user to be logged in is authenticated, determining the server to be logged in from each of the target servers; Obtaining the first target password file corresponding to the server to be logged in; According to the user login information, obtaining a target login password corresponding to the user to be logged in from the first target password file corresponding to the server to be logged in, wherein the target login password is unknown to the user; Sending a login request to the server to be logged in, the login request including the target login password corresponding to the user to be logged in, so that the server to be logged in performs a match in the second target password file corresponding to the server to be logged in, according to the target login password corresponding to the user to be logged in, to obtain a corresponding matching result; When the matching result indicates a successful match, a login success feedback message for the server to be logged in is sent to the terminal side, so that the terminal side jumps to the system interface of the server to be logged in in response to the login success feedback message.

2. The method according to claim 1, characterized in that The method further comprises: Obtaining the operating status of each server to be managed, wherein the operating status includes a working state or a non-working state; The server to be managed, whose operating state is the non-working state, is used as the target server.

3. The method according to claim 1, characterized in that Before determining the target login password of each user according to the password generation rule corresponding to each user in the target server, the method further includes: For any of the users, obtaining the user attributes corresponding to the user in the target server; Determining password generation rules corresponding to each user according to the user attributes corresponding to each user in the target server, wherein the password generation rules corresponding to different user attributes have different complexities; Alternatively, the security level of the target server is obtained, and the password generation rule corresponding to each user is determined according to the security level of the target server and the user attributes of each user.

4. The method according to claim 1, wherein The method further comprises: Obtaining a locked user in each target server, wherein the user's login status includes a first status or a second status, the first status being used to indicate that the user is allowed to log in to the target server, and the second status being used to indicate that the user is prohibited from logging in to the target server, and the locked user is a user whose login status is the second status; For any of the target servers, in response to an unlock request, determining a new target login password according to the password generation rule corresponding to the locked user in the target server; According to the new target login password, the target login password of the locked user in the first target password file and the target login password of the locked user in the second target password file are updated, and the login status of the locked user is updated to the first status.

5. The method according to claim 1, wherein The target server includes a plurality of applications, and the method further includes: Obtaining verification information input by the user to be logged in for the target application; Sending an application login request to the server to be logged in according to the verification information, wherein the application login request is used to instruct the server to be logged in to perform application login verification according to the verification information and obtain an application login verification result; If the application login verification result indicates that the verification has been passed, the key corresponding to the user to be logged in is obtained, and if the key corresponding to the user to be logged in is authenticated, the application login password of the user to be logged in is obtained to log in to the target application according to the application login password.

6. A server management device, characterized in that: The device comprises: The first acquisition module is used to obtain user information of each user in the target server; A first determining module, configured to determine a target login password for each user according to a password generation rule corresponding to each user in the target server; A construction module, configured to construct a first target password file of the target server according to the user information of each user and the target login password of each user; a first sending module, sending a management request to the target server, the management request including the target login password of each user, the management request being used to instruct the target server to update the initial login password of each user in the password file of the target server according to the target login password of each user, to obtain a second target password file of the target server; The device further includes: an authentication module, configured to authenticate the user to be logged in in response to an authentication request of the user to be logged in sent by the terminal side, wherein the authentication request includes user login information of the user to be logged in; A second determining module is configured to determine a server to be logged in from each of the target servers if the user to be logged in is authenticated; A second acquisition module is used to obtain the first target password file corresponding to the server to be logged in; A third acquisition module is configured to acquire, based on the user login information, a target login password corresponding to the user to be logged in from the first target password file corresponding to the server to be logged in, wherein the target login password is unknown to the user; a second sending module, configured to send a login request to the server to be logged in, wherein the login request includes the target login password corresponding to the user to be logged in, so that the server to be logged in performs a match in the second target password file corresponding to the server to be logged in, according to the target login password corresponding to the user to be logged in, to obtain a corresponding matching result; The third sending module is used to send login success feedback information for the server to be logged in to the terminal side when the matching result indicates a successful match, so that the terminal side jumps to the system interface of the server to be logged in in response to the login success feedback information.

7. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 5 are implemented.

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

9. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 are implemented.

Images