Method and apparatus for processing user identification

Abstract

The application provides a user identification processing method and device, the method comprising: receiving a user's identification request for a target application component; determining whether there is an associated application component of the target application component; if there is the associated application component of the target application component, determining whether the identification request contains a user specified identification; if the identification request does not contain the user specified identification, generating a target identification of the user; determining whether there is a user identification consistent with the target identification in an associated component identification file; the associated component identification file is used to record the user identification of the target application component and the user identification of the associated application component; if there is no user identification consistent with the target identification in the associated component identification file, taking the target identification as the user identification of the user. The application avoids the problem of file permission expansion caused by the reuse of application user UID between associated components.

Description

TECHNICAL FIELD

[0001] The present application relates to the computer technical field, in particular to a user identification processing method and device. BACKGROUND

[0002] At present, most of the application systems deployed on Linux operating system adopt cluster mode deployment, and a set of application system is often deployed on multiple servers, and a set of application system has multiple application components, different components are deployed on multiple different servers, and there is also interaction between different components.

[0003] If the servers of different components have different application users, but have the same UID, the reuse of the UID will expand the data authority range of the associated components, and is easy to cause data tampering and leakage. SUMMARY

[0004] The technical problem to be solved by the present application is to provide a user identification processing method, which can avoid the file permission expansion problem caused by the reuse of application user UID between associated components.

[0005] The present application also provides a user identification processing device to ensure the implementation and application of the above method in practice.

[0006] A user identification processing method, comprising:

[0007] Receiving an identification request sent by a user for a target application component;

[0008] Determining whether there is an associated application component of the target application component;

[0009] If there is an associated application component of the target application component, determining whether the identification request contains a user-specified identification;

[0010] If the identification request does not contain a user-specified identification, generating a target identification of the user;

[0011] Determining whether there is a user identification consistent with the target identification in an associated component identification file; the associated component identification file is used to record the user identification of the target application component and the user identification of the associated application component;

[0012] If the associated component identification file does not have a user identification consistent with the target identification, the target identification is used as the user identification of the user.

[0013] The above method, optionally, the generating a target identification of the user, comprises:

[0014] determining a preset minimum value of the target application component;

[0015] setting the minimum value as the target identity of the user.

[0016] The method further comprises:

[0017] If the association component identification file contains a user identity consistent with the target identity, the target identity is updated in a preset manner to obtain a new target identity.

[0018] determining whether the new target identity is greater than a preset maximum identity value.

[0019] If the new target identity is not greater than the maximum identity value, it is determined again whether the association component identification file contains a user identity consistent with the new target identity. When the association component identification file does not contain a user identity consistent with the new target identity, the new target identity is set as the user identity of the user.

[0020] The method further comprises:

[0021] If the new target identity is greater than the preset maximum identity value, a prompt message is sent, and the prompt message is used to prompt that the user identity creation fails.

[0022] The method further comprises:

[0023] determining a mounting point of a shared storage NAS to which the target application component belongs;

[0024] determining whether the mounting point of the NAS contains an application component other than the target application component;

[0025] If the mounting point of the NAS contains an application component other than the target application component, the application component is determined as an association component of the target application component.

[0026] If the mounting point of the NAS does not contain an application component other than the target application component, it is determined that there is no association application component of the target application component.

[0027] A user identity processing apparatus comprises:

[0028] a receiving unit configured to receive an identity request for a target application component sent by a user;

[0029] a first determining unit configured to determine whether there is an association application component of the target application component;

[0030] The determining unit is configured to determine whether the identification request contains a user-specified identification if there is an associated application component of the target application component;

[0031] The generating unit is configured to generate a target identification of the user if the identification request does not contain a user-specified identification.

[0032] The second judging unit is configured to judge whether there is a user identification consistent with the target identification in an associated component identification file, wherein the associated component identification file is used to record user identifications of the target application component and user identifications of the associated application component.

[0033] The first executing unit is configured to take the target identification as the user identification of the user if there is no user identification consistent with the target identification in the associated component identification file.

[0034] The device described above, optionally, the generating unit comprises:

[0035] The first determining sub-unit is configured to determine a pre-set minimum identification of a cluster system in which the target application component is located.

