A method, system, and medium for changing user permissions with immediate effect

Abstract

This invention discloses a method, system, and medium for instantly changing user permissions. The method includes the following steps: obtaining user information and constructing a user permission configuration file based on the user information; performing a file loading operation on the user permission configuration file; performing a permission pre-update operation based on the file loading result; performing a permission verification operation on the result of the permission pre-update operation to obtain a verification result; performing a permission update operation based on the verification result to obtain updated permissions; performing a permission change information push operation based on the updated permissions; and performing a permission change operation based on the result of the permission change information push operation. Through the above method, this invention can achieve unified management of user permissions for various business platforms in a business system, improving work efficiency; after detecting a permission change, the permission management server instantly pushes the permission change message, enabling each business platform to obtain the latest permission information instantly, improving permission update efficiency.

Description

Technical Field

[0001] This invention relates to the field of permission setting technology, and in particular to a method, system, and medium for changing user permissions to take effect immediately. Background Technology

[0002] Access control generally refers to a method of dividing the functions of users accessing the system according to the security rules or security policies set by the system. Different users can perform different operations in the system according to their own permissions.

[0003] Existing systems typically integrate multiple business platforms, dealing with multiple user groups and multiple users across these platforms. Given the confidentiality and competitive relationships among these platforms, access control for multiple users is particularly important.

[0004] The existing permission management settings are rather fragmented, with each business platform having its own permission management strategies and methods, making it impossible to manage permissions uniformly. Furthermore, due to the independence of permission management between different business platforms, timely synchronization is not possible after permission changes occur, affecting efficiency. Summary of the Invention

[0005] The present invention mainly addresses the problems of existing permission management being fragmented, unable to be managed uniformly, and unable to take effect immediately after permission changes.

[0006] To address the above problems, one technical solution adopted by the present invention is to provide a method for changing user permissions to take effect immediately, comprising the following steps: Permission file management: Obtain user information, construct a user permission configuration file based on the user information; perform a file loading operation on the user permission configuration file; Access control: Based on the result of the file loading operation, perform a permission pre-update operation; perform a permission verification operation on the result of the permission pre-update operation to obtain a verification result; and perform a permission update operation based on the verification result to obtain updated permissions. Permission change push: Based on the updated permissions, perform a permission change information push operation; based on the result of the permission change information push operation, perform a permission change operation.

[0007] Furthermore, the steps of the permission file management further include: Build the permission file: Obtain the user information whose permissions are to be changed, and build the user permission configuration file through a text document based on the user information; Load permission file: Perform the file loading operation on the user permission configuration file to obtain permission file cache information.

[0008] Furthermore, the permission management steps further include: Permission pre-update: Based on the permission file cache information, perform the permission pre-update operation on the permission management server to obtain pre-updated permissions; Permission verification: Based on the pre-updated permissions and the user permission configuration file, the permission verification operation is performed through the test server to obtain the verification result; Permission update: Based on the verification result, perform the permission update operation on the permission management server to obtain the updated permissions.

[0009] Furthermore, the permission pre-update step further includes: A permission pre-update file is constructed at the permission pre-update location of the permission management server. The permission file cache information is sent to the permission pre-update location of the permission management server, and the permission file cache information is written into the permission pre-update file to obtain the pre-update permission. The pre-update test permission of the permission management server is then enabled.

[0010] Furthermore, the verification result includes a first verification result and a second verification result; the permission verification steps further include: Configure the pre-update test permissions on the test server; verify the pre-update permissions through the test server according to the user permission configuration file: If the pre-updated permission is the same as the permission configured in the user permission configuration file, then the verification result is set to the first verification result; If the pre-updated permissions are different from the permissions configured in the user permission configuration file, then the verification result is set to the second verification result, and the first difference is recorded.

