CN118885994A - SMB user management method, device, electronic device and readable storage medium - Google Patents

Abstract

The application discloses a SMB user management method, a device, an electronic device and a readable storage medium, which are applied to any service node in a shared service cluster and comprise the following steps: creating a target SMB user and determining a working mode; if the single-node mode is adopted, determining a new serial number according to serial numbers of all the same-name SMB users of the target SMB users in other service nodes, setting the user serial number as the new serial number in a user information table corresponding to the target SMB users, and setting a user tag as an independent user; if the user information table is in the cluster mode, setting the user serial number as a default serial number in the user information table corresponding to the target SMB user, setting the user label as the cluster user, and updating the user serial number in the cluster mode along with the updating of the corresponding user information table; and managing each SMB user according to each user information table. The scheme realizes the simultaneous support of the shared service cluster to the single node mode and the cluster mode, and further realizes the unified management of the SMB users.

Description

SMB user management method, device, electronic device and readable storage medium

Technical Field

The present application relates to the technical field of cluster systems, and in particular to an SMB user management method, and also to an SMB user management device, an electronic device, a computer-readable storage medium, and a computer program product.

Background Art

Samba is a service suite that implements the SMB protocol (Server Message Block, a shared transmission protocol between different network nodes) on Linux and UNIX systems. Its main purpose is to provide SMB sharing services to Windows clients on Linux or UNIX servers, thereby facilitating centralized management of employee user data within the enterprise.

The premise of using Samba service is to provide authentication users first. There are two types of authentication users directly created based on Samba service: single-node users and cluster users. These two types of users cannot communicate with each other under normal circumstances, that is, authentication users created when Samba service works in single-node mode can only be used in single-node mode, and authentication users created in cluster mode can only be used in cluster mode. The significant problem is that when the customer sets Samba service to switch between single-node mode and cluster mode, users created in one mode will automatically become invalid when in the other mode. It can be seen that the existing technical architecture of Samba service is independent of each other for user management in cluster mode and single-node mode, that is, SMB users created in single-node mode cannot be seen in cluster mode, and conversely, SMB users created in cluster mode cannot be seen when switched to single-node mode, which means that the uniformity of user management in single-node mode and cluster mode is isolated.

Therefore, how to realize the shared service cluster to support both the single node mode and the cluster mode, and then realize the shared service cluster to manage SMB users in a unified manner under the two different working modes is a problem to be solved urgently by those skilled in the art.

Summary of the invention

The purpose of the present application is to provide an SMB user management method, which can realize the simultaneous support of a shared service cluster for a single-node mode and a cluster mode, thereby realizing the unified management of SMB users by the shared service cluster under two different working modes; another purpose of the present application is to provide an SMB user management device, an electronic device, a computer-readable storage medium, and a computer program product, all of which have the above-mentioned beneficial effects.

In a first aspect, the present application provides an SMB user management method, which is applied to any service node in a shared service cluster, where all service nodes in the shared service cluster are connected to a unified database, and the unified database is used to store user information tables of all SMB users in the shared service cluster, and the method includes:

When receiving an SMB user creation command, creating a target SMB user according to the SMB user creation command, and determining a working mode of the shared service cluster; the working mode includes a single node mode and a cluster mode;

If the working mode is the single-node mode, determine the SMB users with the same name as the target SMB user in each of the other service nodes, determine a new serial number according to the serial numbers of each of the SMB users with the same name, set the user serial number as the new serial number in the user information table corresponding to the target SMB user, and set the user label as an independent user;

If the working mode is the cluster mode, the user serial number is set as the default serial number in the user information table corresponding to the target SMB user, and the user tag is set as a cluster user; wherein the user serial number in the cluster mode is updated as the corresponding user information table is updated;

Each of the SMB users is managed according to each user information table in the unified database.

Optionally, when the SMB user management operation is specifically a modification operation, managing each SMB user according to each user information table in the unified database includes:

Determine the user data of the SMB user to be modified;

If the working mode is the single-node mode, determine whether there is an SMB user with the same name as the SMB user to be modified locally in the service node; if so, overwrite the original user data of the SMB user with the same name with the user data, and set the user label as an independent user in the user information table corresponding to the SMB user with the same name; if not, execute the step of creating a target SMB user according to the SMB user creation command;

If the working mode is the cluster mode, determine whether there is an SMB user with the same name as the SMB user to be modified in the shared service cluster; if so, use the user data to overwrite the original user data of the SMB user with the same name, and set the user label as a cluster user in the user information table corresponding to the SMB user with the same name, and synchronize other service nodes to perform the modification operation; if not, execute the step of creating the target SMB user according to the SMB user creation command.

Optionally, when the SMB user management operation is specifically a retrieval operation, managing each SMB user according to each user information table in the unified database includes:

Determine the user information of the target SMB user to be queried;

If the working mode is the single node mode, the user information is used to determine whether the target query SMB user exists locally in the service node; if so, the user data of the target query SMB user is output; if not, an error prompt is output;

If the working mode is the cluster mode, the user information is used to determine whether there is a target query SMB user with a user label of a cluster user locally in the service node; if so, the user data of the target query SMB user with a user label of a cluster user is output; if not, all target query SMB users with a user label of an independent user are determined in the shared service cluster, and the target query SMB user with a user serial number of the latest serial number is determined among all target query SMB users with a user label of an independent user, and the user data of the target query SMB user with a user serial number of the latest serial number is output.

Optionally, when the SMB user management operation is specifically a deletion operation, managing each SMB user according to each user information table in the unified database includes:

Confirm the SMB user to be deleted;

If the working mode is the single node mode, deleting the SMB user with the same name as the SMB user to be deleted in the local service node;

If the working mode is the cluster mode, the SMB users with the same name as the SMB user to be deleted in the shared service cluster are deleted.

Optionally, when receiving the SMB user creation command, after creating the target SMB user according to the SMB user creation command, the method further includes:

Determine whether there is a default user group in the shared service cluster;

If so, executing the step of determining the working mode of the shared service cluster;