[0036] The executing sub-unit is configured to take the minimum identification as the target identification of the user.

[0037] The device described above, optionally, further comprises:

[0038] The updating unit is configured to update the target identification in a pre-set updating manner to obtain a new target identification if there is a user identification consistent with the target identification in the associated component identification file.

[0039] The judging unit is configured to judge whether the new target identification satisfies a pre-set maximum identification value.

[0040] The second executing unit is configured to re-judge whether there is a user identification consistent with the new target identification in the associated component identification file if the new target identification is not greater than the maximum identification value, and take the new target identification as the user identification of the user when there is no user identification consistent with the new target identification in the associated component identification file.

[0041] The device described above, optionally, further comprises:

[0042] The sending unit is configured to send a prompt information if the new target identification is greater than the pre-set maximum identification value, wherein the prompt information is used to prompt a user identification creation failure.

[0043] The device described above, optionally, the first judging unit comprises:

[0044] A second determining sub-unit is configured to determine a mounting point of a shared storage NAS to which the target application component belongs;

[0045] A judging sub-unit is configured to judge whether the mounting point of the NAS has application components other than the target application component;

[0046] A third determining sub-unit is configured to determine the application components as the associated components of the target application component if the mounting point of the NAS has application components other than the target application component;

[0047] A fourth determining sub-unit is configured to determine that there is no associated application component of the target application component if the mounting point of the NAS has no application components other than the target application component.

[0048] Compared with the prior art, the present application has the following advantages:

[0049] The present application provides a user identification processing method and device, which comprises the following steps: receiving a user's identification request for a target application component; judging whether there is an associated application component of the target application component; determining whether the identification request contains a user-specified identification if there is an associated application component of the target application component; generating a target identification of the user if the identification request does not contain a user-specified identification; judging whether the associated component identification file has a user identification consistent with the target identification; the associated component identification file is used to record the user identification of the target application component and the user identification of the associated application component; and taking the target identification as the user identification of the user if the associated component identification file does not have a user identification consistent with the target identification. The present application can avoid the file permission denial problem and the application start-stop problem caused by the difference in application user UID in the same component, and can also avoid the file permission expansion problem caused by the reuse of application user UID between associated components. BRIEF DESCRIPTION OF DRAWINGS

[0050] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description only constitute the embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of the provided drawings.

[0051] Figure 1 A method flow chart of a user identification processing method provided by the present application;

[0052] Figure 2 A process flow chart of judging whether there is an associated application component of a target application component provided by the present application;

[0053] Figure 3 An example diagram illustrating an implementation scenario of the present invention;

[0054] Figure 4 A flowchart for providing a user identifier to a user is provided by the present invention;

[0055] Figure 5 A schematic diagram of the structure of a user identification processing device provided by the present invention;

[0056] Figure 6 This is a schematic diagram of the structure of an electronic device provided by the present invention. Detailed Implementation

[0057] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0058] In this application, the terms "comprising," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0059] In related technologies, users typically submit applications for user IDs and / or user group IDs to the platform manually. There are no unified standards or specifications for these applications; in most cases, they are defined by the applicants themselves. Applicants often have limited understanding of user identification across system components. Furthermore, these applications only consider the uniqueness of Linux system UIDs on a single server, neglecting the uniqueness and consistency issues of Linux system UIDs in cluster mode. This may lead to the following drawbacks:

[0060] First, it may cause inconsistencies in UIDs between users of the same component application within the application system, leading to file permission denial issues and application startup / shutdown problems.

[0061] Secondly, it may cause security risks such as file tampering due to UID reuse among related components within the application system.

[0062] Based on this, the embodiment of the present application provides a user identification processing method, which can be applied to an electronic device, which can be a computer, and a method flowchart of the method is as shown in Figure 1 The method specifically comprises the following steps.

[0063] S101: receiving an identification request for a target application component sent by a user.

[0064] In the embodiment of the present application, the identification request can be used to apply for a user identification, the target application component can be an application component deployed in a server cluster, and the target application component can access each server of the server cluster.

[0065] S102: judging whether there is an associated application component of the target application component.

[0066] The associated application component of the target application component refers to an application component mounted with the same NAS volume as the target application component.