[0011] Furthermore, the permission update step further includes: If the verification result is the first verification result, then the first change time of the permission information of the permission update location of the permission management server is recorded, and the pre-update permission of the permission pre-update location is copied to the permission update location of the permission management server to obtain the update permission; If the verification result is the second verification result, then the first different item is obtained, and the pre-updated permission is changed according to the user permission configuration file before proceeding to the permission verification step.

[0012] Furthermore, the step of performing the permission change information push operation based on the updated permissions further includes: Obtain the second change time for the update permission, and compare the second change time with the first change time: If the second change time is later than the first change time, then the permission change information is sent to the application server through the permission management server; If the second change time is the same as the first change time, then no permission update is required; If the second change time is earlier than the first change time, an alarm is triggered, and the file content of the pre-updated permission is compared with that of the user permission configuration file. If the file content of the pre-updated permission is the same as that of the user permission configuration file, the pre-updated permission is copied to the permission update location on the permission management server, and the permission change push step is initiated. If the file content of the pre-updated permission is different from that of the user permission configuration file, the second difference between the pre-updated permission and the user permission configuration file is obtained, and the pre-updated permission is modified according to the second difference to obtain the modified pre-updated permission, and the permission verification step is initiated.

[0013] Furthermore, the step of performing the permission change operation based on the result of the permission change information push operation further includes: Upon obtaining the permission change information, the permission information of the application server is deleted, and a permission acquisition request is sent to the permission management server; based on the permission acquisition request, the update permission cache information of the updated permission is obtained and sent; the update permission cache information is obtained and saved to the application server.

[0014] A system that allows changes to user permissions to take effect immediately includes: a permission file management module, a permission management module, and a permission change push module; The permission file management module is used to obtain user information, construct a user permission configuration file based on the user information, and perform a file loading operation on the user permission configuration file. The permission management module is used to perform a permission pre-update operation based on the result of the file loading operation; perform a permission verification operation on the result of the permission pre-update operation to obtain a verification result; and perform a permission update operation based on the verification result to obtain updated permissions. The permission change push module is used to perform a permission change information push operation based on the updated permissions; and to perform a permission change operation based on the result of the permission change information push operation. The permission file management module includes a permission file building unit and a permission file loading unit; The permission file building unit is used to obtain the user information of the permissions to be changed, and build the user permission configuration file through a text document based on the user information; The permission file loading unit is used to perform the file loading operation on the user permission configuration file to obtain permission file cache information; The permission management module includes a permission pre-update unit, a permission verification unit, and a permission update unit; The permission pre-update unit is used to perform the permission pre-update operation on the permission management server according to the permission file cache information to obtain pre-updated permissions; The permission verification unit is used to perform the permission verification operation through the test server according to the pre-updated permissions and the user permission configuration file to obtain the verification result; The permission update unit is used to perform the permission update operation on the permission management server according to the verification result, so as to obtain the updated permission.

[0015] The present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the method for making changes to user permissions take effect immediately.

[0016] The beneficial effects of this invention are: 1. The method for changing user permissions to take effect immediately as described in this invention can realize unified management of user permissions in the same business system through a permission management server, which facilitates permission maintenance personnel to change and maintain permissions and improves work efficiency. 2. The system described in this invention, which allows for immediate changes to user permissions, enables convenient and quick modifications to user permissions within the system via user permission configuration files. Furthermore, upon detecting a permission change, it instantly pushes permission change messages to various business platforms, allowing each platform to immediately obtain the latest permissions and improving the efficiency of user permission changes. 3. The medium for immediate effect of user permission changes described in this invention can simulate the environment of various business platforms through a test server when permissions are changed, and verify the validity of permissions to ensure the correctness of permission settings. Attached Figure Description

