File system management method, device, computer equipment, storage medium and program product

Abstract

The present application relates to a method, apparatus, computer equipment, storage medium and program product for managing a file system. The method comprises: receiving a mount request sent by a user terminal, authenticating the file system information according to a pre-stored key table file, creating a target user account associated with the user information locally when the authentication is passed, and managing the file system according to the target user account; the mount request includes file system information and user information, and the key table file is generated according to the administrator information of the resource management platform and the corresponding file system information. In the above method, when responding to a user request, the file system server only needs to authenticate the file system information with the local key table file, and create a user account locally based on the user information, thereby realizing the management of the file system in the file system server, without the need to interact with the AD domain controller, which is in line with the architectural design of the current public cloud scenario.

Description

Technical Field

[0001] The present application relates to the field of cloud platform technology, and in particular to a file system management method, apparatus, computer equipment, storage medium, and program product. Background Art

[0002] With the advent of the information age, the amount of data generated by enterprises has exploded. Traditional data storage methods can no longer meet enterprises' needs for data capacity, security, and scalability. Public cloud file systems, as a cloud computing-based data storage solution, can provide high-capacity, highly reliable storage space, effectively solving enterprises' data storage challenges.

[0003] To uniformly manage and schedule file systems and enhance data security, file systems are often authorized and managed using an AD domain. Traditional solutions for managing file systems using an AD domain include adding the server node where the file system resides to the AD domain environment so that the AD domain manages the server node. When a client accesses the server where the file system resides, the server must communicate with the AD domain controller. This requires network connectivity between the AD domain controller node, the client, and the server node where the file system resides.

[0004] However, in the public cloud scenario, the above file system management method is not applicable. Summary of the Invention

[0005] Based on this, it is necessary to provide a file system management method, apparatus, computer equipment, storage medium and program product capable of managing file systems in a public cloud scenario to address the above technical problems.

[0006] In a first aspect, the present application provides a file system management method, which is applied to a file system server, comprising:

[0007] Receive the mount request sent by the user; the mount request includes file system information and user information;

[0008] Authenticate the file system information based on the pre-stored key table file; the key table file is generated based on the administrator information of the resource management platform and the corresponding file system information;

[0009] If the authentication is successful, a target user account associated with the user information is created locally, and the file system is managed based on the target user account.

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

[0011] Receive the key table file sent by the client and store the key table file locally.

[0012] In one embodiment, the receiving of the key table file sent by the user terminal and storing the key table file locally includes:

[0013] Perform verification processing on the key table file to obtain the verification processing result;

[0014] If the verification result indicates that the verification is passed, the key table file is stored locally;

[0015] If the verification result indicates that the verification fails, the process returns to the step of performing verification on the key table file to obtain the verification result.

[0016] In one embodiment, the verification process of the key table file to obtain the verification result includes:

[0017] Generate first verification information based on the key table file, and encode the key table file to obtain an encoded key table file;

[0018] Decoding the encoded key table file to obtain a decoded key table file, and generating second verification information based on the decoded key table file;

[0019] Verification processing is performed on the first verification information and the second verification information to obtain a verification processing result.

[0020] In one embodiment, the method further includes:

[0021] Merge the key table file with other key table files and perform deduplication processing to obtain the target key table file; other key table files are generated based on other administrator information of the resource management platform and the corresponding file system information;

[0022] Store the target key table file locally.

[0023] In a second aspect, the present application further provides a file system management method, which is applied to a user terminal and includes:

[0024] Receive the key table file sent by the resource management platform; the key table file is generated based on the administrator information of the resource management platform and the corresponding file system address information;

[0025] Send the key table file to the file system server;

[0026] Send a mount request to the file system server so that the file system server authenticates the file system information in the mount request based on the key table file. If the authentication is successful, the server creates a target user locally based on the user information in the mount request to manage the file system based on the target user.

[0027] In a third aspect, the present application also provides a file system management method, which is applied to a resource management platform, including:

[0028] Generate a key table file based on the manager information and the file system information corresponding to the manager information;

[0029] Send the key table file to the user.

[0030] In a fourth aspect, the present application further provides a file system management device, which is applied to a file system server and includes: a receiving module, an authentication module, and a management module, wherein:

[0031] The receiving module is used to receive the mount request sent by the user end; the mount request includes file system information and user information;

[0032] An authentication module is used to authenticate the file system information based on a pre-stored key table file; the key table file is generated based on the administrator information of the resource management platform and the corresponding file system information;

[0033] The management module is used to create a target user account associated with the user information locally when the authentication is passed, and manage the file system according to the target user account.

[0034] In a fifth aspect, the present application further provides a file system management device, which is applied to a user terminal and includes: a receiving module, a sending module, and a management module, wherein:

[0035] The receiving module is used to receive the key table file sent by the resource management platform; the key table file is generated according to the administrator information of the resource management platform and the corresponding file system address information;

[0036] A sending module, used to send the key table file to the file system server;

[0037] The management module is used to send a mount request to the file system server, so that the file system server authenticates the file system information in the mount request according to the key table file. If the authentication is successful, the target user is created locally according to the user information in the mount request to manage the file system based on the target user.

[0038] In a sixth aspect, the present application further provides a file system management device, which is applied to a resource management platform and includes: a generation module and a sending module, wherein:

[0039] A generation module, configured to generate a key table file based on the manager information and the file system information corresponding to the manager information;

[0040] The sending module is used to send the key table file to the user end.

[0041] In a seventh aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0042] Receive the mount request sent by the user; the mount request includes file system information and user information;

[0043] Authenticate the file system information based on the pre-stored key table file; the key table file is generated based on the administrator information of the resource management platform and the corresponding file system information;

[0044] If the authentication is successful, a target user account associated with the user information is created locally, and the file system is managed based on the target user account.

[0045] In an eighth aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0046] Receive the key table file sent by the resource management platform; the key table file is generated based on the administrator information of the resource management platform and the corresponding file system address information;

[0047] Send the key table file to the file system server;

[0048] Send a mount request to the file system server so that the file system server authenticates the file system information in the mount request based on the key table file. If the authentication is successful, the server creates a target user locally based on the user information in the mount request to manage the file system based on the target user.

[0049] In a ninth aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0050] Generate a key table file based on the manager information and the file system information corresponding to the manager information;

[0051] Send the key table file to the user.

[0052] In a tenth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0053] Receive the mount request sent by the user; the mount request includes file system information and user information;

[0054] Authenticate the file system information based on the pre-stored key table file; the key table file is generated based on the administrator information of the resource management platform and the corresponding file system information;

[0055] If the authentication is successful, a target user account associated with the user information is created locally, and the file system is managed based on the target user account.

[0056] In an eleventh aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0057] Receive the key table file sent by the resource management platform; the key table file is generated based on the administrator information of the resource management platform and the corresponding file system address information;

[0058] Send the key table file to the file system server;

[0059] Send a mount request to the file system server so that the file system server authenticates the file system information in the mount request based on the key table file. If the authentication is successful, the server creates a target user locally based on the user information in the mount request to manage the file system based on the target user.

[0060] In a twelfth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0061] Generate a key table file based on the manager information and the file system information corresponding to the manager information;

[0062] Send the key table file to the user.

[0063] In a thirteenth aspect, the present application further provides a computer program product, comprising a computer program, which, when executed by a processor, implements the following steps:

[0064] Receive the mount request sent by the user; the mount request includes file system information and user information;

[0065] Authenticate the file system information based on the pre-stored key table file; the key table file is generated based on the administrator information of the resource management platform and the corresponding file system information;

[0066] If the authentication is successful, a target user account associated with the user information is created locally, and the file system is managed based on the target user account.

[0067] In a fourteenth aspect, the present application further provides a computer program product, including a computer program, which, when executed by a processor, implements the following steps:

[0068] Receive the key table file sent by the resource management platform; the key table file is generated based on the administrator information of the resource management platform and the corresponding file system address information;

[0069] Send the key table file to the file system server;

[0070] Send a mount request to the file system server so that the file system server authenticates the file system information in the mount request based on the key table file. If the authentication is successful, the server creates a target user locally based on the user information in the mount request to manage the file system based on the target user.

[0071] In a fifteenth aspect, the present application further provides a computer program product, including a computer program, which, when executed by a processor, implements the following steps:

[0072] Generate a key table file based on the manager information and the file system information corresponding to the manager information;