[0067] S103: if there is the associated application component of the target application component, determining whether the identification request contains a user specified identification.

[0068] In the embodiment of the present application, if there is the user specified identification, it can be judged whether there is a user identification consistent with the identification in the associated component identification, and if there is no user identification consistent with the identification, the identification can be used as the user identification of the user.

[0069] S104: if the identification request does not contain the user specified identification, generating a target identification of the user.

[0070] Specifically, the target identification of the user can be generated according to an identification generation rule of the target application component.

[0071] S105: judging whether there is a user identification consistent with the target identification in an associated component identification file; the associated component identification file is used to record the user identification of the target application component and the user identification of the associated application component.

[0072] In the embodiment of the present application, the user identification can be a UID or a GID, and the associated component identification file can be a database.

[0073] S106: if there is no user identification consistent with the target identification in the associated component identification file, using the target identification as the user identification of the user.

[0074] In the embodiment of the present application, if the association component identification file does not have a user identification consistent with the target identification, a user object user can be created by the target identification, and the target identification is recorded in the association component identification file as the user identification of the user, so that the uniqueness of the user identification of the target application component and the associated component can be ensured.

[0075] In the method provided by the embodiment of the present application, based on the above implementation process, specifically, a feasible way of generating the target identification of the user includes:

[0076] determining a preset minimum identification of a cluster system in which the target application component is located;

[0077] taking the minimum identification as the target identification of the user.

[0078] Specifically, the target identification can be set as the minimum identification allowed by the cluster system of the target application component.

[0079] In the method provided by the embodiment of the present application, based on the above implementation process, specifically, the method further includes:

[0080] if the association component identification file has a user identification consistent with the target identification, updating the target identification according to a preset updating mode to obtain a new target identification;

[0081] determining whether the new target identification is greater than a preset maximum identification value;

[0082] if the new target identification is not greater than the maximum identification value, re-determining whether the association component identification file has a user identification consistent with the new target identification, and taking the new target identification as the user identification of the user when the association component identification file does not have a user identification consistent with the new target identification.

[0083] In the embodiment of the present application, a feasible way of updating the target identification according to the preset updating mode is adding a preset value to the target identification to obtain a new target identification. The value can be any value such as 1, 2 or 5.

[0084] The maximum identification value can be set according to actual needs.

[0085] In the method provided by the embodiment of the present application, based on the above implementation process, specifically, the method further includes:

[0086] if the new target identification is greater than the preset maximum identification value, sending a prompt information, and the prompt information is used to prompt that the user identification creation fails.

[0087] In this embodiment of the invention, based on the above implementation process, specifically, it further includes: if there is no associated application component of the target application component, determining whether the identification request contains a user-specified identifier; if the identification request does not contain a user-specified identifier, generating a target identifier for the user; determining whether there is a user identifier in the component identifier file that matches the target identifier; the component identifier file is used to record the user identifier of the target application component; if there is no user identifier in the component identifier file that matches the target identifier, then using the target identifier as the user identifier for the user.

[0088] In the method provided in this embodiment of the invention, based on the above implementation process, specifically, the process of determining whether there is an associated application component of the target application component is as follows: Figure 2 As shown, it specifically includes:

[0089] S201: Determine the mount point of the shared storage NAS to which the target application component belongs.

[0090] S202: Determine whether the NAS mount point contains any application components other than the target application component.

[0091] S203: If there are application components other than the target application component, then the application component is determined as an associated component of the target application component.

[0092] S204: If there are no application components other than the target application component, then it is determined that there are no associated application components of the target application component.

[0093] In one embodiment of the present invention, an example diagram of an implementation scenario is provided, such as... Figure 3 As shown, this implementation scenario includes an electronic device deploying a Linux system. The system manages various application components deployed on different clusters, specifically application component A, application component B, application component C, and application component D. When the electronic device receives an identification request for application component A, it can use application component A as the target application component. After receiving the user's identification request for application component A, a flowchart is provided to the user with the user's identification, as shown below. Figure 4 As shown, it includes the following steps:

[0094] S401: Determine whether the cluster of component A of the requesting user has established a UID list database, i.e., component identification file.