[0017] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0018] Figure 1 This is a flowchart of a method for changing user permissions to take effect immediately, as described in Embodiment 1 of the present invention; Figure 2 This is a flowchart of the permission file management steps in a method for changing user permissions to take effect immediately, as described in Embodiment 1 of the present invention. Figure 3 This is a flowchart of the permission management steps in a method for changing user permissions to take effect immediately, as described in Embodiment 1 of the present invention. Figure 4 This is a schematic diagram of a system for instantly changing user permissions as described in Embodiment 2 of the present invention; Figure 5 This is a schematic diagram of the permission file management module of a system that allows changes to user permissions to take effect immediately, as described in Embodiment 2 of the present invention. Figure 6 This is a schematic diagram of the permission management module of a system that allows changes to user permissions to take effect immediately, as described in Embodiment 2 of the present invention. Detailed Implementation

[0019] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. 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.

[0020] In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, terms such as "user information," "user permission configuration file," "file loading," "permission pre-update," "verification result," "update permission," "permission change information push," "permission change," "permission file cache information," "pre-update permission," "permission management server," "permission pre-update location," "pre-update test permission," "first verification result," "second verification result," "permission change information," "permission cache information," "update permission cache information," and "quasi-business platform environment" should be interpreted broadly. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0021] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined with "first" or "second" may explicitly or implicitly include at least one of that feature.

[0022] Example 1 This invention provides a method for changing user permissions to take effect immediately. Please refer to [link / reference]. Figures 1 to 3 This includes the following steps: S100, Permission File Management: S101. Construct the permissions file: Obtain all user information that needs to have its permissions changed, and build a user permission configuration file using a text document based on the user information; the user information can be that of a single user or a group of users.

[0023] To explain this invention more clearly, examples are given here. When the user information is a single user information, it generally includes user ID, user name, user role, user level, etc.; when the user information is user group information, it generally includes user group name, user group number, user group member information, etc.; corresponding permissions are set according to the user role, user level, user group number, user group name, etc. in the user information, and the corresponding permissions are written into a text document to obtain the user permission configuration file.

[0024] S102. Load the permissions file: Loading the user permission configuration file involves reading it through a system function or component, storing it in a cache, and obtaining the cached permission file information. This system function or component can be a user-developed system or an existing system; for example, a cache of the user permission configuration file can be built using the ConcurrentHashMap() method.

[0025] S200, Access Control: S201, Permission Pre-Update: A permission pre-update file is built in the permission pre-update location of the permission management server. The permission file cache information is sent to the permission pre-update location of the permission management server. The software reads the permission file cache information and writes it into the permission pre-update file to obtain the pre-update permissions. At the same time, the pre-update test permission of the permission management server needs to be enabled so that the test server can test the pre-update permissions.

[0026] The permission management server has two file locations: the permission pre-update location and the permission update location. The permission pre-update location is used to store permission pre-update information, and the permission update location is used to store the verified permission update information. The permission update information in the permission update location will only be updated after the permission pre-update information in the permission pre-update location has been verified.

[0027] S202, Permission Verification: Configure the test server as a quasi-business platform environment, that is, a complete simulation of the business platform environment, and configure pre-update test permissions for the test server; manage the server through the test server's access permissions, test the pre-update permissions, and compare the test results with the user permission configuration file: If the test result is the same as the permission set in the user permission configuration file, then the verification result is set as the first verification result, that is, the pre-update permission test passes; If at least one of the test results differs from the permissions set in the user permission configuration file, the verification result is set as the second verification result, meaning the pre-update permission test failed, and the first difference is recorded, namely the difference between the pre-update permission and the user permission configuration file.

[0028] To explain the invention more clearly, an example is given here. Suppose that the approval permission of the automated office platform for user number 00231 is set to unavailable in the pre-update permissions, while the approval permission for the automated office platform for user 00231 is available in the user permission configuration file. Then, this difference needs to be recorded.