[0073] Send the key table file to the user.

[0074] The above-mentioned file system management method, apparatus, computer equipment, storage medium and program product, when responding to a user request, the file system server only needs to authenticate the file system information with the local key table file and create a user account locally based on the user information to achieve the management of the file system in the file system server. There is no need to interact with the AD domain controller, nor is there a need to add the file system server to the AD domain controller, which is in line with the architectural design of the current public cloud scenario. BRIEF DESCRIPTION OF THE DRAWINGS

[0075] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following briefly introduces the drawings required for use in the embodiments of the present application or related technical descriptions. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying any creative work.

[0076] Figure 1 FIG. 1 is an application environment diagram of a file system management method according to an embodiment;

[0077] Figure 2 1 is a flowchart of a method for managing a file system in one embodiment;

[0078] Figure 3 is a flowchart of a method for managing a file system in another embodiment;

[0079] Figure 4 is a flowchart of a method for managing a file system in another embodiment;

[0080] Figure 5 is a flowchart of a method for managing a file system in another embodiment;

[0081] Figure 6 is a flowchart of a method for managing a file system in another embodiment;

[0082] Figure 7 is a flowchart of a method for managing a file system in another embodiment;

[0083] Figure 8 is a flowchart of a method for managing a file system in another embodiment;

[0084] Figure 9 is a structural block diagram of a file system management device in one embodiment;

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

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

[0087] With the advent of the information age, the amount of data generated by enterprises has exploded. Traditional data storage methods can no longer meet enterprise requirements for data capacity, security, and scalability. Public cloud file systems, as cloud computing-based data storage solutions, provide high-capacity, highly reliable storage space, effectively addressing enterprise data storage challenges. Common Internet File System (CIFS), a type of public cloud file system, is commonly used for data access on Windows devices and is suitable for enterprise office environments.

[0088] In Windows environments, file systems are often managed and authorized using an Active Directory (AD) domain to achieve unified management and scheduling of file systems and enhance data security. Traditional solutions for managing file systems using an AD domain involve adding the server node where the file system resides to the AD domain environment, allowing the AD domain to manage the server node. When a client accesses the server where the file system resides, the server must communicate with the AD domain controller. This requires network connectivity between the AD domain controller node, the client, and the server node where the file system resides.

[0089] However, the above solution is only applicable to private cloud scenarios or offline small-scale deployment applications. In a public cloud scenario, the file system server is located in the cloud service provider's computer room, and the cloud service provider has its management and control authority, while the AD domain controller is usually served by a server outside the cloud or a cloud host server, and the user has full management and control authority. For security reasons, the user's client node and AD controller node can only access the cloud vendor's file system server in one direction, and the file system server cannot reversely access the user's cloud host or AD domain controller. Therefore, the above solution cannot realize the management of the file system by the AD domain controller, that is, in a public cloud scenario, the above file system management method is not applicable. This application aims to solve this problem.

[0090] After introducing the background technology of the file system management method provided by the embodiment of the present application, the following briefly describes the implementation environment involved in the file system management method provided by the embodiment of the present application. The file system management method provided by the embodiment of the present application can be applied to Figure 1 In the implementation environment shown, the implementation environment includes a file system server 10, a resource management platform 20, and a client 30. The file system server 10 is used to store the file system. The resource management platform 20 and the client 30 can perform one-way communication with the file system server 10. That is, the resource management platform 20 and the client 30 can send messages to the file system server 10, but the file system server 10 cannot send messages to the resource management platform 20 and the client 30.

[0091] After introducing the application scenarios of the file system management method provided by the embodiments of the present application, the following focuses on introducing the file system management method described in the present application.

[0092] In one embodiment, Figure 2 As shown, a file system management method is provided, which is applied to Figure 1 Taking the file system server 10 in FIG. 1 as an example, the method includes the following steps:

[0093] S201: Receive a mount request sent by a user terminal.

[0094] The mount request includes file system information and user information.

[0095] In an embodiment of the present application, when it is necessary to manage multiple file systems stored in a file system server, the user terminal may send a mount request to the file system server, so that the file system server receives the mount request sent by the user terminal.

[0096] S202: Authenticate the file system information according to the pre-stored key table file.