[0095] S402: If the UID list database for component A cluster has not been created, the corresponding database can be created by obtaining it from / etc / passwd.

[0096] S403: Start the process of creating a new user.

[0097] S404: Determine if component A is associated with other components; if not, go to S405; if yes, go to S415.

[0098] S405: Determine if the applicant user has specified a UID; if not, go to S406; if yes, go to S412.

[0099] S406: If the applicant user has not specified a UID, set the UID to the minimum value of the UID allowed by the component A cluster system, and go to S407.

[0100] S407: Determine if the UID exists in the component A cluster UID list database. If yes, go to S408; if not, go to S410.

[0101] S408: Determine if the UID is greater than the maximum value of the UID allowed by the system. If yes, go to S409; if not, increment the UID by 1, and go to S407.

[0102] S409: Prompt that the set UID exceeds the maximum value of the UID allowed by the system, and exit the entire process.

[0103] S410: If the set UID does not exist in the component A cluster UID list database, create a user using this UID, and go to S411.

[0104] S411: Write the created UID into the UID list database, and end the entire process.

[0105] S412: If the applicant specifies a UID, further determine if the specified UID exists in the UID list database. If not, go to S413; if yes, go to S414.

[0106] S413: The specified UID does not exist in the UID list database, so create a user using the specified UID, and deploy the created user on all server systems of the component.

[0107] S414: The specified UID exists in the UID list database, so prompt that the UID already exists, and end the process.

[0108] S415: Component A is associated with other components, if the associated component UID list database does not exist, establish the associated component UID list database, if it already exists, go to S416; if not, go to S417. The associated component UID list database is the associated component identification file.

[0109] S416: New associated component UID list database.

[0110] S417: Determine if a UID is specified. If yes, proceed to S418; otherwise, proceed to S422.

[0111] S418: Determine if the UID exists in the associated component UID list database. If not, proceed to S419; if yes, proceed to S421.

[0112] S419: If the applicant specifies a UID and the UID does not exist in the associated component's UID list database, then use this UID to create a user. The created user is deployed on all server systems of this component, proceeding to S420.

[0113] S420: Write the created UID to the associated component UID list database and end the process.

[0114] S421: The specified UID already exists in the associated component. The system will indicate that the UID already exists and end the process.

[0115] S422: If the applicant does not specify a UID, then set the UID to the minimum UID allowed by the Component A cluster system, and proceed to S423.

[0116] S423: Determine if the UID exists in the associated component's UID list database. If yes, proceed to S424; otherwise, proceed to S426.

[0117] S424: The UID exists in the associated component UID list database. Determine if the UID is greater than the maximum allowed UID by the system. If yes, proceed to S425; otherwise, increment the UID by 1 and proceed to S423.

[0118] S425: The system prompts that the UID exceeds the maximum allowed UID value and exits the process.

[0119] S426: If the UID does not exist in the associated component list database, then use this UID to create a user. The created user is deployed on all server systems of this component, proceed to S427.

[0120] S427: Write the created UID into the associated component list data and end the process.

[0121] Using the method provided in the embodiments of the present invention, a user is created by obtaining a UID from the present invention. The created user is established on all server systems of the component, which ensures that the UID within an independent component is uniquely determined, and also ensures that the UID of the component associated with other components is uniquely set and not reused.

[0122] and Figure 1 Corresponding to the method described above, embodiments of the present invention also provide a user identifier processing device for processing... Figure 1In a specific implementation of the method, the user identification processing apparatus provided by the embodiment of the application can be applied to an electronic device, a structural schematic diagram of which is shown in FIG. 5, and specifically includes the following components: Figure 5

[0123] The receiving unit 501 is configured to receive an identification request for a target application component sent by a user.

[0124] The first judging unit 502 is configured to judge whether there is an associated application component of the target application component.

[0125] The determining unit 503 is configured to determine whether the identification request contains a user-specified identification if there is an associated application component of the target application component.

[0126] The generating unit 504 is configured to generate a target identification of the user if the identification request does not contain a user-specified identification.

[0127] The second judging unit 505 is configured to judge whether there is a user identification consistent with the target identification in an associated component identification file, which is used to record user identifications of the target application component and user identifications of the associated application component.