If not, the target SMB user is set to belong to the default user group, and the user information of the target SMB user is added to the member list of the default user group, and the process returns to the step of creating the target SMB user according to the SMB user creation command when an SMB user creation command is received.

Optionally, when the service node is a newly added service node, the method further includes:

Determining a working mode of the shared service cluster;

If the working mode is the single node mode, executing the preset operation;

If the working mode is the cluster mode, the user information of each of the SMB users whose user tag is a cluster user is obtained from the main service node of the shared service cluster and saved locally.

Optionally, the SMB user management method further includes:

Receive an SMB connection request from a client for the target SMB user;

Determine whether the target SMB user exists according to the SMB connection request;

If it does not exist, an error message is fed back to the client;

If so, a response message is fed back to the client to receive the password data of the target SMB user sent by the client, verify the password data using the registered password data of the target SMB user, and establish an SMB connection with the client when the verification passes.

In a second aspect, the present application further provides an SMB user management device, which is applied to any service node in a shared service cluster, wherein all service nodes in the shared service cluster are connected to a unified database, and the unified database is used to store user information tables of all SMB users in the shared service cluster, and the device includes:

A determination module, configured to, when receiving an SMB user creation command, create a target SMB user according to the SMB user creation command, and determine a working mode of the shared service cluster; the working mode includes a single node mode and a cluster mode;

A first setting module is used for, if the working mode is the single-node mode, determining SMB users with the same name as the target SMB user in each of the other service nodes, determining a new serial number according to the serial numbers of each of the SMB users with the same name, setting the user serial number as the new serial number in the user information table corresponding to the target SMB user, and setting the user label as an independent user;

A second setting module is used for setting the user serial number as a default serial number and the user tag as a cluster user in the user information table corresponding to the target SMB user if the working mode is the cluster mode; wherein the user serial number in the cluster mode is updated as the corresponding user information table is updated;

The management module is used to manage each of the SMB users according to each user information table in the unified database.

In a third aspect, the present application further discloses an electronic device, comprising:

Memory for storing computer programs;

A processor is used to implement the steps of any one of the SMB user management methods described above when executing the computer program.

In a fourth aspect, the present application further discloses a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of any one of the SMB user management methods described above are implemented.

In a fifth aspect, the present invention further discloses a computer program product, including a computer program/instruction, which implements the steps of any one of the SMB user management methods described above when executed by a processor.

The present application provides an SMB user management method, which is applied to any service node in a shared service cluster, wherein all service nodes in the shared service cluster are connected to a unified database, and the unified database is used to store user information tables of all SMB users in the shared service cluster. The method comprises: when an SMB user creation command is received, a target SMB user is created according to the SMB user creation command, and a working mode of the shared service cluster is determined; the working mode comprises a single node mode and a cluster mode; if the working mode is the single node mode, the SMB users with the same name as the target SMB user in other service nodes are determined, a new serial number is determined according to the serial numbers of the SMB users with the same name, the user serial number is set to the new serial number in the user information table corresponding to the target SMB user, and the user label is set to an independent user; if the working mode is the cluster mode, the user serial number is set to the default serial number in the user information table corresponding to the target SMB user, and the user label is set to a cluster user; wherein the user serial number in the cluster mode is updated as the corresponding user information table is updated; and each SMB user is managed according to each user information table in the unified database.

Applying the technical solution provided by the present application, a unified database is created in a shared service cluster, so that all service nodes in the shared service cluster are connected to the unified database, which is used to store the user information table of all SMB users created under each service node, and the user information table records the user label and user serial number of the corresponding SMB user, the user label indicates the user type of the corresponding SMB user, that is, the independent user in the single node mode and the cluster user in the cluster mode, and the user serial number indicates the serial number of the most recent update of the corresponding SMB user, which can ensure that the most recently updated SMB user with the same name can be retrieved when the user searches. On this basis, after a target SMB user is created, the corresponding user information table in the unified database can be set according to the working mode of the shared service cluster, that is, the user label and user serial number of the SMB user are set, so that the SMB user management in the shared service cluster can be realized according to the user information recorded in each user information table in the unified database. Therefore, the technical solution realizes the simultaneous support of the shared service cluster for the single node mode and the cluster mode, and then realizes the unified management of SMB users by the shared service cluster under two different working modes.

In one embodiment of the present application, the client can access the shared service cluster by connecting to the SMB user. When the client initiates an SMB connection request for a target SMB user, the service node will first determine whether the target SMB user exists, and perform a password check on the target SMB user when it is determined that the target SMB user exists, thereby achieving an SMB connection between the client and the target SMB user when the check passes, so that the client can access the shared service cluster by connecting to the SMB user, effectively ensuring the security of the shared service cluster. Among them, when it is determined that the target SMB user does not exist, an error prompt will be directly initiated, and the SMB connection request will no longer be processed, ensuring the access efficiency of the shared service cluster.

The SMB user management device, electronic device, computer-readable storage medium, and computer program product provided in this application also have the above-mentioned technical effects, and this application will not repeat them here.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the prior art and the embodiments of the present application, the drawings required for use in the description of the prior art and the embodiments of the present application are briefly introduced below. Of course, the drawings described below in relation to the embodiments of the present application are only part of the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without creative work, and the obtained other drawings also belong to the protection scope of the present application.

FIG1 is a schematic diagram of the structure of a shared service cluster provided by the present application;

FIG2 is a flow chart of an SMB user management method provided by the present application;

FIG3 is a layout diagram of a unified database provided by the present application;

FIG4 is a schematic structural diagram of an SMB user management device provided by the present application;

FIG5 is a schematic diagram of the structure of an electronic device provided in the present application.

DETAILED DESCRIPTION

The core of the present application is to provide an SMB user management method, which can realize the simultaneous support of the shared service cluster for single-node mode and cluster mode, thereby realizing the unified management of SMB users by the shared service cluster under two different working modes; another core of the present application is to provide an SMB user management device, an electronic device, a computer-readable storage medium and a computer program product, all of which have the above-mentioned beneficial effects.

In order to describe the technical solutions in the embodiments of the present application more clearly and completely, the technical solutions in the embodiments of the present application will be introduced below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

An embodiment of the present application provides an SMB user management method.