[0097] The key table file is generated based on the administrator information of the resource management platform and the corresponding file system information.

[0098] Among them, the resource management platform can be an AD domain server. AD (Active Directory) domain is a hierarchical structure developed by Microsoft for centrally managing network resources. It can provide a standardized method to create, organize and manage users, computers, services and other resources in computer networks, and provide enterprises with the ability to centrally manage user authentication, authorization and access control. The concept of AD domain is based on the Windows operating system. The management node in the AD domain is called the domain controller DC, which implements the specific management of resources in the AD domain.

[0099] The administrator information refers to the user information and password information of the administrator in the AD domain server, and the file system information refers to the file system service address information managed by the administrator in the administrator information.

[0100] In an embodiment of the present application, after obtaining the file system information in the mount request, the file system information can be authenticated based on a pre-stored key table file. Optionally, the specific authentication process may include comparing the file system information in the pre-stored key table file with the file system information in the mount request. If the file system information in the key table file and the file system information in the mount request are the same, authentication is successful; if the file system information in the key table file and the file system information in the mount request are different, authentication fails.

[0101] S203: If the authentication is successful, create a target user account associated with the user information locally, and manage the file system according to the target user account.

[0102] In the embodiment of the present application, if the above authentication is passed, an account of the target user associated with the user information can be created locally, and the file system can be managed according to the account of the target user.

[0103] The file system management method provided in the embodiment of the present application is applied to a file system server, receives a mount request sent by a user terminal, authenticates the file system information according to a pre-stored key table file, and if the authentication is successful, creates a target user account associated with the user information locally, and manages the file system according to the target user account; the mount request includes file system information and user information, and the key table file is generated according to the administrator information of the resource management platform and the corresponding file system information. In the above method, when responding to a user request, the file system server only needs to authenticate the file system information with the local key table file, and create a user account locally based on the user information, thereby realizing the management of the file system in the file system server, without the need to interact with the AD domain controller, nor the need to add the file system server to the AD domain controller, which is in line with the architectural design of the current public cloud scenario.

[0104] In one embodiment, Figure 2 Based on the embodiment shown, Figure 3 As shown, the above method also includes:

[0105] S204: Receive the key table file sent by the user terminal, and store the key table file locally.

[0106] In an embodiment of the present application, before the user terminal sends a mount request to the file system server, the user terminal may also first send a key table file to the file system server, so that the file system server receives and stores the key table file sent by the user terminal, so as to subsequently authenticate the file system information based on the key table file.

[0107] Optionally, the following provides a method for storing the key table file locally, see Figure 4 The above S204 "receiving the key table file sent by the user terminal and storing the key table file locally" includes:

[0108] S301. Verify the key table file to obtain a verification result. If the verification result indicates that the verification is passed, execute the following S302. If the verification result indicates that the verification is not passed, return to the step of verifying the key table file to obtain a verification result.

[0109] In the embodiment of the present application, after the key table file is obtained as described above, the key table file can be verified based on the file identifier corresponding to the key table file to obtain a verification result indicating that the key table file has passed verification or a verification result indicating that the key table file has failed verification. It should be noted that one key table file corresponds to one file identifier.

[0110] Optionally, a specific implementation method for verifying the key table file is also provided, see Figure 5 The above S301 "verify the key table file to obtain a verification result" includes:

[0111] S401: Generate first verification information based on a key table file, and encode the key table file to obtain an encoded key table file.

[0112] In the embodiment of the present application, after the key table file is obtained as described above, the data in the key table file can be calculated and processed to obtain the first verification information, and the key table file can be string encoded to obtain the encoded key table file.

[0113] Optionally, the user terminal can first upload the key table file to the public cloud front-end page console of the file system server. The public cloud front-end page console first checks the validity of the key table file and calculates the first verification information of the key table file. Then, the key table file is encoded into a string to obtain the encoded key table file. By calling the interface provided by the file server, the encoded key table file and the first verification information are transmitted to the file server.

[0114] S402: Decode the encoded key table file to obtain a decoded key table file, and generate second verification information based on the decoded key table file.

[0115] In an embodiment of the present application, after the file system server receives the encoded key table file and the first verification information, it can decode the encoded key table file to obtain a decoded key table file, and calculate the second verification information of the decoded key table file.

