Rights management method, device and storage medium
By establishing a business permission correspondence relationship in the permission server and directly configuring user access rights, the complexity of role-based permission management in the case of dispersed role members is solved, which improves permission management efficiency and reduces maintenance costs.
Patent Information
- Application Number
- CN202010838932.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-08-19
- Publication Date
- 2024-11-05
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
When the role members are relatively dispersed, the role-based permission management method cannot effectively simplify the complexity of permission management, which instead leads to an increase in the maintenance cost of the permission management system.
By establishing a business permission correspondence relationship in the permission server, obtaining the access permission information of the target user based on the target user and resource identification information, directly configure the access permissions of the user to avoid the increase in complexity caused by role permission management.
It improves the granularity of permission management, simplifies the permission management process, and reduces the later maintenance cost of the permission management system.
Smart Images

Figure CN112100585B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of computer technology, and in particular to a permission management method, device and storage medium. Background Art
[0002] Most of the current permission management methods are role-based access control (RBAC), that is, an association between permissions and roles is established, and users obtain the permissions of a role by becoming a member of that role. These RBAC-based permission management methods can greatly simplify the complexity of permission management and improve the efficiency of permission management when member roles are relatively concentrated (that is, the number of members corresponding to each role is large).
[0003] However, when role members are more dispersed (i.e., each role has fewer members and more roles are involved), the role's role is weakened. Creating roles does not simplify the difficulty of permission management. On the contrary, the creation of roles will increase the complexity of permission management and increase the maintenance cost of the permission management system. Summary of the invention
[0004] In order to overcome the above problems, the present disclosure provides a permission management method, device and storage medium.
[0005] According to a first aspect of an embodiment of the present disclosure, there is provided a rights management method, which is applied to a rights server, and the method includes:
[0006] Receiving a permission query request message sent by a business server, wherein the permission query request message includes target user identification information of a target user and resource identification information corresponding to a target resource requested to be accessed by the target user;
[0007] According to the target user identification information and the resource identification information, obtaining first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship, wherein the business permission correspondence relationship includes a correspondence relationship between the resource identification information and the user permission information, wherein the user permission information includes access permission information corresponding to the user identification information of a designated user, wherein the designated user includes a pre-set user who can access the target resource;
[0008] The first access permission information is sent to the business server, so that the business server configures the target user's access permission to the target resource according to the first access permission information.
[0009] Optionally, the acquiring, according to the target user identification information and the resource identification information, the first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship includes:
[0010] Determine the user authority information corresponding to the resource identification information through the business authority correspondence relationship;
[0011] The first access permission information corresponding to the target user identification information is acquired from the user permission information.
[0012] Optionally, when the target resource is a data type resource, the data type resource includes at least one of row data, column data and field data;
[0013] In the case where the data type resource includes row data, the resource identification information includes the row data identification information, and the business authority correspondence relationship includes the correspondence relationship between the row data identification information and row-level authority information; or,
[0014] In the case where the data type resource includes column data, the business authority correspondence relationship includes a correspondence relationship between the column data identification information and column-level authority information; or,
[0015] In the case where the data type resource includes field data, the business authority correspondence relationship includes a correspondence relationship between the field data identification information and the field authority information.
[0016] Optionally, before obtaining the first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship according to the target user identification information and the resource identification information, the method further includes:
[0017] Determine whether there is role information corresponding to the target user identification information;
[0018] The acquiring, according to the target user identification information and the resource identification information, the first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship comprises:
[0019] When it is determined that there is no role information corresponding to the target user identification information, first access permission information of the target user when accessing the target resource is obtained according to the target user identification information and the resource identification information through a pre-established business permission correspondence relationship.
[0020] Optionally, the method further comprises:
[0021] In the case where it is determined that there is role information corresponding to the target user identification information, obtaining second access permission information corresponding to the role information through a pre-established role permission correspondence relationship; the role permission correspondence relationship includes a correspondence relationship between the role information and the second access permission information;
[0022] The second access permission information is sent to the business server, so that the business server configures the target user's access permission to the target resource according to the second access permission information.
[0023] Optionally, the business authority correspondence relationship is pre-established in the following manner:
[0024] Receiving resource registration request information sent by the business server, the resource registration request information including the resource identification information of the target resource and the user authority information;
[0025] A correspondence between the resource identification information and the user authority information is established to obtain the business authority correspondence.
[0026] According to a second aspect of an embodiment of the present disclosure, there is provided a rights management device, which is applied to a rights server, and the device includes:
[0027] A receiving module is configured to receive a permission query request message sent by a business server, wherein the permission query request message includes target user identification information of a target user and resource identification information corresponding to a target resource requested to be accessed by the target user;
[0028] A first acquisition module is configured to acquire, according to the target user identification information and the resource identification information, first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship, wherein the business permission correspondence relationship includes a correspondence relationship between the resource identification information and the user permission information, the user permission information includes access permission information corresponding to the user identification information of a designated user, and the designated user includes a pre-set user who can access the target resource;
[0029] The first sending module is configured to send the first access permission information to the business server, so that the business server configures the target user's access permission to the target resource according to the first access permission information.
[0030] Optionally, the first acquisition module includes:
[0031] A determination submodule, configured to determine the user authority information corresponding to the resource identification information through the business authority correspondence relationship;
[0032] The acquisition submodule is configured to acquire the first access permission information corresponding to the target user identification information from the user permission information.
[0033] Optionally, when the target resource is a data type resource, the data type resource includes at least one of row data, column data and field data;
[0034] In the case where the data type resource includes row data, the resource identification information includes the row data identification information, and the business authority correspondence relationship includes the correspondence relationship between the row data identification information and row-level authority information; or,
[0035] In the case where the data type resource includes column data, the business authority correspondence relationship includes a correspondence relationship between the column data identification information and column-level authority information; or,
[0036] In the case where the data type resource includes field data, the business authority correspondence relationship includes a correspondence relationship between the field data identification information and the field authority information.
[0037] Optionally, the device further comprises:
[0038] A determination module, configured to determine whether there is role information corresponding to the target user identification information;
[0039] The first acquisition module is configured to obtain the first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship based on the target user identification information and the resource identification information when it is determined that there is no role information corresponding to the target user identification information.
[0040] Optionally, the device further comprises:
[0041] A second acquisition module is configured to, when determining that there is role information corresponding to the target user identification information, acquire second access permission information corresponding to the role information through a pre-established role permission correspondence relationship; the role permission correspondence relationship includes a correspondence relationship between the role information and the second access permission information;
[0042] The second sending module is configured to send the second access permission information to the business server, so that the business server configures the target user's access permission to the target resource according to the second access permission information.
[0043] Optionally, the business authority correspondence relationship is pre-established in the following manner:
[0044] Receiving resource registration request information sent by the business server, the resource registration request information including the resource identification information of the target resource and the user authority information;
[0045] A correspondence between the resource identification information and the user authority information is established to obtain the business authority correspondence.
[0046] According to a third aspect of an embodiment of the present disclosure, there is provided a rights management device, including:
[0047] processor;
[0048] a memory for storing processor-executable instructions;
[0049] Wherein, the processor is configured to:
[0050] Receiving a permission query request message sent by a business server, wherein the permission query request message includes target user identification information of a target user and resource identification information corresponding to a target resource requested to be accessed by the target user;
[0051] According to the target user identification information and the resource identification information, obtaining first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship, wherein the business permission correspondence relationship includes a correspondence relationship between the resource identification information and the user permission information, wherein the user permission information includes access permission information corresponding to the user identification information of a designated user, wherein the designated user includes a pre-set user who can access the target resource;
[0052] The first access permission information is sent to the business server, so that the business server configures the target user's access permission to the target resource according to the first access permission information.
[0053] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, on which computer program instructions are stored, and when the program instructions are executed by a processor, the steps of the method described in the first aspect above are implemented.
[0054] The technical solution provided by the embodiments of the present disclosure may include the following beneficial effects: based on the target user identification information and the resource identification information, the first access permission information of the target user when accessing the target resource is obtained through a pre-established business permission correspondence relationship; since the business permission correspondence relationship includes the correspondence between the resource identification information and the user permission information, and the user permission information includes the access permission information corresponding to the user identification information of the specified user, the granularity of permission management can be effectively improved, and the problem of increased complexity of permission management caused by the use of role permission management can be effectively avoided, which is conducive to improving permission management efficiency and reducing the subsequent maintenance cost of the permission management system.
[0055] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0056] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[0057] Figure 1 is a flowchart of a method for rights management shown in an exemplary embodiment of the present disclosure;
[0058] Figure 2 is a flowchart of a method for rights management shown in another exemplary embodiment of the present disclosure;
[0059] Figure 3 is a block diagram of a rights management device shown in another exemplary embodiment of the present disclosure;
[0060] Figure 4 is based on Figure 3 A block diagram of a rights management device shown in the illustrated embodiment;
[0061] Figure 5 It is a block diagram of a device for rights management according to an exemplary embodiment. DETAILED DESCRIPTION
[0062] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.
[0063] Before introducing the specific implementation methods of the present invention in detail, the specific application scenarios of the present invention are first described as follows. The present invention can be applied to the process in which the permission server returns the permission information of the specified resource in the business system run by the business server to the business server. Here, the XM community system is used as an example for explanation. The XM community system is a platform for users of products produced by XM company to exchange product usage experience. In the process of exchanging product usage experience, the advantages and disadvantages of XM products are often involved. XM products usually include multiple products such as product A, product B and product C. XM community users can include product A developer users, product B developer users, product C developer users and development organization manager users. Therefore, in order to better manage the community of the XM community system Users need to set corresponding permissions for each community user. For example, users who are developers of product A can only see relevant communication information about product A, users who are developers of product B can only see relevant communication experience about product B, users who are developers of product C can only see relevant communication experience about product C, and managers of development organizations can see communication information of all products. In order to better manage the community user permissions of the XM community system, the business server running the XM community system is connected to the permission server. When each community user accesses the target resource in the XM community system, the permission server provides the XM community system with the corresponding access permission of the community user, so that the XM community system configures corresponding resources for the community user according to the access permission sent by the permission server.
[0064] In the related art, when performing permission management, community users are usually divided into multiple roles (for example, A product developer user, B product developer user, C product developer user and development organization manager user, etc.), and the association relationship between permissions and roles is established, and the permissions of the role are configured for the community users by making the community users members of a certain role. However, with the expansion of the functions of the XM community system, functions such as employee attendance and salary details payment are added to the XM community system. In the functions such as employee attendance and salary details payment, data resources (for example, sales reports, payroll tables, etc.) are often involved. In the access permissions of data resources, it is often encountered that only one or two community users have access permissions for each row (column) of data. If the permission management method in the related art is still used, the community user is made a member of a role, and then the access permissions of the row (column) of data are configured for the role, this will not only fail to simplify the difficulty of permission management, but will increase the complexity of permission management due to the creation of roles, and will also increase the later maintenance cost of the permission management system.
[0065] In order to solve the technical problems existing in the related technology, the present disclosure provides a permission management method, device and storage medium. The method obtains the first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship based on the target user identification information and the resource identification information. Since the business permission correspondence relationship includes the correspondence between the resource identification information and the user permission information, and the user permission information includes the access permission information corresponding to the user identification information of the specified user, the granularity of permission management can be effectively improved, and the problem of increased complexity of permission management caused by adopting role permission management can be effectively avoided, which is conducive to improving the efficiency of permission management and reducing the later maintenance cost of the permission management system.
[0066] Figure 1 is a flowchart of a method for managing rights shown in an exemplary embodiment of the present disclosure; see Figure 1 The method is applied to the authority server and may include the following steps:
[0067] Step 101: Receive a permission query request message sent by a business server.
[0068] The permission query request message includes target user identification information of the target user and resource identification information corresponding to the target resource that the target user requests to access.
[0069] It should be noted that a business system is running in the business server, the target user is at least one of the users of the business system, the target user identification information may be the ID account, name or icon of the target user, and the target resource may be a web page, a label, button, table, field, database, etc. in the page.
[0070] Step 102: acquiring first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship according to the target user identification information and the resource identification information.
[0071] The business authority correspondence relationship includes the correspondence relationship between the resource identification information and the user authority information, the user authority information includes the access authority information corresponding to the user identification information of the designated user, and the designated user includes a pre-set user who can access the target resource.
[0072] In this step, a possible implementation method is: determining the user authority information corresponding to the resource identification information through the business authority correspondence, and acquiring the first access authority information corresponding to the target user identification information from the user authority information.
[0073] In the above implementation, the business authority correspondence relationship can be pre-established in the following manner:
[0074] Receive resource registration request information sent by the business server, the resource registration request information including the resource identification information of the target resource and the user authority information; establish a correspondence between the resource identification information and the user authority information to obtain the business authority correspondence.
[0075] For example, the XM community system includes a creation module, a community product circle module, a data management module, and an indicator module. After the creation module, the community product circle module, the data management module, and the indicator module are created in the XM community system, the user authority information of the creation module, the community product circle module, the data management module, and the indicator module can be pre-stored in an authority server connected to the XM community system, and a correspondence between the module identifier and the user authority information of each module in the XM community system is generated in the authority server, that is, the business authority correspondence corresponding to the XM community system is pre-stored in the authority server, and the business authority correspondence corresponding to the XM community system includes a correspondence between the identifier of the creation module and the user authority information of the creation module, a correspondence between the identifier of the community product circle module and the user authority information of the community product circle module, and a correspondence between the identifier of the data management module and the user authority information of the data management module. The correspondence between the identification of the management module and the user permission information of the data management module, the correspondence between the identification of the indicator module and the user permission information of the indicator module, wherein the user permission information of the creation module includes the correspondence between the user identification information corresponding to the user who can access the creation module and the access permission information, the user permission information of the community product circle module includes the correspondence between the user identification information corresponding to the user who can access the community product circle module and the access permission information, the user permission information of the data management module includes the correspondence between the user identification information corresponding to the user who can access the data management module and the access permission information, the user permission information of the indicator module includes the correspondence between the user identification information corresponding to the user who can access the indicator module and the access permission information, and the access permission information can be an identification of permissions such as readable, editable or forwardable.
[0076] Step 103: Send the first access permission information to the business server, so that the business server configures the target user's access permission to the target resource according to the first access permission information.
[0077] Still taking the example shown in the above step 102 as an example for explanation, when user M of the XM community system accesses the creation module, the XM community system will send a permission query request message to the permission server, and the permission query request message includes the user identifier M of the user M and the identifier of the creation module. When the permission server receives the permission query request, it obtains the access permission information corresponding to the user identifier M from the correspondence between the identifier of the creation module and the user permission information of the creation module, and sends the access permission information corresponding to the user identifier M to the XM community system. The XM community system configures access permissions for the creation module for the user M according to the access permission information corresponding to the user identifier M.
[0078] The above technical scheme obtains the first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship based on the target user identification information and the resource identification information. Since the business permission correspondence relationship includes the correspondence between the resource identification information and the user permission information, and the user permission information includes the access permission information corresponding to the user identification information of the specified user, the granularity of permission management can be effectively improved, and the problem of increased complexity of permission management caused by the use of role permission management can be effectively avoided, which is conducive to improving the efficiency of permission management and reducing the subsequent maintenance cost of the permission management system.
[0079] Figure 2 is a flowchart of a method for managing rights shown in another exemplary embodiment of the present disclosure; see Figure 2 , the method may include the following steps:
[0080] Step 201: receiving resource registration request information sent by the service server.
[0081] The resource registration request information includes the resource identification information of the target resource and the user authority information, wherein the user authority information includes access authority information corresponding to the user identification information of the designated user, and the designated user includes a pre-set user who can access the target resource.
[0082] It should be noted that the target resource may be a web page, a label in the page, a button, a table, a field, a database, etc. The access permission information may be an identifier of permissions such as read, edit, forward, and copy.
[0083] Step 202: Establish a correspondence between the resource identification information and the user authority information to obtain the business authority correspondence.
[0084] A possible implementation of this step is: when the target resource is a data type resource, the data type resource includes at least one of row data, column data and field data; when the data type resource includes row data, the resource identification information includes the row data identification information, and the business permission correspondence includes the correspondence between the row data identification information and the row-level permission information; or, when the data type resource includes column data, the business permission correspondence includes the correspondence between the column data identification information and the column-level permission information; or, when the data type resource includes field data, the business permission correspondence includes the correspondence between the field data identification information and the field permission information.
[0085] Among them, the row-level permission information includes the correspondence between the user identification information of the specified user who can access the row data and the access permission information, the column-level permission information includes the correspondence between the user identification information of the specified user who can access the column data and the access permission information, and the field permission information includes the correspondence between the user identification information of the specified user who can access the field data and the access permission information.
[0086] It should be noted that whether the target resource belongs to a data type resource can be determined by the resource type corresponding to the target resource. For example, when the resource type of the target resource is determined to be int, it can be determined that the target resource belongs to a data type resource. The row data is the data stored in a row in the data table, and the row data identification information can be the row number or row name in the target resource. The column data is the data stored in a column in the data table, and the column data identification information can be the column number or column name in the target resource. The field data is a data resource composed of fields, and the field data identification information can be the code or symbol of the target field in the target resource.
[0087] For example, when the target resource is a salary report, each row of data in the salary report records the salary details of an employee, wherein each employee has read permission for his or her own salary details, and the financial staff and company leaders have read and edit permissions for the entire salary report. The business permission correspondence for each row of data in the salary report may include the correspondence between the row number of the row in the salary report and the row-level permission information of the row of data. For example, if the row of data is the salary details of employee A, the corresponding row-level permission information includes the correspondence between employee A's name and the read permission, and the correspondence between financial employee B's name and the read and edit permissions. In this way, for data-type resources, the correspondence between the resource identification information of the target resource and the user permission information is directly established, which can effectively improve the granularity of the permission management of data-type resources, avoid the problem of complicated permission management caused by role allocation, and thus facilitate the later maintenance of the permission management system and save data maintenance costs.
[0088] Step 203: Receive the authority query request message sent by the business server.
[0089] The permission query request message includes target user identification information of the target user and resource identification information corresponding to the target resource that the target user requests to access.
[0090] It should be noted that the target user is one of the users who can access the target resource. The target user identification information can be the ID account, name or icon of the target user. The target resource can be a web page, a label, button, table, field, database, etc. in the page.
[0091] Step 204, determining whether there is role information corresponding to the target user identification information;
[0092] The role information may include an organizational structure (for example, a company consists of a sales department, a human resources department, a production department, and a logistics department) or a custom role (for example, a gold member, a silver member, a super gold member, etc.).
[0093] It should be noted that, when it is determined that there is a corresponding relationship between the target user identification information and an organization in the organizational structure, or when it is determined that there is a corresponding relationship between the target user identification information and a custom role, it can be determined that there is role information corresponding to the target identification information. When it is determined that there is no corresponding relationship between the target user identification information and any organization in the organizational structure, and there is no corresponding relationship between the target user identification information and any custom role, it can be determined that there is no role information corresponding to the target identification information.
[0094] In this step, if it is determined that the role information corresponding to the target user identification information does not exist, steps 205 to 207 are executed; if it is determined that the role information corresponding to the target user identification information exists, steps 208 to 209 are executed.
[0095] Step 205: Determine the user authority information corresponding to the resource identification information through the business authority correspondence relationship.
[0096] Step 206: Acquire the first access permission information corresponding to the target user identification information from the user permission information.
[0097] For example, when obtaining the first access permission of the creation module corresponding to the user M of the XM community system from the permission server, the correspondence between the identifier of the creation module and the user permission information of the creation module, the correspondence between the identifier of the community product circle module and the user permission information of the community product circle module, the correspondence between the identifier of the data management module and the user permission information of the data management module, and the correspondence between the identifier of the indicator module and the user permission information of the indicator module can be obtained according to the identifier of the creation module, thereby obtaining the user permission information of the identifier of the creation module. Since the user permission information of the creation module includes the correspondence between the user identification information corresponding to the user who can access the creation module and the access permission information, the access permission information corresponding to the user identifier M can be obtained according to the target user identifier.
[0098] Step 207: Send the first access permission information to the business server, so that the business server configures the target user's access permission to the target resource according to the first access permission information.
[0099] The above steps 203 to 207 can obtain the first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship based on the target user identification information and the resource identification information. Since the business permission correspondence relationship includes the correspondence between the resource identification information and the user permission information, and the user permission information includes the access permission information corresponding to the user identification information of the specified user, the granularity of permission management can be effectively improved, and the problem of increased complexity of permission management caused by the use of role permission management can be effectively avoided, which is conducive to improving the efficiency of permission management and reducing the subsequent maintenance cost of the permission management system.
[0100] Step 208: Obtain second access permission information corresponding to the role information through the pre-established role permission correspondence relationship.
[0101] The role permission correspondence relationship includes the correspondence relationship between the role information and the second access permission information. The second access permission information may be identification information of permissions such as read, edit, copy, and forward.
[0102] For example, when there is a correspondence between the target user identifier of the target user and a gold member, the access permission information corresponding to the gold member is obtained, and the access permission information corresponding to the gold member is used as the second access permission information of the target user.
[0103] Step 209: Send the second access permission information to the business server, so that the business server configures the target user's access permission to the target resource according to the second access permission information.
[0104] The above steps 208 to 209 can, when it is determined that there is role information corresponding to the target user identification information, obtain the second access permission information corresponding to the role information through the pre-established role permission correspondence relationship. When the number of members corresponding to each role is large, the complexity of permission management can be greatly simplified and the efficiency of permission management can be improved.
[0105] The above technical scheme can, when it is determined that there is role information corresponding to the target user identification information, obtain the second access permission information corresponding to the role information through a pre-established role permission correspondence relationship. It can also, when it is determined that there is no role information corresponding to the target user identification information, obtain the first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship. This can not only effectively improve the granularity of permission management, but also effectively improve the permission management efficiency of the permission management system and reduce the subsequent maintenance cost of the permission management system.
[0106] Figure 3 is a block diagram of a rights management device shown in another exemplary embodiment of the present disclosure; see Figure 3 , the device is applied to the authority server and may include:
[0107] The receiving module 301 is configured to receive a permission query request message sent by a business server, wherein the permission query request message includes target user identification information of a target user and resource identification information corresponding to a target resource requested to be accessed by the target user;
[0108] The first acquisition module 302 is configured to acquire, according to the target user identification information and the resource identification information, first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship, wherein the business permission correspondence relationship includes a correspondence relationship between the resource identification information and the user permission information, wherein the user permission information includes access permission information corresponding to the user identification information of a specified user, wherein the specified user includes a pre-set user who can access the target resource;
[0109] The first sending module 303 is configured to send the first access permission information to the business server, so that the business server configures the target user's access permission to the target resource according to the first access permission information.
[0110] The above technical solution, through the first acquisition module 302, obtains the first access permission information of the target user when accessing the target resource according to the target user identification information and the resource identification information through a pre-established business permission correspondence relationship. Since the business permission correspondence includes the correspondence between the resource identification information and the user permission information, and the user permission information includes the access permission information corresponding to the user identification information of the specified user, the granularity of permission management can be effectively improved, and the problem of increased complexity of permission management caused by the use of role permission management can be effectively avoided, which is conducive to improving the efficiency of permission management and reducing the subsequent maintenance cost of the permission management system.
[0111] Figure 4 is based on Figure 3 The embodiment shown is a block diagram of a rights management device; see Figure 4 , the first acquisition module 302 includes:
[0112] The determination submodule 3021 is configured to determine the user authority information corresponding to the resource identification information through the business authority correspondence relationship;
[0113] The acquisition submodule 3022 is configured to acquire the first access permission information corresponding to the target user identification information from the user permission information.
[0114] Optionally, when the target resource is a data type resource, the data type resource includes at least one of row data, column data and field data;
[0115] In the case where the data type resource includes row data, the resource identification information includes the row data identification information, and the business authority correspondence relationship includes the correspondence relationship between the row data identification information and row-level authority information; or,
[0116] In the case where the data type resource includes column data, the business authority correspondence relationship includes a correspondence relationship between the column data identification information and the column-level authority information; or,
[0117] In the case where the data type resource includes field data, the business authority correspondence relationship includes a correspondence relationship between the field data identification information and the field authority information.
[0118] Optionally, the device further comprises:
[0119] A determination module 304 is configured to determine whether there is role information corresponding to the target user identification information;
[0120] The first acquisition module 302 is configured to obtain the first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship based on the target user identification information and the resource identification information when it is determined that there is no role information corresponding to the target user identification information.
[0121] Optionally, the device further comprises:
[0122] The second acquisition module 305 is configured to, when determining that there is role information corresponding to the target user identification information, acquire the second access permission information corresponding to the role information through a pre-established role permission correspondence relationship; the role permission correspondence relationship includes a correspondence relationship between the role information and the second access permission information;
[0123] The second sending module 306 is configured to send the second access permission information to the business server, so that the business server configures the target user's access permission to the target resource according to the second access permission information.
[0124] Optionally, the business authority correspondence is pre-established in the following manner:
[0125] Receiving resource registration request information sent by the business server, the resource registration request information including the resource identification information of the target resource and the user authority information;
[0126] A correspondence between the resource identification information and the user authority information is established to obtain the business authority correspondence.
[0127] The above technical scheme can, when it is determined that there is role information corresponding to the target user identification information, obtain the second access permission information corresponding to the role information through a pre-established role permission correspondence relationship. It can also, when it is determined that there is no role information corresponding to the target user identification information, obtain the first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship. This can not only effectively improve the granularity of permission management, but also effectively improve the permission management efficiency of the permission management system and reduce the subsequent maintenance cost of the permission management system.
[0128] An exemplary embodiment of the present disclosure further provides a rights management device, including:
[0129] processor;
[0130] a memory for storing processor-executable instructions;
[0131] The processor is configured as follows:
[0132] Receive a permission query request message sent by a business server, the permission query request message including target user identification information of a target user and resource identification information corresponding to a target resource requested to be accessed by the target user;
[0133] According to the target user identification information and the resource identification information, first access permission information of the target user when accessing the target resource is obtained through a pre-established business permission correspondence relationship, wherein the business permission correspondence relationship includes a correspondence relationship between the resource identification information and the user permission information, wherein the user permission information includes access permission information corresponding to the user identification information of a designated user, wherein the designated user includes a pre-set user who can access the target resource;
[0134] The first access permission information is sent to the business server, so that the business server configures the target user's access permission to the target resource according to the first access permission information.
[0135] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.
[0136] The present disclosure also provides a computer-readable storage medium on which computer program instructions are stored. When the program instructions are executed by a processor, the steps of the rights management method provided by the present disclosure are implemented.
[0137] Figure 5 5 is a block diagram of a device for rights management according to an exemplary embodiment. For example, the device 500 may be provided as a server. Figure 5 , the apparatus 500 includes a processing component 522, which further includes one or more processors, and a memory resource represented by a memory 532 for storing instructions executable by the processing component 522, such as an application. The application stored in the memory 532 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 522 is configured to execute instructions to perform the above-mentioned permission management method.
[0138] The device 500 may also include a power supply component 526 configured to perform power management of the device 500, a wired or wireless network interface 550 configured to connect the device 500 to a network, and an input / output (I / O) interface 558. The device 500 may operate based on an operating system stored in the memory 532, such as Windows Server 2008. TM , Mac OS X TM , Unix TM ,Linux TM , FreeBSD TM or similar.
[0139] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the present disclosure. This application is intended to cover any variations, uses or adaptations of the present disclosure, which follow the general principles of the present disclosure and include common knowledge or customary technical means in the art that are not disclosed in the present disclosure. The specification and examples are to be considered as exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.
[0140] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims
1. A rights management method, characterized in that: Applied to an authority server, the method comprises: Receiving a permission query request message sent by a business server, wherein the permission query request message includes target user identification information of a target user and resource identification information corresponding to a target resource requested to be accessed by the target user; According to the target user identification information and the resource identification information, obtaining first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship, wherein the business permission correspondence relationship includes a correspondence relationship between the resource identification information and the user permission information, wherein the user permission information includes access permission information corresponding to the user identification information of a designated user, wherein the designated user includes a pre-set user who can access the target resource; sending the first access permission information to the business server, so that the business server configures the target user's access permission to the target resource according to the first access permission information; In the case where the target resource is a data type resource, the data type resource includes at least one of row data, column data and field data; In the case where the data type resource includes row data, the resource identification information includes the row data identification information, and the business authority correspondence relationship includes the correspondence relationship between the row data identification information and row-level authority information; or, In the case where the data type resource includes column data, the business authority correspondence relationship includes a correspondence relationship between the column data identification information and column-level authority information; or, In the case where the data type resource includes field data, the business authority correspondence relationship includes a correspondence relationship between the field data identification information and the field authority information.
2. The method according to claim 1, characterized in that The acquiring, according to the target user identification information and the resource identification information, the first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship comprises: Determine the user authority information corresponding to the resource identification information through the business authority correspondence relationship; The first access permission information corresponding to the target user identification information is acquired from the user permission information.
3. The method according to claim 1, characterized in that Before obtaining the first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship according to the target user identification information and the resource identification information, the method further includes: Determine whether there is role information corresponding to the target user identification information; The acquiring, according to the target user identification information and the resource identification information, the first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship comprises: When it is determined that there is no role information corresponding to the target user identification information, first access permission information of the target user when accessing the target resource is obtained according to the target user identification information and the resource identification information through a pre-established business permission correspondence relationship.
4. The method according to claim 3, characterized in that The method further comprises: In the case where it is determined that there is role information corresponding to the target user identification information, obtaining second access permission information corresponding to the role information through a pre-established role permission correspondence relationship; the role permission correspondence relationship includes a correspondence relationship between the role information and the second access permission information; The second access permission information is sent to the business server, so that the business server configures the target user's access permission to the target resource according to the second access permission information.
5. The method according to any one of claims 1 to 4, characterized in that: The business authority correspondence relationship is pre-established in the following manner: Receiving resource registration request information sent by the business server, the resource registration request information including the resource identification information of the target resource and the user authority information; A correspondence between the resource identification information and the user authority information is established to obtain the business authority correspondence.
6. A rights management device, characterized in that: Applied to an authority server, the device comprises: A receiving module is configured to receive a permission query request message sent by a business server, wherein the permission query request message includes target user identification information of a target user and resource identification information corresponding to a target resource requested to be accessed by the target user; A first acquisition module is configured to acquire, according to the target user identification information and the resource identification information, first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship, wherein the business permission correspondence relationship includes a correspondence relationship between the resource identification information and the user permission information, the user permission information includes access permission information corresponding to the user identification information of a designated user, and the designated user includes a pre-set user who can access the target resource; A first sending module is configured to send the first access permission information to the business server, so that the business server configures the target user's access permission to the target resource according to the first access permission information; In the case where the target resource is a data type resource, the data type resource includes at least one of row data, column data and field data; In the case where the data type resource includes row data, the resource identification information includes the row data identification information, and the business authority correspondence relationship includes the correspondence relationship between the row data identification information and row-level authority information; or, In the case where the data type resource includes column data, the business authority correspondence relationship includes a correspondence relationship between the column data identification information and column-level authority information; or, In the case where the data type resource includes field data, the business authority correspondence relationship includes a correspondence relationship between the field data identification information and the field authority information.
7. The device according to claim 6, characterized in that The first acquisition module includes: A determination submodule, configured to determine the user authority information corresponding to the resource identification information through the business authority correspondence relationship; The acquisition submodule is configured to acquire the first access permission information corresponding to the target user identification information from the user permission information.
8. The device according to claim 6, characterized in that The device also includes: A determination module, configured to determine whether there is role information corresponding to the target user identification information; The first acquisition module is configured to obtain the first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship based on the target user identification information and the resource identification information when it is determined that there is no role information corresponding to the target user identification information.
9. The device according to claim 8, characterized in that The device also includes: A second acquisition module is configured to, when determining that there is role information corresponding to the target user identification information, acquire second access permission information corresponding to the role information through a pre-established role permission correspondence relationship; the role permission correspondence relationship includes a correspondence relationship between the role information and the second access permission information; The second sending module is configured to send the second access permission information to the business server, so that the business server configures the target user's access permission to the target resource according to the second access permission information.
10. The device according to any one of claims 6 to 9, characterized in that The business authority correspondence relationship is pre-established in the following manner: Receiving resource registration request information sent by the business server, the resource registration request information including the resource identification information of the target resource and the user authority information; A correspondence between the resource identification information and the user authority information is established to obtain the business authority correspondence.
11. A rights management device, characterized in that: include: processor; a memory for storing processor-executable instructions; Wherein, the processor is configured to: Receiving a permission query request message sent by a business server, wherein the permission query request message includes target user identification information of a target user and resource identification information corresponding to a target resource requested to be accessed by the target user; According to the target user identification information and the resource identification information, obtaining first access permission information of the target user when accessing the target resource through a pre-established business permission correspondence relationship, wherein the business permission correspondence relationship includes a correspondence relationship between the resource identification information and the user permission information, wherein the user permission information includes access permission information corresponding to the user identification information of a designated user, wherein the designated user includes a pre-set user who can access the target resource; sending the first access permission information to the business server, so that the business server configures the target user's access permission to the target resource according to the first access permission information; In the case where the target resource is a data type resource, the data type resource includes at least one of row data, column data and field data; In the case where the data type resource includes row data, the resource identification information includes the row data identification information, and the business authority correspondence relationship includes the correspondence relationship between the row data identification information and row-level authority information; or, In the case where the data type resource includes column data, the business authority correspondence relationship includes a correspondence relationship between the column data identification information and column-level authority information; or, In the case where the data type resource includes field data, the business authority correspondence relationship includes a correspondence relationship between the field data identification information and the field authority information.
12. A computer-readable storage medium having computer program instructions stored thereon, characterized in that: When the program instructions are executed by a processor, the steps of the method described in any one of claims 1 to 5 are implemented.