First, please refer to Figure 1, which is a structural diagram of a shared service cluster provided by the present application. Multiple service nodes are deployed in the shared service cluster, and all service nodes are connected to a unified database. Each service node can create an SMB user to provide shared services for each SMB user. The unified database is used to store the user information table of all SMB users in the shared service cluster, and the SMB user corresponds to the user information table one by one, that is, one SMB user corresponds to one user information table, and the user information table records the user label and user serial number of each SMB user, wherein the user label indicates the user type of the corresponding SMB user, such as an independent user in a single-node mode and a cluster user in a cluster mode, and the user serial number indicates the serial number of the corresponding SMB user that was last updated, which is used to ensure that the SMB user with the same name that was last updated is retrieved when the user searches. The SMB user management method provided in the embodiment of the present application is implemented based on the shared service cluster shown in Figure 1.

Further, please refer to FIG. 2 , which is a flow chart of an SMB user management method provided by the present application. The SMB user management method is applied to any service node in the shared service cluster shown in FIG. 1 , and its implementation process may include the following S101 to S104:

S101: When an SMB user creation command is received, a target SMB user is created according to the SMB user creation command, and a working mode of a shared service cluster is determined; the working modes include a single node mode and a cluster mode.

This step is intended to achieve the creation of the target SMB user and the determination of the working mode of the shared service cluster. Among them, the target SMB user is the SMB user that needs to be created, which is implemented in response to the SMB user creation command; the working mode of the shared service cluster includes single-node mode and cluster mode. In the traditional technical implementation, the SMB users created by each service node in the single-node mode are all stored in the private database of the corresponding service node, and data cannot be shared between the service nodes; the SMB users created by each service node in the cluster mode are stored in the cluster database, and data sharing can be achieved between the service nodes through the cluster database. Based on this, the traditional Samba service architecture is independent of each other in user management for cluster mode and single-node mode. In this regard, a unified database is created in the embodiment of the present application, whether it is single-node mode or cluster mode, it is used to realize the relevant data storage of the newly created SMB user, so as to realize the simultaneous support of the Samba service architecture for cluster mode and single-node mode.

S102: If the working mode is the single-node mode, determine the SMB users with the same name as the target SMB user in other service nodes, determine a new serial number according to the serial numbers of the SMB users with the same name, set the user serial number as the new serial number in the user information table corresponding to the target SMB user, and set the user label to an independent user.

This step is intended to implement the setting of the corresponding user information table in the unified database for the newly created target SMB user in single-node mode, including the setting of the user label and user serial number for the target SMB user. Specifically, since it is a single-node mode, the user label in the user information table can be directly set to an independent user, and for the user serial number, it is possible to first query whether there is an SMB user with the same name as the target SMB user on other service nodes in the shared service cluster. If so, a new serial number can be determined based on the serial numbers of each SMB user with the same name, and the user serial number of the target SMB user can be set to the new serial number. For example, if the serial numbers of the SMB users with the same name as the target SMB user already exist in the shared service cluster, which are 0001, 0002, and 0003, then the user serial number of the target SMB user can be determined to be 0004. Among them, when there is no SMB user with the same name as the target SMB user in the shared service cluster, its user serial number can be directly set to the default initial serial number, such as 0001.

S103: If the working mode is cluster mode, set the user serial number to the default serial number in the user information table corresponding to the target SMB user, and set the user tag to a cluster user; wherein the user serial number in the cluster mode is updated as the corresponding user information table is updated.

This step is intended to achieve the setting of the corresponding user information table in the unified database for the newly created target SMB user in the cluster mode, including the setting of the user label and user serial number for the target SMB user. Specifically, since it is a cluster mode, the user label in the user information table can be directly set to the cluster user, and for the user serial number, since all service nodes in the cluster mode share the target SMB user, a default serial number can be directly set, and the user serial number in the cluster mode is updated as the user information table is updated. For example, for the newly created target SMB user, its user serial number can be directly set to the default serial number 0001, then, if there is any service node to modify the information of the target SMB user later, the user serial number in its corresponding user information table will be increased one by one on the basis of the default serial number, that is, the user serial number of the target SMB user after the first information modification is 0002, and the user serial number after the second information modification is 0003, and so on.

S104: Manage each SMB user according to each user information table in the unified database.

This step is intended to achieve the management of each SMB user in the shared service cluster. Based on the above S101~S103, the user information tables of all newly created SMB users in the shared service cluster are stored in a unified database. The user label in the user information table is used to indicate the user type of the corresponding SMB user, and the user serial number is used to indicate the serial number of the corresponding SMB user's most recent update, so as to ensure that the most recently updated SMB user with the same name can be retrieved during user search. Therefore, unified management of all SMB users in the shared service cluster can be achieved based on each user information table in the unified database. Among them, the management operations on each SMB user may include but are not limited to modification operations, query operations, deletion operations, etc.

In one embodiment of the present application, when the SMB user management operation is specifically a modification operation, the management of each SMB user according to each user information table in the unified database may include:

Determine the user data of the SMB user to be modified;

If the working mode is single-node mode, determine whether there is an SMB user with the same name as the SMB user to be modified locally in the service node; if so, overwrite the original user data of the SMB user with the same name with the user data, and set the user label as an independent user in the user information table corresponding to the SMB user with the same name; if not, execute the step of creating the target SMB user according to the SMB user creation command;

If the working mode is cluster mode, determine whether there is an SMB user with the same name as the SMB user to be modified in the shared service cluster; if so, use the user data to overwrite the original user data of the SMB user with the same name, set the user label as a cluster user in the user information table corresponding to the SMB user with the same name, and synchronize other service nodes to perform the modification operation; if not, execute the steps of creating the target SMB user according to the SMB user creation command.

The SMB user management method provided in the embodiment of the present application can be used to implement the modification operation of each SMB user in the shared service cluster, that is, to modify the user data of one or more SMB users. Specifically, after determining the user data of the SMB user to be modified (the user data refers to the modified user data, that is, the new user data), the SMB user can be modified according to the working mode of the shared service cluster, wherein the SMB user to be modified can be specified by the user name.