[0116] S403: Perform verification processing on the first verification information and the second verification information to obtain a verification processing result.

[0117] The verification processing results include verification success and verification failure.

[0118] In an embodiment of the present application, after the first verification information and the second verification information are obtained as described above, the first verification information and the second verification information can be compared. If the first verification information and the second verification information are consistent, it indicates that the verification is successful. If the first verification information and the second verification information are inconsistent, it indicates that the verification is successful.

[0119] So far, a method for obtaining verification processing results is provided.

[0120] S302: Store the key table file locally.

[0121] In the embodiment of the present application, if the verification processing result indicates that the verification is passed, the key table file is stored locally.

[0122] The file system management method provided in the embodiment of the present application verifies the key table file and, based on the verification result, determines whether to store the key table file locally, thereby providing an accurate data basis for subsequent authentication based on the key table file.

[0123] In one embodiment, Figure 3 Based on the embodiment shown, Figure 6 As shown, the above method also includes:

[0124] S205: Merge the key table file and other key table files to remove duplicates and obtain a target key table file.

[0125] Among them, other key table files are generated according to other manager information of the resource management platform and corresponding file system information.

[0126] In an embodiment of the present application, after the file system server simultaneously receives the key table file and other key table files, the key table file and other key table files may be merged and deduplicated to obtain a target key table file.

[0127] S206. Store the target key table file locally.

[0128] In the embodiment of the present application, after the target key table file is determined as described above, the target key table file can be stored locally.

[0129] The method for merging and deduplicating key table files provided in the embodiments of the present application can avoid duplication of key table files, thereby reducing the space occupied by key table files.

[0130] In one embodiment, Figure 7 As shown, a file system management method is provided, which is applied to Figure 1 The following steps are used as an example to illustrate the user end in FIG.

[0131] S501: Receive a key table file sent by a resource management platform.

[0132] The key table file is generated based on the administrator information of the resource management platform and the corresponding file system address information.

[0133] In an embodiment of the present application, after the resource management platform generates the key table file, the key table file may be sent to the user terminal so that the user terminal receives the key table file sent by the resource management platform.

[0134] S502: Send the key table file to the file system server.

[0135] In the embodiment of the present application, after receiving the key table file sent by the resource management platform, the key table file can be sent to the file system server.

[0136] S503. Send a mount request to the file system server, so that the file system server authenticates the file system information in the mount request according to the key table file, and if the authentication is successful, creates a target user locally according to the user information in the mount request to manage the file system based on the target user.

[0137] In an embodiment of the present application, after the key table file is sent to the file system server as mentioned above, a mount request can be sent to the file system server at any time, so that the file system server can authenticate the file system information in the mount request based on the key table file, and if the authentication is successful, create a target user locally based on the user information in the mount request to manage the file system based on the target user.

[0138] The file system management method provided in the embodiment of the present application is that, when responding to a user request, the file system server only needs to authenticate the file system information with the local key table file and create a user account locally based on the user information to manage the file system in the file system server. There is no need to interact with the AD domain controller, nor is there any need to add the file system server to the AD domain controller, which is in line with the architectural design of the current public cloud scenario.

[0139] In one embodiment, Figure 8 As shown, a file system management method is provided, which is applied to Figure 1 The resource management platform in the example is used to illustrate the process, which includes the following steps:

[0140] S601: Generate a key table file according to the manager information and the file system information corresponding to the manager information.

[0141] In this embodiment of the present application, a service account can be pre-registered for the file system's domain name on the AD domain controller. This service account is added to the AD domain controller as the file system service code. This service account is used to create a service principal (SPN) for the file system. Using a tool such as ktpass, a Kerberos key table file is created for the file system's SPN on the AD domain based on the administrator information and the file system information corresponding to the administrator information.

[0142] S602: Send the key table file to the user terminal.

[0143] In the embodiment of the present application, after the key table file is obtained as described above, the key table file can be sent to the user end.

[0144] Optionally, this application uses a customized Samba as a CIFS file service on a public cloud file system server. This Samba service is capable of using Kerberos as the authentication protocol. The server provides file system mount points to users using the \\[ip]\[share_path] format. Each file system server provides multiple file system shares. The file system root directory is configured with non-recursive permissions to ensure that users have sufficient permissions for read and write operations after mounting.