[0029] S203, Permission Update: Obtain the verification result and evaluate it: If the verification result is the first verification result, that is, the pre-update permission test passes, then record the first change time of the permission information at the permission update location of the permission management server. The first change time is also the last change time of the permission information. Copy the pre-update permissions at the permission pre-update location to the permission update location in the permission management server, overwriting the original permission information there, and obtain the updated permissions. If the verification result is the second verification result, that is, the pre-update permission test fails, then the first difference item is obtained, and the pre-update permissions are modified according to the first difference item and the user permission configuration file. After the modification is completed, the process re-enters the S102 step of loading the permission file.

[0030] S300, Permission Change Push: The second modification time for obtaining update permissions, which is also the last modification time for obtaining update permissions, is compared with the first and second modification times: If the second change time is later than the first change time, it means that the permission information in the permission management server has changed, and the updated permission is the last permission file. In this case, the permission management server promptly pushes the permission change information to each application server. After receiving the permission change information, each application server deletes the permission information cached locally in the application server and initiates a permission acquisition request to the permission management server. Based on the permission acquisition request, the application server retrieves the updated permission cache information through the cache information reading software and sends the updated permission cache information to each application server. Each application server receives the updated permission cache information and saves it to the permission storage location in the application server, completing the permission update and making the permission change take effect immediately. When an application server needs to acquire permission, it directly reads the updated permission cache information from the corresponding local location. The aforementioned cache information reading software can be user-developed software or commercially available software.

[0031] If the second modification time is the same as the first modification time, it means that the permission information in the permission management server has not changed, and there is no need to update the permissions. If the second change time is earlier than the first change time, it indicates a problem with the update permission settings. This is because update permissions are copied to the permission update location on the permission management server after the permission information is in the permission management server. Therefore, if the last change time of the update permission is earlier than the last change time of the permission information, the permission configuration file for the update permission may be faulty. An alarm should be triggered to remind staff to check the permission configuration file. The file content of the pre-updated permission is compared with the user permission configuration file. If the file content of the pre-updated permission is the same as the user permission configuration file, the pre-updated permission is copied back to the permission update location on the permission management server, and the S300 permission change push step is restarted. If the file content of the pre-updated permission is different from the user permission configuration file, the second difference between the pre-updated permission and the user permission configuration file is obtained. Based on the second difference, the pre-updated permission is modified to obtain the changed update permission, and the S202 permission verification step is restarted for verification and update.

[0032] To explain the invention more clearly, an example is given here. Listening threads or listening channels are set up in each application server to listen to the permission management server. When a message indicating a change in permission information is received from the permission server, the application server is notified to initiate a permission update operation, which involves sending a request to the permission management server to obtain the latest permission information. At the same time, the application server deletes the permission information cached locally and updates the permission information to the latest version.

[0033] It should be noted that the above examples are only for the purpose of more clearly explaining the execution process of the present invention, and should not be construed as limiting the scope of protection of the present invention.

[0034] Example 2 This invention also provides a system where changes to user permissions take effect immediately. Please refer to [link / reference]. Figures 4 to 6 It includes: a permission file management module, a permission management module, and a permission change push module; Permission file management module: The permission file management module is used to obtain user information, construct user permission configuration files based on the user information, and perform file loading operations on the user permission configuration files. The permission file management module includes a permission file construction unit and a permission file loading unit. Building the permission file unit: The permission file construction unit is used to obtain the user information of the permissions to be changed, and to construct the user permission configuration file through a text document based on the user information; Specifically, the permission file construction unit obtains all user information that needs to be changed in terms of permissions, and constructs user permission configuration files through a text document based on the user information; where user information can be information about a single user or information about a user group.

[0035] To explain this invention more clearly, examples are given here. When the user information is a single user information, it generally includes user ID, user name, user role, user level, etc.; when the user information is user group information, it generally includes user group name, user group number, user group member information, etc.; corresponding permissions are set according to the user role, user level, user group number, user group name, etc. in the user information, and the corresponding permissions are written into a text document to obtain the user permission configuration file.