In single-node mode, if there is an SMB user with the same name as the SMB user to be modified locally in the current service node, the user data of each SMB user with the same name can be modified. Here, the new user data can be directly used to overwrite the original user data, and the user label of the corresponding user information table is modified to be an independent user. In addition, if there is no SMB user with the same name as the SMB user to be modified locally in the current service node, a new SMB user with the same name can be directly created based on S102.

In cluster mode, if there is an SMB user with the same name as the SMB user to be modified in the shared service cluster, the user data of each SMB user with the same name can be modified. Here, the new user data can be directly used to overwrite the original user data, and the user label in the corresponding user information table can be modified and set to the cluster user. At the same time, since it is a cluster mode, the same operation can be performed in synchronization with other service nodes to realize SMB user modification. Similarly, if there is no SMB user with the same name as the SMB user to be modified in the shared service cluster, a new SMB user with the same name can be created directly based on S103. In addition, since the modification operation of the SMB user has occurred in the cluster mode, in addition to modifying the user label, the user serial number in the corresponding user information table can also be increased by 1 to realize the update of the user serial number, indicating that the corresponding SMB user has been updated.

In one embodiment of the present application, when the SMB user management operation is specifically a retrieval operation, the management of each SMB user according to each user information table in the unified database may include:

Determine the user information of the target SMB user to be queried;

If the working mode is single node mode, the user information is used to determine whether the target query SMB user exists locally in the service node; if so, the user data of the target query SMB user is output; if not, an error prompt is output;

If the working mode is cluster mode, the user information is used to determine whether there is a target query SMB user with a user label of cluster user locally in the service node; if so, the user data of the target query SMB user with a user label of cluster user is output; if not, all target query SMB users with a user label of independent users are determined in the shared service cluster, and the target query SMB user with the latest user serial number is determined among all target query SMB users with user labels of independent users, and the user data of the target query SMB user with the latest user serial number is output.

The SMB user management method provided in the embodiment of the present application can be used to implement the query operation of each SMB user in the shared service cluster, that is, to query the user data of one or more SMB users. Specifically, after determining the user information (such as user name) of the target queried SMB user, the query operation can be performed on the SMB user according to the working mode of the shared service cluster.

In single-node mode, you can directly query whether the target SMB user exists locally in the current service node based on user information, such as querying whether there is an SMB user with the user name XXX in the current service node. If it exists, its user data is directly returned; if it does not exist, an error prompt is directly output.

In cluster mode, you can first query whether there is a target query SMB user with a user tag of cluster user in the current service node based on user information, such as querying whether there is an SMB user with the user name XXX and the user tag of cluster user in the current service node. If it exists, its user data is returned directly; if it does not exist, you can continue to query the SMB user with the user tag of independent user and the user serial number of the latest serial number in the shared service cluster as the target query SMB user, and return its user data.

In one embodiment of the present application, when the SMB user management operation is specifically a deletion operation, the management of each SMB user according to each user information table in the unified database may include:

Confirm the SMB user to be deleted;

If the working mode is single node mode, the SMB user with the same name as the SMB user to be deleted in the local service node will be deleted;

If the working mode is cluster mode, delete the SMB user with the same name as the SMB user to be deleted in the shared service cluster.

The SMB user management method provided in the embodiment of the present application can be used to implement the deletion operation of each SMB user in the shared service cluster, that is, to delete one or more SMB users. Specifically, after determining the user information (such as user name) of the SMB user to be deleted, the deletion operation can be performed on it according to the working mode of the shared service cluster. Among them, in the single-node mode, the SMB user with the user name XXX created locally in the current service node can be directly deleted; in the cluster mode, the SMB user with the user name XXX created in the shared service cluster can be directly deleted.

It can be seen that the SMB user management method provided in the embodiment of the present application creates a unified database in the shared service cluster, so that all service nodes in the shared service cluster are connected to the unified database, which is used to store the user information table of all SMB users created under each service node, and the user information table records the user label and user serial number of the corresponding SMB user, the user label indicates the user type of the corresponding SMB user, that is, the independent user in the single node mode and the cluster user in the cluster mode, and the user serial number indicates the serial number of the corresponding SMB user that was last updated, which can ensure that the SMB user with the same name that was last updated can be retrieved when the user searches. On this basis, after a target SMB user is created, the corresponding user information table in the unified database can be set according to the working mode of the shared service cluster, that is, the user label and user serial number of the SMB user are set, so that the SMB user management in the shared service cluster can be realized according to the user information recorded in each user information table in the unified database. Therefore, the technical solution realizes the simultaneous support of the shared service cluster for the single node mode and the cluster mode, and then realizes the unified management of SMB users by the shared service cluster under two different working modes.

Based on the above embodiments:

In one embodiment of the present application, when an SMB user creation command is received, after creating a target SMB user according to the SMB user creation command, the following may also be included:

Determine whether there is a default user group in the shared service cluster;

If so, executing the step of determining the working mode of the shared service cluster;

If it does not exist, the target SMB user is set to belong to the default user group, and the user information of the target SMB user is added to the member list of the default user group, and the process returns to the step of creating the target SMB user according to the SMB user creation command when the SMB user creation command is received.

It is understandable that in Windows or Linux systems, when creating a user, a default user group is generally set, and the default user group is mainly used for permission management. Based on this, when creating an SMB user, after creating an SMB user, you can first determine whether there is a default user group in the shared service cluster. If it does, you can continue to make corresponding settings for its corresponding user information table to achieve complete creation of the SMB user. If it does not exist, you can directly make the target SMB user a member of the default user group and re-create the SMB user. Among them, the number of SMB users in the default user group can be set in advance according to actual needs.

In one embodiment of the present application, when the service node is a newly added service node, the SMB user management method may further include:

Determine the working mode of the shared service cluster;

If the working mode is single node mode, the preset operation is executed;

If the working mode is cluster mode, the user information of each SMB user whose user tag is cluster user is obtained from the main service node of the shared service cluster and saved locally.