[0145] Optionally, the file system server uses Kerberos as the network authorization protocol to authenticate client requests. The Kerberos service does not contain any information related to the specific AD domain, and does not register the IP address or domain name of the AD domain server. The Kerberos service is configured to use a key table for authentication, verifying the legitimacy of the user's identity by comparing the service principal SPN in the key table.

[0146] Optionally, use Windows as an AD domain controller to manage domain user information, such as usernames and passwords. Configure local domain name mapping for the file system on the AD domain controller. Map the original file system mount point to an Internet domain name by setting the mount point IP to domain name mapping in the local hosts file.

[0147] The file system management method provided in the embodiment of the present application is that, when responding to a user request, the file system server only needs to authenticate the file system information with the local key table file and create a user account locally based on the user information to manage the file system in the file system server. There is no need to interact with the AD domain controller, nor is there any need to add the file system server to the AD domain controller, which is in line with the architectural design of the current public cloud scenario.

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

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

[0150] In an exemplary embodiment, Figure 9 As shown, a file system management device is provided, comprising: a receiving module 10, an authentication module 11 and a management module 12, wherein:

[0151] The receiving module 10 is configured to receive a mount request sent by a user terminal; the mount request includes file system information and user information.

[0152] The authentication module 11 is used to authenticate the file system information according to a pre-stored key table file; the key table file is generated according to the administrator information of the resource management platform and the corresponding file system information.

[0153] The management module 12 is used to create a target user account associated with the user information locally when the authentication is passed, and manage the file system according to the target user account.

[0154] In an exemplary embodiment, the apparatus further includes: a storage module configured to receive a key table file sent by a user terminal and store the key table file locally.

[0155] In an exemplary embodiment, the storage module includes: a first processing unit, a storage unit, and a second processing unit, wherein:

[0156] The first processing unit is specifically configured to perform verification processing on the key table file to obtain a verification processing result;

[0157] a storage unit, specifically configured to store the key table file locally when the verification processing result indicates that the verification has passed;

[0158] The second processing unit is specifically configured to return to the step of performing verification processing on the key table file to obtain a verification processing result when the verification processing result indicates that the verification fails.

[0159] In an exemplary embodiment, the above-mentioned first processing unit is specifically used to generate first verification information based on the key table file, and encode the key table file to obtain an encoded key table file; decode the encoded key table file to obtain a decoded key table file, and generate second verification information based on the decoded key table file; verify the first verification information and the second verification information to obtain a verification processing result.

[0160] In an exemplary embodiment, the file system management device further includes: a processing module and a storage module, wherein:

[0161] A processing module is used to merge and remove duplicates from the key table file and other key table files to obtain a target key table file; other key table files are generated based on other administrator information of the resource management platform and corresponding file system information;

[0162] The storage module is used to store the target key table file locally.

[0163] In an exemplary embodiment, a file system management device is provided, comprising: a receiving module, a first sending module, and a second sending module, wherein:

[0164] The receiving module is used to receive the key table file sent by the resource management platform; the key table file is generated according to the administrator information of the resource management platform and the corresponding file system address information;

[0165] A first sending module, configured to send the key table file to a file system server;

[0166] The second sending module is used to send a mount request to the file system server, so that the file system server authenticates the file system information in the mount request according to the key table file, and if the authentication is successful, creates a target user locally according to the user information in the mount request to manage the file system based on the target user.

[0167] In an exemplary embodiment, a file system management device is provided, comprising: a generating module and a sending module, wherein:

[0168] A generation module, configured to generate a key table file based on the manager information and the file system information corresponding to the manager information;

[0169] The sending module is used to send the key table file to the user end.

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

[0171] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 10 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O) and a communication interface. The processor, memory and input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store file system data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a file system management method is implemented.

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

[0173] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0174] Receive the mount request sent by the user; the mount request includes file system information and user information;

[0175] Authenticate the file system information based on the pre-stored key table file; the key table file is generated based on the administrator information of the resource management platform and the corresponding file system information;

[0176] If the authentication is successful, a target user account associated with the user information is created locally, and the file system is managed based on the target user account.

[0177] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0178] Receive the key table file sent by the client and store the key table file locally.