[0036] Load permission file unit: The "Load Permission File" unit is used to perform a file loading operation on the user permission configuration file to obtain permission file cache information. Specifically, the permission file loading unit loads the user permission configuration file, that is, it reads the user permission configuration file through a function or component in the system, reads the user permission configuration file into the cache, and obtains the permission file cache information. The function or component in the system here can be a user-developed system, or it can use an existing system. For example, the cache of the user permission configuration file can be built using the ConcurrentHashMap() method.

[0037] Access control module: The permission management module is used to perform a permission pre-update operation based on the file loading result; perform a permission verification operation on the result of the permission pre-update operation to obtain the verification result; and perform a permission update operation based on the verification result to obtain the updated permissions. The permission management module includes a permission pre-update unit, a permission verification unit, and a permission update unit. Permission pre-update unit: The permission pre-update unit is used to perform a permission pre-update operation on the permission management server based on the permission file cache information to obtain pre-updated permissions; Specifically, the permission pre-update unit constructs a permission pre-update file at the permission pre-update location of the permission management server, sends the permission file cache information to the permission pre-update location of the permission management server, reads the permission file cache information through software, and writes the permission file cache information into the permission pre-update file to obtain the pre-update permissions. At the same time, the pre-update test permission of the permission management server needs to be enabled so that the test server can test the pre-update permissions.

[0038] The permission management server has two file locations: the permission pre-update location and the permission update location. The permission pre-update location is used to store permission pre-update information, and the permission update location is used to store the verified permission update information. The permission update information in the permission update location will only be updated after the permission pre-update information in the permission pre-update location has been verified.

[0039] Permission verification unit: The permission verification unit is used to perform permission verification operations through the test server based on the pre-updated permissions and user permission configuration files, and obtain the verification results; Specifically, the permission verification unit sets the test server to a quasi-business platform environment, that is, a complete simulation of the business platform environment, and configures pre-update test permissions for the test server; it tests the pre-update permissions through the test server's access permission management server, and compares the test results with the user permission configuration file: If the test result is the same as the permission set in the user permission configuration file, then the verification result is set as the first verification result, that is, the pre-update permission test passes; If at least one of the test results differs from the permissions set in the user permission configuration file, the verification result is set as the second verification result, meaning the pre-update permission test failed, and the first difference is recorded, namely the difference between the pre-update permission and the user permission configuration file.

[0040] To explain the invention more clearly, an example is given here. Suppose that the approval permission of the automated office platform for user number 00231 is set to unavailable in the pre-update permissions, while the approval permission for the automated office platform for user 00231 is available in the user permission configuration file. Then, this difference needs to be recorded.

[0041] Permission update unit: The permission update unit is used to perform permission update operations on the permission management server based on the verification results, and obtain updated permissions; Specifically, the permission update unit obtains the verification result and makes a judgment on the verification result: If the verification result is the first verification result, that is, the pre-update permission test passes, then record the first change time of the permission information at the permission update location of the permission management server. The first change time is also the last change time of the permission information. Copy the pre-update permissions at the permission pre-update location to the permission update location in the permission management server, overwriting the original permission information there, and obtain the updated permissions. If the verification result is the second verification result, that is, the pre-update permission test fails, then the first difference item is obtained, and the pre-update permissions are modified according to the first difference item and the user permission configuration file. After the modification is completed, the process re-enters the S102 step of loading the permission file.

[0042] Permission change push module: The permission change push module is used to push permission change information based on updated permissions; and to perform permission change operations based on the result of the permission change information push operation. Specifically, the permission change push module obtains the second change time of the updated permission, which is also the last change time of the updated permission, and compares the first change time with the second change time: If the second change time is later than the first change time, it means that the permission information in the permission management server has changed, and the updated permission is the last permission file. In this case, the permission management server promptly pushes the permission change information to each application server. After receiving the permission change information, each application server deletes the permission information cached locally in the application server and initiates a permission acquisition request to the permission management server. Based on the permission acquisition request, the application server retrieves the updated permission cache information through the cache information reading software and sends the updated permission cache information to each application server. Each application server receives the updated permission cache information and saves it to the permission storage location in the application server, completing the permission update and making the permission change take effect immediately. When an application server needs to acquire permission, it directly reads the updated permission cache information from the corresponding local location. The aforementioned cache information reading software can be user-developed software or commercially available software.