It is understandable that a shared service cluster consists of multiple service nodes. In actual application scenarios, new nodes are bound to be added and old nodes are removed. For newly added service nodes, preset operations can be performed in single-node mode, such as no processing. In cluster mode, user information of all SMB users with user tags as cluster users in the shared service cluster needs to be obtained and saved locally to achieve information synchronization of cluster SMB users.

In one embodiment of the present application, the SMB user management method may further include:

Receive an SMB connection request from a client for a target SMB user;

Determine whether the target SMB user exists based on the SMB connection request;

If it does not exist, an error message will be fed back to the client;

If it exists, a response message is fed back to the client to receive the password data of the target SMB user sent by the client, the password data is verified using the registered password data of the target SMB user, and an SMB connection is established with the client when the verification passes.

In actual application scenarios, the client can access the shared service cluster by connecting to the SMB user. Specifically, the client can initiate an SMB connection request for a certain SMB user (i.e., the target SMB user mentioned above) to the service node (server), so that the service node can determine whether the target SMB user currently exists based on the SMB connection request. If not, an error prompt can be directly fed back to the client; if it exists, a response message can be fed back to the client, so that the client can send the target SMB user's password data to the service node based on the response message, and thus the service node can verify it using the registered password data of the target SMB user stored locally (the registered password data is the target SMB user registered to the service node when it is created). Obviously, if the verification is successful, the SMB connection request can be responded to to realize the connection between the target SMB user and the client, so that the client can access the shared service cluster through the target SMB user; if the verification fails, the SMB connection request will not be responded to, and the SMB connection will be refused to be established.

It can be seen that in the embodiment of the present application, the client can access the shared service cluster by connecting to the SMB user. When the client initiates an SMB connection request for a target SMB user, the service node will first determine whether the target SMB user exists, and perform a password verification on the target SMB user when it is determined that the target SMB user exists, thereby realizing the SMB connection between the client and the target SMB user when the verification passes, so that the client can access the shared service cluster by connecting to the SMB user, effectively ensuring the security of the shared service cluster. Among them, when it is determined that the target SMB user does not exist, an error prompt will be directly initiated, and the SMB connection request will no longer be processed, ensuring the access efficiency of the shared service cluster.

In one embodiment of the present application, the above-mentioned feedback of response information to the client to receive the password data of the target SMB user sent by the client, verifying the password data using the registered password data of the target SMB user, and establishing an SMB connection with the client when the verification passes, includes:

Feedback response information to the client, so that the client performs a hash operation on the user password of the target SMB user according to the response information to obtain the password data;

Receive the target SMB user's password data fed back by the client;

Perform hash operation on the registration password of the target SMB user stored locally to obtain the registration password data;

Determine whether the registered password data and the password data are consistent; if they are consistent, the verification is passed, and the target SMB user is controlled to establish an SMB connection with the client; if they are inconsistent, the verification fails.

The embodiment of the present application provides a verification method for SMB user password information, namely a verification method based on a hash algorithm. Specifically, the client can first perform a hash calculation on the user password of the target SMB user and then send it to the service node, and the service node can perform a hash calculation on the registration password of the target SMB user and then verify the password data sent by the client.

It can be seen that the embodiment of the present application implements password verification based on ciphertext by performing hash operation on password information, effectively ensuring the security of user passwords from being leaked, and further ensuring the security of the shared service cluster.

Based on the above embodiments, the present application embodiment provides another SMB user management method, and the implementation process of the SMB user management method is as follows:

First, as shown in FIG1 , the shared service cluster, the SMB user management method provided in the embodiment of the present application is implemented based on the shared service cluster. Secondly, please refer to FIG3 , which is a layout diagram of a unified database provided by the present application. Based on the user information tables in the unified database, the purpose of SMB user modification and use in single-node mode without affecting each other, SMB user modification and use in cluster mode taking effect on all service nodes, and users can correctly retrieve modifications when switching back and forth between single-node mode and cluster mode can be achieved. The meanings of the fields in the user information table are as follows:

(1) User flag: STANDLONE indicates a single-node user, and CLUSTER indicates a cluster user;

(2) User node ID: used to determine which service node the user operation is performed on. Since the database is distributed, the data added by each service node is directly visible in another service node. Here, node ID is used to distinguish between service nodes.

(3) User serial number sn: It is used to identify the most recently updated serial number of an SMB user. This serial number can ensure that the most recently updated SMB user with the same name can be used when searching for SMB users.

(4) User data: the specific content data of the corresponding SMB user.

Furthermore, the SMB user management method provided in the embodiment of the present application is introduced in detail below according to the processes of SMB user creation, modification, retrieval, deletion, and application.

1. SMB user creation:

(1) Execute the SMB user creation command, enter the user password, and create a basic SMB user that does not include any additional information;

(2) After receiving the creation command, the user management module parses the username and password text, then performs MD4 HASH calculation on the plain text password and saves it for subsequent client access authentication;

(3) Determine whether there is a default Users group in the shared service cluster. The Users group is one of the default groups built into the Windows system. Therefore, the implementation of the SMB protocol needs to support this default group. If it does not exist, the user management module first automatically creates the Users group and then assigns the newly added SMB user to the Users group. This involves two actions:

a. Set all groups of SMB users to Users;

b. Add the SMB user to the member list of the Users group;

After adding, users can also create new user groups and modify the user group information of existing SMB users;

(4) Determine the currently set Samba working mode:

If it is a single-node mode, add a new user and set the mark as STANDLONE, collect the user serial numbers of the SMB users with the same name of the remaining service nodes, and determine the latest sn serial number as the user serial number of the current new user;

If it is cluster mode, add a new user and set the tag to CLUSTER, then the sn sequence number starts from 1. The next time another service node updates the SMB user's information, the sequence number is automatically incremented.

2. SMB user modification:

(1) In single-node mode, if there is a user with the same name, regardless of whether it has the STANDLONE or CLUSTER mark, the new user data will be used to uniformly overwrite the original user data of the user with the same name and the mark will be changed to STANDLONE. Otherwise, the new user will be added directly according to step 1;

(2) In cluster mode, if there is a user with the same name, regardless of whether it is marked with STANDLONE or CLUSTER, the new user data will be used to uniformly overwrite the original user data of the user with the same name, and the mark will be changed to CLUSTER. Otherwise, the new user will be added directly according to step 1. At the same time, this operation will be performed on all service nodes to ensure that each service node has a copy of the latest user record.