[0179] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0180] Perform verification processing on the key table file to obtain the verification processing result;

[0181] If the verification result indicates that the verification is passed, the key table file is stored locally;

[0182] If the verification result indicates that the verification fails, the process returns to the step of performing verification on the key table file to obtain the verification result.

[0183] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0184] Generate first verification information based on the key table file, and encode the key table file to obtain an encoded key table file;

[0185] Decoding the encoded key table file to obtain a decoded key table file, and generating second verification information based on the decoded key table file;

[0186] Verification processing is performed on the first verification information and the second verification information to obtain a verification processing result.

[0187] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0188] Merge the key table file with other key table files and perform deduplication processing to obtain the target key table file; other key table files are generated based on other administrator information of the resource management platform and the corresponding file system information;

[0189] Store the target key table file locally.

[0190] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0191] Receive the key table file sent by the resource management platform; the key table file is generated based on the administrator information of the resource management platform and the corresponding file system address information;

[0192] Send the key table file to the file system server;

[0193] Send a mount request to the file system server so that the file system server authenticates the file system information in the mount request based on the key table file. If the authentication is successful, the server creates a target user locally based on the user information in the mount request to manage the file system based on the target user.

[0194] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0195] Generate a key table file based on the manager information and the file system information corresponding to the manager information;

[0196] Send the key table file to the user.

[0197] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0198] Receive the mount request sent by the user; the mount request includes file system information and user information;

[0199] Authenticate the file system information based on the pre-stored key table file; the key table file is generated based on the administrator information of the resource management platform and the corresponding file system information;

[0200] If the authentication is successful, a target user account associated with the user information is created locally, and the file system is managed based on the target user account.

[0201] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0202] Receive the key table file sent by the client and store the key table file locally.

[0203] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0204] Perform verification processing on the key table file to obtain the verification processing result;

[0205] If the verification result indicates that the verification is passed, the key table file is stored locally;

[0206] If the verification result indicates that the verification fails, the process returns to the step of performing verification on the key table file to obtain the verification result.

[0207] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0208] Generate first verification information based on the key table file, and encode the key table file to obtain an encoded key table file;

[0209] Decoding the encoded key table file to obtain a decoded key table file, and generating second verification information based on the decoded key table file;

[0210] Verification processing is performed on the first verification information and the second verification information to obtain a verification processing result.

[0211] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0212] Merge the key table file with other key table files and perform deduplication processing to obtain the target key table file; other key table files are generated based on other administrator information of the resource management platform and the corresponding file system information;

[0213] Store the target key table file locally.

[0214] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0215] Receive the key table file sent by the resource management platform; the key table file is generated based on the administrator information of the resource management platform and the corresponding file system address information;

[0216] Send the key table file to the file system server;

[0217] Send a mount request to the file system server so that the file system server authenticates the file system information in the mount request based on the key table file. If the authentication is successful, the server creates a target user locally based on the user information in the mount request to manage the file system based on the target user.

[0218] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0219] Generate a key table file based on the manager information and the file system information corresponding to the manager information;

[0220] Send the key table file to the user.

[0221] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0222] Receive the mount request sent by the user; the mount request includes file system information and user information;

[0223] Authenticate the file system information based on the pre-stored key table file; the key table file is generated based on the administrator information of the resource management platform and the corresponding file system information;

[0224] If the authentication is successful, a target user account associated with the user information is created locally, and the file system is managed based on the target user account.

[0225] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0226] Receive the key table file sent by the client and store the key table file locally.

[0227] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0228] Perform verification processing on the key table file to obtain the verification processing result;

[0229] If the verification result indicates that the verification is passed, the key table file is stored locally;

[0230] If the verification result indicates that the verification fails, the process returns to the step of performing verification on the key table file to obtain the verification result.

[0231] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0232] Generate first verification information based on the key table file, and encode the key table file to obtain an encoded key table file;

[0233] Decoding the encoded key table file to obtain a decoded key table file, and generating second verification information based on the decoded key table file;

[0234] Verification processing is performed on the first verification information and the second verification information to obtain a verification processing result.

[0235] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0236] Merge the key table file with other key table files and perform deduplication processing to obtain the target key table file; other key table files are generated based on other administrator information of the resource management platform and the corresponding file system information;