[0043] If the second modification time is the same as the first modification time, it means that the permission information in the permission management server has not changed, and there is no need to update the permissions. If the second change time is earlier than the first change time, it indicates a problem with the update permission settings. This is because update permissions are copied to the permission update location on the permission management server after the permission information is in the permission management server. Therefore, if the last change time of the update permission is earlier than the last change time of the permission information, the permission configuration file for the update permission may be faulty. An alarm should be triggered to remind staff to check the permission configuration file. The file content of the pre-updated permission is compared with the user permission configuration file. If the file content of the pre-updated permission is the same as the user permission configuration file, the pre-updated permission is copied back to the permission update location on the permission management server, and the S300 permission change push step is restarted. If the file content of the pre-updated permission is different from the user permission configuration file, the second difference between the pre-updated permission and the user permission configuration file is obtained. Based on the second difference, the pre-updated permission is modified to obtain the changed update permission, and the S202 permission verification step is restarted for verification and update.

[0044] To explain the invention more clearly, an example is given here. Listening threads or listening channels are set up in each application server to listen to the permission management server. When a message indicating a change in permission information is received from the permission server, the application server is notified to initiate a permission update operation, which involves sending a request to the permission management server to obtain the latest permission information. At the same time, the application server deletes the permission information cached locally and updates the permission information to the latest version.

[0045] It should be noted that the above examples are only for the purpose of more clearly explaining the execution process of the present invention, and should not be construed as limiting the scope of protection of the present invention.

[0046] Example 3 This embodiment 3 includes a computer-readable storage medium for storing computer software instructions used to implement the method for immediate effect of changing user permissions as described in embodiment 1. The storage medium includes a program set for the method for immediate effect of changing user permissions. Specifically, the executable program can be built into the system for immediate effect of changing user permissions as described in embodiment 2. In this way, the system for immediate effect of changing user permissions can implement the method for immediate effect of changing user permissions as described in embodiment 1 by executing the built-in executable program.

[0047] The embodiment numbers disclosed in the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0048] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware, or by a program instructing related hardware to implement the program, which can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0049] The above description is merely an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent structural or procedural transformations made based on the content of the present invention's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A method for changing user permissions to take effect immediately, characterized in that, Includes the following steps: Permission file management: Obtain user information and build user permission configuration files based on the user information; Perform a file loading operation on the user permission configuration file; Access control: Based on the result of the file loading operation, perform a permission pre-update operation; Perform a permission verification operation on the result of the permission pre-update operation to obtain the verification result; Based on the verification result, perform a permission update operation to obtain updated permissions; Permission change push: Based on the updated permissions, perform a permission change information push operation; Based on the result of the permission change information push operation, execute the permission change operation; The steps for managing the permission file further include: Build the permission file: Obtain the user information whose permissions are to be changed, and build the user permission configuration file through a text document based on the user information; Load permission file: Perform the file loading operation on the user permission configuration file to obtain permission file cache information; The access control steps further include: Permission pre-update: Based on the permission file cache information, perform the permission pre-update operation on the permission management server to obtain pre-updated permissions; Permission verification: Based on the pre-updated permissions and the user permission configuration file, the permission verification operation is performed through the test server to obtain the verification result; Permission Update: Based on the verification result, perform the permission update operation on the permission management server to obtain the updated permission; The permission pre-update step further includes: A permission pre-update file is constructed at the permission pre-update location of the permission management server. The permission file cache information is sent to the permission pre-update location of the permission management server, and the permission file cache information is written into the permission pre-update file to obtain the pre-update permission. The pre-update test permission of the permission management server is then enabled. The verification result includes a first verification result and a second verification result; the permission verification steps further include: Configure the pre-update test permissions on the test server; verify the pre-update permissions through the test server according to the user permission configuration file: If the pre-updated permission is the same as the permission configured in the user permission configuration file, then the verification result is set to the first verification result; If the pre-updated permissions are different from the permissions configured in the user permission configuration file, then the verification result is set to the second verification result, and the first difference is recorded. The first difference is the difference between the pre-updated permissions and the user permission configuration file.