3. SMB user retrieval:

(1) In single-node mode, first check whether the target search user exists in this service node. If it exists, regardless of whether it has the STANDLONE or CLUSTER mark, directly return its user data; if it does not exist, directly report an error;

(2) In cluster mode, first check whether there is an SMB user with the CLUSTER mark in this service node. If so, return its user data directly; if not, collect SMB users with the STANDLONE mark in all service nodes, and determine the SMB user with the latest sn sequence number as the final SMB user and return its user data, thereby realizing the SMB user merging from single-node mode to cluster mode.

4. SMB user deletion:

(1) In single-node mode, only the SMB users with the same name of this service node will be deleted, regardless of whether they are marked with STANDLONE or CLUSTER;

(2) In cluster mode, traverse all service nodes and delete all SMB users with the same name, regardless of whether they are marked with STANDLONE or CLUSTER.

5. New service nodes added:

(1) In single-node mode, when a new service node is added, no processing is done on the user records in the unified database;

(2) In cluster mode, when a new service node is added, the Samba service of the new service node automatically pulls the latest CLUSTER user information from the cluster master node and saves it locally.

6. SMB user use:

After adding an SMB user to the database, you can use the Windows client or other Linux clients that support the SMB protocol to access the shared service using the SMB user. The implementation process is as follows:

(1) The client uses the SMB user to initiate an SMB connection request. The server first checks whether the SMB user exists. If not, it directly returns a user-existing error to the client.

(2) If it exists, the server returns a Challenge response, and the client uses the Challenge response to further encrypt the user password HASH and send it to the server;

(3) The server uses the same algorithm to perform the same calculation on the locally stored password HASH. If it is consistent with the ciphertext field sent by the user, the verification passes. Otherwise, the verification fails.

(4) When verification passes, an SMB connection is established to enable access to the shared service cluster.

As can be seen from this, the present embodiment, by designing a user information table of a specific format, ensures the correct conversion of SMB users in the two modes of single node mode and cluster mode of Samba service, and solves the deficiency that the existing Samba service cannot carry out unified management of two kinds of SMB local users. From the user's perspective, no matter it is single node mode or cluster mode, the SMB user who adds, modifies and deletes in a kind of working mode can be seamlessly switched to take effect in another kind of working mode. On this basis, the whole technology realizes the use of an integrated management mechanism, while centrally and uniformly managing user data, reduces the problem of excessive fragmentation of user data storage, has a very obvious positive effect on the stability of the Linux end Samba service and the ease of use of SMB sharing, and has a very high use value for the centralized and unified management of SMB local users in enterprises.

It can be seen that the SMB user management method provided in the embodiment of the present application creates a unified database in the shared service cluster, so that all service nodes in the shared service cluster are connected to the unified database, which is used to store the user information table of all SMB users created under each service node, and the user information table records the user label and user serial number of the corresponding SMB user, the user label indicates the user type of the corresponding SMB user, that is, the independent user in the single node mode and the cluster user in the cluster mode, and the user serial number indicates the serial number of the most recent update of the corresponding SMB user, which can ensure that the most recently updated SMB user with the same name can be retrieved when the user searches. On this basis, after a target SMB user is created, the corresponding user information table in the unified database can be set according to the working mode of the shared service cluster, that is, the user label and user serial number of the SMB user are set, so that the SMB user management in the shared service cluster can be realized according to the user information recorded in each user information table in the unified database. Therefore, the technical solution realizes the simultaneous support of the shared service cluster for the single node mode and the cluster mode, and then realizes the unified management of SMB users by the shared service cluster under two different working modes.

An embodiment of the present application provides an SMB user management device.

Please refer to FIG. 4 , which is a schematic diagram of the structure of an SMB user management device provided by the present application. The SMB user management device is applied to any service node in a shared service cluster. All service nodes in the shared service cluster are connected to a unified database. The unified database is used to store user information tables of all SMB users in the shared service cluster. The SMB user management device may include:

Determine module 1, for, when receiving an SMB user creation command, creating a target SMB user according to the SMB user creation command, and determining a working mode of the shared service cluster; the working modes include a single node mode and a cluster mode;

The first setting module 2 is used for, if the working mode is the single-node mode, determining the SMB users with the same name as the target SMB user in other service nodes, determining the new serial number according to the serial numbers of the SMB users with the same name, setting the user serial number as the new serial number in the user information table corresponding to the target SMB user, and setting the user label as an independent user;

The second setting module 3 is used to set the user serial number as the default serial number in the user information table corresponding to the target SMB user and set the user tag as a cluster user if the working mode is the cluster mode; wherein the user serial number in the cluster mode is updated as the corresponding user information table is updated;

The management module 4 is used to manage each SMB user according to each user information table in the unified database.

It can be seen that the SMB user management device provided in the embodiment of the present application creates a unified database in the shared service cluster, so that all service nodes in the shared service cluster are connected to the unified database, which is used to store the user information table of all SMB users created under each service node, and the user information table records the user label and user serial number of the corresponding SMB user, the user label indicates the user type of the corresponding SMB user, that is, the independent user in the single node mode and the cluster user in the cluster mode, and the user serial number indicates the serial number of the most recent update of the corresponding SMB user, which can ensure that the most recently updated SMB user with the same name can be retrieved when the user searches. On this basis, after a target SMB user is created, the corresponding user information table in the unified database can be set according to the working mode of the shared service cluster, that is, the user label and user serial number of the SMB user are set, so that the SMB user management in the shared service cluster can be realized according to the user information recorded in each user information table in the unified database. Therefore, the technical solution realizes the simultaneous support of the shared service cluster for the single node mode and the cluster mode, and then realizes the unified management of SMB users by the shared service cluster under two different working modes.

In one embodiment of the present application, when the SMB user management operation is specifically a modification operation, the management module 4 may be specifically used to:

Determine the user data of the SMB user to be modified;