[0128] The first executing unit 506 is configured to take the target identification as the user identification of the user if there is no user identification consistent with the target identification in the associated component identification file.

[0129] In an embodiment provided by the application, based on the above scheme, the generating unit 504 optionally includes the following components:

[0130] The first determining subunit is configured to determine a pre-set minimum identification value of a cluster system in which the target application component is located.

[0131] The executing subunit is configured to take the minimum identification value as the target identification of the user.

[0132] In an embodiment provided by the application, based on the above scheme, the generating unit 504 optionally includes the following components:

[0133] The updating unit is configured to update the target identification in a pre-set updating manner to obtain a new target identification if there is a user identification consistent with the target identification in the associated component identification file.

[0134] The judging unit is configured to judge whether the new target identification satisfies a pre-set maximum identification value.

[0135] ​The second execution unit is configured to re-determine whether the user identifier consistent with the new target identifier exists in the associated component identifier file if the new target identifier is not greater than the maximum identifier value, and to take the new target identifier as the user identifier of the user when the user identifier consistent with the new target identifier does not exist in the associated component identifier file.

[0136] In an embodiment provided by the application, based on the above scheme, optionally, the method further comprises:

[0137] The sending unit is configured to send prompt information if the new target identifier is greater than the maximum identifier value, and the prompt information is used to prompt the user identifier creation failure.

[0138] In an embodiment provided by the application, based on the above scheme, optionally, the first determination unit 502 comprises:

[0139] The second determination sub-unit is configured to determine the mounting point of the shared storage NAS to which the target application component belongs.

[0140] The determination sub-unit is configured to determine whether the mounting point of the NAS exists the application component other than the target application component.

[0141] The third determination sub-unit is configured to determine the application component other than the target application component as the associated component of the target application component if the application component other than the target application component exists.

[0142] The fourth determination sub-unit is configured to determine that the associated application component of the target application component does not exist if the application component other than the target application component does not exist.

[0143] The embodiment of the application further provides a storage medium, which comprises stored instructions, wherein the instructions control the device where the storage medium is located to execute the processing method of the user identifier when the instructions are executed.

[0144] The embodiment of the application further provides an electronic device, and a structure diagram thereof is shown in Figure 6 The electronic device specifically comprises a memory 601 and one or more than one instruction 602, wherein the one or more than one instruction 602 is stored in the memory 601 and is configured to be executed by one or more than one processor 603 to perform the following operations:

[0145] Receiving the identifier request for the target application component sent by the user;

[0146] Determining whether the associated application component of the target application component exists;

[0147] If the associated application component of the target application component exists, it is determined whether the identification request contains a user-specified identification;

[0148] If the identification request does not contain a user-specified identification, a target identification of the user is generated;

[0149] It is determined whether the associated component identification file contains a user identification consistent with the target identification; the associated component identification file is used to record the user identification of the target application component and the user identification of the associated application component;

[0150] If the associated component identification file does not contain a user identification consistent with the target identification, the target identification is taken as the user identification of the user.

[0151] It should be noted that each of the above-described embodiments of the present application is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts of each embodiment can be understood by mutual reference. For the device embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be understood by referring to the description of the method embodiments.

[0152] Finally, it should be noted that in this document, the relationship terms such as first and second are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or device. Without more limitations, the element defined by the statement "including a" does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0153] For the convenience of description, the above device is described by dividing it into various units and describing each unit respectively. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0154] Those skilled in the art can clearly understand the present application by the description of the above embodiments. Based on such an understanding, the technical solutions of the present application can be embodied in the form of a software product, which can be stored in a storage medium, such as a ROM / RAM, a magnetic disk, an optical disk, and the like, and includes a number of instructions to make a computer device (which can be a personal computer, a server, or a network device, and the like) execute the methods described in the various embodiments or some parts of the embodiments of the present application.

[0155] The above describes in detail the user identification processing method provided by the present application. The principles and implementation manners of the present application are described by using specific examples. The above description of the embodiments is only used to help understand the method of the present application and its core idea. Meanwhile, for those skilled in the art, the specific implementation manners and application ranges can be changed according to the idea of the present application. In summary, the content of the present description should not be understood as a limitation of the present application.