2. The method for changing user permissions to take effect immediately according to claim 1, characterized in that: The permission update step further includes: If the verification result is the first verification result, then the first change time of the permission information of the permission update location of the permission management server is recorded, and the pre-update permission of the permission pre-update location is copied to the permission update location of the permission management server to obtain the update permission; If the verification result is the second verification result, then the first different item is obtained, and the pre-updated permission is changed according to the user permission configuration file before proceeding to the permission verification step.

3. The method for changing user permissions to take effect immediately according to claim 2, characterized in that: The step of performing the permission change information push operation based on the updated permission further includes: Obtain the second change time for the update permission, and compare the second change time with the first change time: If the second change time is later than the first change time, then the permission change information is sent to the application server through the permission management server; If the second change time is the same as the first change time, then no permission update is required; If the second change time is earlier than the first change time, an alarm is triggered, and the file content of the pre-updated permission is compared with that of the user permission configuration file. If the file content of the pre-updated permission is the same as that of the user permission configuration file, the pre-updated permission is copied to the permission update location on the permission management server, and the permission change push step is initiated. If the file content of the pre-updated permission is different from that of the user permission configuration file, the second difference between the pre-updated permission and the user permission configuration file is obtained, and the pre-updated permission is modified according to the second difference to obtain the modified pre-updated permission, and the permission verification step is initiated. The second difference is the difference between the pre-updated permission and the user permission configuration file.

4. A method for changing user permissions to take effect immediately according to claim 3, characterized in that: The step of performing the permission change operation based on the result of the permission change information push operation further includes: Upon obtaining the permission change information, the permission information of the application server is deleted, and a permission acquisition request is sent to the permission management server; based on the permission acquisition request, the update permission cache information of the updated permission is obtained and sent; the update permission cache information is obtained and saved to the application server.

5. A system for immediate effect of changes to user permissions, based on the method for immediate effect of changes to user permissions as described in claim 1, characterized in that, The system includes: a permission file management module, a permission management module, and a permission change push module; The permission file management module is used to obtain user information, construct a user permission configuration file based on the user information, and perform a file loading operation on the user permission configuration file. The permission management module is used to perform a permission pre-update operation based on the result of the file loading operation; perform a permission verification operation on the result of the permission pre-update operation to obtain a verification result; and perform a permission update operation based on the verification result to obtain updated permissions. The permission change push module is used to perform a permission change information push operation based on the updated permissions; and to perform a permission change operation based on the result of the permission change information push operation. The permission file management module includes a permission file building unit and a permission file loading unit; The permission file building unit is used to obtain the user information of the permissions to be changed, and build the user permission configuration file through a text document based on the user information; The loading permission file unit is used to perform the file loading operation on the user permission configuration file to obtain permission file cache information; The permission management module includes a permission pre-update unit, a permission verification unit, and a permission update unit; The permission pre-update unit is used to perform the permission pre-update operation on the permission management server according to the permission file cache information to obtain pre-updated permissions; The permission verification unit is used to perform the permission verification operation through the test server according to the pre-updated permissions and the user permission configuration file to obtain the verification result; The permission update unit is used to perform the permission update operation on the permission management server according to the verification result, and obtain the updated permission.

6. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the method described in any one of claims 1-4, which states that changing user permissions takes effect immediately.

Images