If the working mode is single-node mode, determine whether there is an SMB user with the same name as the SMB user to be modified locally in the service node; if so, overwrite the original user data of the SMB user with the same name with the user data, and set the user label as an independent user in the user information table corresponding to the SMB user with the same name; if not, execute the step of creating the target SMB user according to the SMB user creation command;

If the working mode is cluster mode, determine whether there is an SMB user with the same name as the SMB user to be modified in the shared service cluster; if so, use the user data to overwrite the original user data of the SMB user with the same name, set the user label as a cluster user in the user information table corresponding to the SMB user with the same name, and synchronize other service nodes to perform the modification operation; if not, execute the steps of creating the target SMB user according to the SMB user creation command.

In one embodiment of the present application, when the SMB user management operation is specifically a retrieval operation, the management module 4 may be specifically used to:

Determine the user information of the target SMB user to be queried;

If the working mode is single node mode, the user information is used to determine whether the target query SMB user exists locally in the service node; if so, the user data of the target query SMB user is output; if not, an error prompt is output;

If the working mode is cluster mode, the user information is used to determine whether there is a target query SMB user with a user label of cluster user locally in the service node; if so, the user data of the target query SMB user with a user label of cluster user is output; if not, all target query SMB users with a user label of independent users are determined in the shared service cluster, and the target query SMB user with the latest user serial number is determined among all target query SMB users with user labels of independent users, and the user data of the target query SMB user with the latest user serial number is output.

In one embodiment of the present application, when the SMB user management operation is specifically a deletion operation, the management module 4 may be specifically used to:

Confirm the SMB user to be deleted;

If the working mode is single node mode, the SMB user with the same name as the SMB user to be deleted in the local service node will be deleted;

If the working mode is cluster mode, delete the SMB user with the same name as the SMB user to be deleted in the shared service cluster.

In one embodiment of the present application, the SMB user management device may also include a user group creation module, which is used to determine whether there is a default user group in the shared service cluster after creating the target SMB user according to the SMB user creation command when the SMB user creation command is received; if so, execute the step of determining the working mode of the shared service cluster; if not, set the target SMB user to belong to the default user group, and add the user information of the target SMB user to the member list of the default user group, and return to the step of creating the target SMB user according to the SMB user creation command when the SMB user creation command is received.

In one embodiment of the present application, the SMB user management device may also include a cluster update module, which is used to determine the working mode of the shared service cluster when the service node is a newly joined service node; if the working mode is a single node mode, a preset operation is executed; if the working mode is a cluster mode, the user information of each SMB user with a user label as a cluster user is obtained from the main service node of the shared service cluster and saved locally.

In one embodiment of the present application, the SMB user management device may also include an application module for receiving an SMB connection request from a client for a target SMB user; determining whether the target SMB user exists based on the SMB connection request; if not, feeding back an error prompt to the client; if so, feeding back a response message to the client to receive password data of the target SMB user sent by the client, verifying the password data using the registered password data of the target SMB user, and establishing an SMB connection with the client when the verification passes.

For an introduction to the device provided in the embodiments of the present application, please refer to the above method embodiments, and the present application will not elaborate on them here.

An embodiment of the present application provides an electronic device.

Please refer to FIG5 , which is a schematic diagram of the structure of an electronic device provided by the present application. The electronic device may include:

A memory 11, used for storing computer programs;

The processor 10 can implement the steps of any one of the above-mentioned SMB user management methods when executing a computer program.

As shown in Fig. 5, it is a schematic diagram of the composition structure of an electronic device, which may include: a processor 10, a memory 11, a communication interface 12 and a communication bus 13. The processor 10, the memory 11 and the communication interface 12 all communicate with each other through the communication bus 13.

In the embodiment of the present application, the processor 10 may be a central processing unit (CPU), an application specific integrated circuit, a digital signal processor, a field programmable gate array or other programmable logic devices, etc.

The processor 10 may call a program stored in the memory 11. Specifically, the processor 10 may execute operations in an embodiment of the SMB user management method.

The memory 11 is used to store one or more programs, which may include program codes, and the program codes include computer operation instructions. In the embodiment of the present application, the memory 11 at least stores programs for implementing the following functions:

When receiving an SMB user creation command, a target SMB user is created according to the SMB user creation command, and the working mode of the shared service cluster is determined; the working modes include single-node mode and cluster mode;

If the working mode is single-node mode, determine the SMB users with the same name as the target SMB user in other service nodes, determine the new serial number according to the serial numbers of each SMB user with the same name, set the user serial number to the new serial number in the user information table corresponding to the target SMB user, and set the user label to an independent user;

If the working mode is cluster mode, the user serial number is set as the default serial number in the user information table corresponding to the target SMB user, and the user tag is set as a cluster user; wherein the user serial number in the cluster mode is updated as the corresponding user information table is updated;

Each SMB user is managed according to the user information table in the unified database.

In a possible implementation, the memory 11 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application required for at least one function, etc.; the data storage area may store data created during use.

In addition, the memory 11 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device or other volatile solid-state storage device.

The communication interface 12 may be an interface of a communication module, and is used to connect to other devices or systems.

Of course, it should be noted that the structure shown in FIG. 5 does not constitute a limitation on the electronic device in the embodiment of the present application. In actual applications, the electronic device may include more or fewer components than those shown in FIG. 5 , or combine certain components.

An embodiment of the present application provides a computer-readable storage medium.

The computer-readable storage medium provided in the embodiment of the present application stores a computer program, and when the computer program is executed by a processor, the steps of any one of the above-mentioned SMB user management methods can be implemented.

Among them, the computer-readable storage medium can be any available medium that can be stored in a computer or a data storage device such as a server or data center that includes one or more available media integrated. For example, it can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape, etc.), an optical medium (such as a DVD) or a semiconductor medium (such as a solid-state hard disk) and other media that can store computer program codes.

For an introduction to the computer-readable storage medium provided in the embodiments of the present application, please refer to the above method embodiments, and the present application will not elaborate on them here.

An embodiment of the present application provides a computer program product.

The computer program product provided in the embodiments of the present application includes a computer program/instruction, and when the computer program/instruction is executed by a processor, the steps of any one of the above-mentioned SMB user management methods can be implemented.