Claims

1. A method of processing a user identification, characterized by, The method comprises the following steps: receiving an identification request sent by a user for a target application component; determining whether there is an associated application component of the target application component; if there is an associated application component of the target application component, determining whether the identification request contains a user-specified identification; if the identification request does not contain a user-specified identification, generating a target identification of the user; the generating of the target identification of the user comprises: determining a preset minimum identification value of a cluster system in which the target application component is located; and taking the minimum identification value as the target identification of the user; determining whether there is a user identification consistent with the target identification in an associated component identification file used for recording user identifications of the target application component and user identifications of the associated application component; if there is no user identification consistent with the target identification in the associated component identification file, taking the target identification as the user identification of the user.

2. The method of claim 1, wherein, The method further comprises the following steps: if there is a user identification consistent with the target identification in the associated component identification file, updating the target identification in a preset updating mode to obtain a new target identification; the preset updating mode is adding a preset value to the target identification; the preset value at least includes 1, 2 or 5; determining whether the new target identification satisfies a preset maximum identification value; if the new target identification is not greater than the maximum identification value, re-determining whether there is a user identification consistent with the new target identification in the associated component identification file, and taking the new target identification as the user identification of the user when there is no user identification consistent with the new target identification in the associated component identification file.

3. The method of claim 2, wherein, The method further comprises the following steps: if the new target identification is greater than the preset maximum identification value, sending a prompt information used for prompting a user identification creation failure.

4. The method of claim 1, wherein, The determining of whether there is an associated application component of the target application component comprises the following steps: determining a mounting point of a shared storage NAS to which the target application component belongs; determining whether there is an application component other than the target application component in the mounting point of the NAS; if there is an application component other than the target application component, determining the application component as an associated component of the target application component; if there is no application component other than the target application component, determining that there is no associated application component of the target application component.

5. A processing device for user identification, characterized in that, The method comprises the following steps: a receiving unit configured to receive an identification request sent by a user for a target application component; a first determining unit configured to determine whether there is an associated application component of the target application component; a determining unit configured to, if there is an associated application component of the target application component, determine whether the identification request contains a user-specified identification; a generating unit configured to, if the identification request does not contain a user-specified identification, generate a target identification of the user; the generating unit comprises a first determining subunit and an executing subunit; the first determining subunit is configured to determine a preset minimum identification value of a cluster system in which the target application component is located; The execution subunit is configured to take the minimum value of the identification as the target identification of the user; The second judging unit is configured to judge whether the target identification is consistent with a user identification in an associated component identification file, wherein the associated component identification file is used to record a user identification of the target application component and a user identification of the associated application component; The first execution unit is configured to take the target identification as the user identification of the user if the associated component identification file does not have a user identification consistent with the target identification.

6. The apparatus of claim 5, wherein, Further comprising: The updating unit is configured to update the target identification in a preset updating mode to obtain a new target identification if the associated component identification file has a user identification consistent with the target identification, wherein the preset updating mode is to add a preset value to the target identification, and the preset value at least includes 1, 2 or 5; The judging unit is configured to judge whether the new target identification is greater than a preset maximum identification value; The second execution unit is configured to re-judge whether the new target identification is consistent with a user identification in the associated component identification file if the new target identification is not greater than the maximum identification value, and take the new target identification as the user identification of the user when the associated component identification file does not have a user identification consistent with the new target identification.

7. The apparatus of claim 6, wherein, Further comprising: The sending unit is configured to send a prompt information if the new target identification is greater than the preset maximum identification value, wherein the prompt information is used to prompt a user identification creation failure.

8. The apparatus of claim 5, wherein, The first judging unit comprises: The second determining subunit is configured to determine a mounting point of a shared storage NAS to which the target application component belongs; The judging subunit is configured to judge whether the mounting point of the NAS has an application component other than the target application component; The third determining subunit is configured to determine the application component as an associated component of the target application component if the mounting point of the NAS has an application component other than the target application component; The fourth determining subunit is configured to determine that there is no associated application component of the target application component if the mounting point of the NAS does not have an application component other than the target application component.

Images