[0237] Store the target key table file locally.

[0238] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0239] Receive the key table file sent by the resource management platform; the key table file is generated based on the administrator information of the resource management platform and the corresponding file system address information;

[0240] Send the key table file to the file system server;

[0241] Send a mount request to the file system server so that the file system server authenticates the file system information in the mount request based on the key table file. If the authentication is successful, the server creates a target user locally based on the user information in the mount request to manage the file system based on the target user.

[0242] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0243] Generate a key table file based on the manager information and the file system information corresponding to the manager information;

[0244] Send the key table file to the user.

[0245] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

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

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

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

Claims

1. A method for managing a file system, characterized in that: Applied to a file system server, the method includes: Receive a mount request sent by a user terminal; the mount request includes file system information and user information; Authenticating the file system information according to a pre-stored key table file; the key table file is generated by a resource management platform based on administrator information of the resource management platform and corresponding file system information, and is sent to the file system server via a user terminal; the resource management platform is an AD domain server; the administrator information is user information and password information of an administrator in the AD domain server; the file system information is the address information of the file system service managed by the administrator in the administrator information; If the authentication is successful, an account of the target user associated with the user information is created locally, and the file system is managed according to the account of the target user.

2. The method according to claim 1, characterized in that The method further comprises: Receive the key table file sent by the user terminal, and store the key table file locally.

3. The method according to claim 2, characterized in that The receiving the key table file sent by the user terminal and storing the key table file locally includes: Performing verification processing on the key table file to obtain a verification processing result; If the verification result indicates that the verification is passed, the key table file is stored locally; If the verification result indicates that the verification fails, the process returns to the step of performing verification on the key table file to obtain a verification result.

4. The method according to claim 3, characterized in that The verifying the key table file to obtain a verification result includes: generating first verification information based on the key table file, and encoding the key table file to obtain an encoded key table file; Decoding the encoded key table file to obtain a decoded key table file, and generating second verification information based on the decoded key table file; Verification processing is performed on the first verification information and the second verification information to obtain the verification processing result.

5. The method according to claim 2, characterized in that The method further comprises: Merging the key table file and other key table files for deduplication to obtain a target key table file; the other key table files are generated based on other administrator information of the resource management platform and corresponding file system information; The target key table file is stored locally.

6. A method for managing a file system, characterized in that: Applied to a user terminal, the method includes: Receive a key table file sent by a resource management platform; the key table file is generated by the resource management platform based on the administrator information of the resource management platform and the corresponding file system address information; the resource management platform is an AD domain server; the administrator information is user information and password information of an administrator in the AD domain server; the file system information is the file system service address information managed by the administrator in the administrator information; Sending the key table file to a file system server; A mount request is sent to the file system server, so that the file system server authenticates the file system information in the mount request according to the key table file, and if the authentication is successful, creates a target user locally according to the user information in the mount request, so as to manage the file system based on the target user.

7. A method for managing a file system, characterized in that: Applied to a resource management platform, the method includes: Generate a key table file based on the administrator information and the file system information corresponding to the administrator information; the resource management platform refers to the AD domain server; the administrator information refers to the user information and password information of the administrator in the AD domain server; the file system information refers to the file system service address information managed by the administrator in the administrator information; The key table file is sent to the user terminal, so that the user terminal sends the key table file and the mount request to the file system server, so that the file system server authenticates the file system information in the mount request according to the key table file, and if the authentication is successful, creates a target user locally according to the user information in the mount request, so as to manage the file system based on the target user; the mount request includes the file system information and the user information.

8. A file system management device, characterized in that: Applied to a file system server, the device includes: A receiving module, configured to receive a mount request sent by a user terminal; the mount request includes file system information and user information; an authentication module configured to authenticate the file system information based on a pre-stored key table file; the key table file is generated by a resource management platform based on administrator information of the resource management platform and corresponding file system information, and is sent to the file system server via a user terminal; the resource management platform is an AD domain server; the administrator information is user information and password information of an administrator in the AD domain server; and the file system information is the address information of the file system service managed by the administrator in the administrator information; The management module is used to create a target user account associated with the user information locally when the authentication is passed, and manage the file system according to the target user account.

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

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

Images