Specifically, in the above embodiments, all or part of them can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of them can be implemented in the form of a computer program product.

Among them, the computer program product may include one or more computer programs/instructions, and when the computer program/instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application may be generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. Computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, computer instructions may be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line, etc.) or wireless (e.g., infrared, wireless, microwave, etc.) means.

For an introduction to the computer program product provided in the embodiments of the present application, please refer to the above method embodiments, and the present application will not elaborate on them here.

The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

The technical solution provided by the present application is described in detail above. The principle and implementation method of the present application are described in detail using specific examples herein, and the description of the above embodiments is only used to help understand the method and core idea of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the principle of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the present application.

Claims (10)

1. The SMB user management method is characterized by being applied to any service node in a shared service cluster, wherein all the service nodes in the shared service cluster are connected to a unified database, and the unified database is used for storing user information tables of all SMB users in the shared service cluster, and the method comprises the following steps:

When receiving an SMB user creation command, creating a target SMB user according to the SMB user creation command, and determining the working mode of the shared service cluster; the working modes comprise a single-node mode and a cluster mode;

If the working mode is the single-node mode, determining the same name SMB users of the target SMB users in other service nodes, determining a new serial number according to the serial numbers of the same name SMB users, setting a user serial number as the new serial number in a user information table corresponding to the target SMB users, and setting a user tag as an independent user;

If the working mode is the cluster mode, setting a user serial number as a default serial number in a user information table corresponding to the target SMB user, and setting a user tag as a cluster user; wherein, the user serial number in the cluster mode is updated along with the update of the corresponding user information table;

and managing each SMB user according to each user information table in the unified database.

2. The SMB user management method according to claim 1, wherein when the SMB user management operation is specifically a modification operation, said managing each SMB user according to each user information table in said unified database includes:

determining user data of the SMB user to be modified;

If the working mode is the single-node mode, judging whether the service node locally has the same name SMB user of the SMB user to be modified; if yes, the user data is used for covering the original user data of the same-name SMB users, and a user tag is set as an independent user in a user information table corresponding to the same-name SMB users; if not, executing the step of creating a target SMB user according to the SMB user creation command;

If the working mode is the cluster mode, judging whether the shared service cluster has the same name SMB user of the SMB user to be modified; if so, covering the original user data of the same-name SMB user by using the user data, setting a user tag as a cluster user in a user information table corresponding to the same-name SMB user, and synchronizing other service nodes to execute the modification operation; and if not, executing the step of creating the target SMB user according to the SMB user creation command.

3. The SMB user management method according to claim 1, wherein when the SMB user management operation is specifically a search operation, said managing each SMB user according to each user information table in said unified database includes:

Determining user information of a target query SMB user;

if the working mode is the single-node mode, judging whether the target query SMB user exists locally by using the user information; if yes, outputting the user data of the target query SMB user; if not, outputting an error prompt;

If the working mode is the cluster mode, judging whether a target query SMB user with a user label as a cluster user exists locally by utilizing the user information; if yes, outputting user data of target query SMB users with the user labels as clustered users; if the target query SMB users with the user labels being independent users are not found in the shared service cluster, and the target query SMB users with the user serial numbers being the latest serial numbers are found in the target query SMB users with the user labels being independent users, and the user data of the target query SMB users with the user serial numbers being the latest serial numbers are output.

4. The SMB user management method according to claim 1, wherein when the SMB user management operation is specifically a delete operation, said managing each SMB user according to each user information table in said unified database includes:

determining SMB users to be deleted;

if the working mode is the single-node mode, deleting the SMB user to be deleted from the same-name SMB user local to the service node;

and if the working mode is the cluster mode, deleting the SMB users with the same name in the shared service cluster by the SMB users to be deleted.

5. The SMB user management method according to claim 1, wherein when receiving an SMB user creation command, after creating a target SMB user according to the SMB user creation command, further comprising:

Judging whether a default user group exists in the shared service cluster;

if yes, executing the step of determining the working mode of the shared service cluster;

If not, setting that the target SMB user belongs to the default user group, adding the user information of the target SMB user into a member list of the default user group, and returning to the step of creating the target SMB user according to the SMB user creation command when the SMB user creation command is received.

6. The SMB user management method according to claim 1, wherein when said service node is a newly joining service node, said method further comprises:

Determining a working mode of the shared service cluster;

if the working mode is the single-node mode, executing preset operation;

and if the working mode is the cluster mode, acquiring user information of each SMB user with a user label as a cluster user from a main service node of the shared service cluster, and storing the user information to a local.

7. The SMB user management method according to any one of claims 1 to 6, further comprising:

Receiving an SMB connection request of a client for the target SMB user;

Judging whether the target SMB user exists or not according to the SMB connection request;

If not, feeding back an error prompt to the client;

If yes, feeding back response information to the client to receive the password data of the target SMB user sent by the client, checking the password data by using the registered password data of the target SMB user, and establishing SMB connection with the client when the password data passes the check.

8. An SMB user management device, applied to any service node in a shared service cluster, where all service nodes in the shared service cluster are connected to a unified database, and the unified database is used to store user information tables of all SMB users in the shared service cluster, where the device includes:

the determining module is used for creating a target SMB user according to the SMB user creation command when the SMB user creation command is received, and determining the working mode of the shared service cluster; the working modes comprise a single-node mode and a cluster mode;

the first setting module is used for determining the same name SMB users of the target SMB users in other service nodes if the working mode is the single node mode, determining new serial numbers according to serial numbers of the same name SMB users, setting the user serial numbers as the new serial numbers in a user information table corresponding to the target SMB users, and setting user labels as independent users;

The second setting module is used for setting a user serial number as a default serial number in a user information table corresponding to the target SMB user if the working mode is the cluster mode, and setting a user label as a cluster user; wherein, the user serial number in the cluster mode is updated along with the update of the corresponding user information table;

And the management module is used for managing each SMB user according to each user information table in the unified database.

9. An electronic device, comprising:

A memory for storing a computer program;

A processor for implementing the steps of the SMB user management method of any of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the SMB user management method of any of claims 1 to 7.