Authority management method and device, equipment and storage medium

By introducing multiple permission types and authorization methods into database permission management, the complexity problem caused by the singularity of permission management in the existing technology is solved, and more flexible and secure permission configuration is achieved, reducing data risks.

CN119089497APending Publication Date: 2024-12-06CHINA ELECTRONICS CLOUD DIGITAL INTELLIGENCE TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202411191043.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-28
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

The existing database permission management method is single, which leads to complex permission management, which can easily cause data problems and production accidents, and it is difficult to effectively control the permissions of multiple databases.

Method used

Provide a permission management method, by displaying the permission configuration page of the target database, including the first permission type and the second permission type, receiving selected operations, configuring permissions for the target database for the target object, supporting active authorization and passive authorization, and generating Approval form and permission verification and recycling are carried out in the database managed by restricted account.

Benefits of technology

丰富了为目标对象配置目标数据库权限的方式,提高了权限管理的灵活性和安全性,减少了数据风险,提高了数据平台的效率和安全管理。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119089497A_ABST
    Figure CN119089497A_ABST
Patent Text Reader

Abstract

The invention provides an authority management method and device, equipment and a storage medium, and the method comprises the steps: if an authority management operation for a target database is received, displaying an authority configuration page of the target database; wherein the permission configuration page comprises a first permission type and a second permission type, and the first permission type and the second permission type are used for configuring permissions for the target database for the target object, receiving a selection operation for the first permission type or the second permission type, and configuring the permissions for the target database for the target object. It can be seen that the permission of the first permission type or the permission of the second permission type for the target database can be configured for the target object, and the mode of configuring the permission of the target database for the target object is enriched.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of data processing, and in particular to a permission management method, device, equipment and storage medium. Background Art

[0002] As the number of databases integrated into data platforms increases, database permission management becomes particularly important.

[0003] However, the current permission management method for databases is relatively simple, which makes database permission management complicated and easily leads to data problems and production accidents. Therefore, how to enrich database permission management has become a technical problem that needs to be solved urgently. Summary of the invention

[0004] In order to solve the above technical problems, the embodiments of the present disclosure provide a permission management method, apparatus, device and storage medium.

[0005] In a first aspect, the present disclosure provides a rights management method, the method comprising:

[0006] If a permission management operation for a target database is received, a permission configuration page for the target database is displayed; wherein the permission configuration page includes a first permission type and a second permission type, and the first permission type and the second permission type are used to configure permissions for the target object for the target database;

[0007] A selection operation for the first permission type or the second permission type is received, and permissions for the target object on the target database are configured.

[0008] In an optional implementation manner, if a permission management operation for a target database is received, displaying a permission configuration page for the target database includes:

[0009] If a permission configuration operation of a target database for a target object is received from a platform administrator, a permission configuration page of the target database is displayed.

[0010] In an optional implementation manner, if a permission management operation for a target database is received, displaying a permission configuration page for the target database includes:

[0011] If a permission application operation of the target object for the target database is received, a permission configuration page of the target database is displayed;

[0012] Accordingly, the receiving a selected operation for the first permission type or the second permission type and configuring permissions for the target object for the target database includes:

[0013] receiving a selection operation for the first permission type or the second permission type, and generating an approval form for the permission application of the target object for the target database;

[0014] If the approval form is approved, the permissions for the target database are configured for the target object.

[0015] In an optional implementation manner, the target database is a database managed based on a limited account, and the receiving a selected operation for the first permission type or the second permission type and configuring permissions for the target database for the target object includes:

[0016] A selection operation for the first permission type or the second permission type is received, and permissions of the target object for the target database are verified. If the verification passes, permissions for the target database are configured for the target object.

[0017] In an optional implementation, the target database includes at least one database, the at least one database includes a first database and a second database, and the first database and the second database belong to different database types.

[0018] In an optional implementation manner, after receiving the selected operation for the first permission type or the second permission type and configuring the permission for the target object for the target database, the method further includes:

[0019] A permission reclaiming operation for the target database is received, and the permission of the target database configured for the target object is reclaimed.

[0020] In an optional implementation manner, the method further includes:

[0021] If a permission management operation for a target data table is received, a permission configuration page for the target data table is displayed; wherein the target data table includes a table in a target database or a view in the target database, and the permission configuration page includes a query permission, and the query permission is used to configure a query permission for the target object for the target data table;

[0022] A selection operation for the query permission is received, and the query permission for the target data table is configured for the target object.

[0023] In a second aspect, the present disclosure provides a rights management device, the device comprising:

[0024] A first display module, configured to display a permission configuration page of the target database upon receiving a permission management operation for the target database; wherein the permission configuration page includes a first permission type and a second permission type, and the first permission type and the second permission type are used to configure permissions for the target object for the target database;

[0025] The first configuration module is used to receive a selected operation for the first permission type or the second permission type, and configure permissions for the target database for the target object.

[0026] In a third aspect, the present disclosure provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, and when the instructions are executed on a terminal device, the terminal device implements the above method.

[0027] In a fourth aspect, the present disclosure provides a rights management device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above method when executing the computer program.

[0028] In a fifth aspect, the present disclosure provides a computer program product, wherein the computer program product comprises a computer program / instructions, and the computer program / instructions implement the above method when executed by a processor.

[0029] Compared with the prior art, the technical solution provided by the embodiments of the present disclosure has at least the following advantages:

[0030] The disclosed embodiment provides a permission management method, if a permission management operation for a target database is received, a permission configuration page for the target database is displayed; wherein the permission configuration page includes a first permission type and a second permission type, the first permission type and the second permission type are used to configure permissions for the target database for the target object, receive a selection operation for the first permission type or the second permission type, and configure permissions for the target database for the target object. It can be seen that the disclosed embodiment can configure permissions of the first permission type or the second permission type for the target database for the target object, enriching the way of configuring permissions for the target database for the target object. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] 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.

[0032] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0033] Figure 1 A flowchart of a permission management method provided by an embodiment of the present disclosure;

[0034] Figure 2 A schematic diagram of a database permission configuration page provided in an embodiment of the present disclosure;

[0035] Figure 3 A schematic diagram of another database permission configuration page provided in an embodiment of the present disclosure;

[0036] Figure 4 A schematic diagram of another database permission configuration page provided in an embodiment of the present disclosure;

[0037] Figure 5 A schematic diagram of another database permission configuration page provided in an embodiment of the present disclosure;

[0038] Figure 6 A schematic diagram of another database permission configuration page provided in an embodiment of the present disclosure;

[0039] Figure 7 A flowchart of another permission management method provided by an embodiment of the present disclosure;

[0040] Figure 8 A flowchart of another permission management method provided by an embodiment of the present disclosure;

[0041] Fig. 9 A flowchart of another permission management method provided by an embodiment of the present disclosure;

[0042] Fig.10 A schematic diagram of the structure of a rights management device provided by an embodiment of the present disclosure;

[0043] Fig.11 A schematic diagram of the structure of a rights management device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0044] In order to more clearly understand the above-mentioned objectives, features and advantages of the present disclosure, the scheme of the present disclosure will be further described below. It should be noted that the embodiments of the present disclosure and the features in the embodiments can be combined with each other without conflict.

[0045] In the following description, many specific details are set forth to facilitate a full understanding of the present disclosure, but the present disclosure may also be implemented in other ways different from those described herein; it is obvious that the embodiments in the specification are only part of the embodiments of the present disclosure, rather than all of the embodiments.

[0046] Terminology explanation:

[0047] Organization: The present disclosure embodiment performs permission management based on organization (department). The same organization shares one account, which facilitates collaborative data operations among personnel in the same organization.

[0048] Data source: refers to data sources such as MySQL, Oracle, and Hive.

[0049] Database: refers to the database in data sources such as MySQL, Oracle, and Hive.

[0050] Database table: refers to a table in a database or a view in a database.

[0051] Database account: the account used to log in to the database.

[0052] Data platforms usually need to integrate multiple databases, and for different databases, expansion and development need to be carried out during the integration. As more and more databases are integrated, how to control and manage database permissions will become a relatively large problem. If there is a deviation in the management of permissions at this time, it will bring many data management problems, reduce the efficiency of the data platform, increase data risks, and even cause major production accidents such as data leakage.

[0053] Currently, many data platforms have a single database target and can only adapt to a certain type of database. Some have a single authorization system and only support a single authorization, which complicates database permission management and easily leads to data problems and production accidents.

[0054] In order to enrich the manner of configuring target database permissions for target objects, an embodiment of the present disclosure provides a permission management method.

[0055] Specifically, if a permission management operation for a target database is received, a permission configuration page for the target database is displayed; wherein the permission configuration page includes a first permission type and a second permission type, the first permission type and the second permission type are used to configure permissions for the target database for the target object, a selection operation for the first permission type or the second permission type is received, and permissions for the target database are configured for the target object. It can be seen that the present disclosure can configure permissions of the first permission type or permissions of the second permission type for the target database for the target object, enriching the way of configuring permissions for the target database for the target object.

[0056] Based on this, the present disclosure provides a method for managing permissions. Figure 1 , is a flowchart of a permission management method provided by an embodiment of the present disclosure, the method comprising:

[0057] S101: If a permission management operation for a target database is received, a permission configuration page for the target database is displayed.

[0058] The permission configuration page includes a first permission type and a second permission type, and the first permission type and the second permission type are used to configure permissions for the target object with respect to the target database.

[0059] In the embodiment of the present disclosure, the first permission type may be full permission, and the full permission includes creation permission, query permission, update permission, and deletion permission. The second permission type may be query permission.

[0060] In the disclosed embodiment, there are full permissions and query permissions for the target database.

[0061] Among them, the permission management operation for the target database can be implemented through active authorization or passive authorization.

[0062] Specifically, active authorization means that the platform administrator can actively grant the authority of the target database to a certain organization (such as the target object described below).

[0063] In an optional implementation, if a permission configuration operation of a target database for a target object is received from a platform administrator, a permission configuration page of the target database is displayed.

[0064] The platform administrator refers to a manager who has the authority to manage the database, and the target object refers to the object for which the platform administrator wants to configure permissions, such as an organization.

[0065] In the embodiment of the present disclosure, the permission configuration operation of the platform administrator on the target database of the target object refers to the permission granted by the platform administrator to the target object on the target database.

[0066] The platform administrator can configure the permissions of the target database for the target object by following the steps below:

[0067] refer to Figure 2 , is a schematic diagram of a database permission configuration page provided by an embodiment of the present disclosure, such as Figure 2 As shown, the platform administrator opens the database permission configuration page and selects the data permission authorization control.

[0068] In the Data Permission Authorization control, select the target object, such as Organization B.

[0069] Next, select the Add new database authorization control to add a new database permission.

[0070] After selecting the new database authorization control, jump to Figure 3 The page shown.

[0071] exist Figure 3 In the page shown, select the target database, that is, the specific database for which you want to configure permissions.

[0072] Through the above process, the platform administrator can easily select the target object and target database and perform specific permission configuration operations.

[0073] Further, after receiving the permission configuration operation of the target database of the target object from the platform administrator, the following is displayed: Figure 3 The permission configuration page of the target database shown in the figure displays a first permission type and a second permission type on the page, wherein the first permission type and the second permission type are used to configure permissions for the target database for the target object.

[0074] The specific process for active authorization is as follows:

[0075] Active authorization - select the authorized organization (i.e. the target object) - select the authorized database (i.e. the target database) - execute authorization (i.e. configure permissions for the target database for the target object) - save the authorization record - the authorization process ends.

[0076] Specifically, passive authorization refers to an organization (such as the target object described below) applying for permission for a target database.

[0077] In an optional implementation, if a permission application operation of the target object for the target database is received, a permission configuration page of the target database is displayed.

[0078] The target object may be an object that needs to apply for permission to the target database, such as an organization.

[0079] The target object can apply for permissions for the target database by following the steps below:

[0080] refer to Figure 4 , which is a schematic diagram of another database permission configuration page provided by an embodiment of the present disclosure, such as Figure 4 As shown, open the database permission configuration page for the target object and enter the name of the target database in the search box, such as Database 3.

[0081] In the search results, the target object selects the operation control 401 corresponding to database 3, that is, the specific database for which permission is to be applied, and then the permission application operation can be performed.

[0082] Through the above process, the target object can easily select the target database and perform permission application operations.

[0083] S102: Receive a selection operation for the first permission type or the second permission type, and configure permissions for a target database for a target object.

[0084] In the embodiment of the present disclosure, after receiving the permission application operation of the target object for the target database, the following is displayed: Figure 5 The permission configuration page of the target database shown in the figure displays a first permission type and a second permission type on the page, wherein the first permission type and the second permission type are used to configure permissions for the target database for the target object.

[0085] In an optional implementation, a selection operation for the first permission type or the second permission type is received, and an approval form for the target object's permission application for the target database is generated. If the approval form is approved, permissions for the target database are configured for the target object.

[0086] In addition, after the approval form is approved, the corresponding authorization record can also be saved.

[0087] In the embodiment of the present disclosure, in order to improve the security management of the target database, after receiving the selected operation for the first permission type or the second permission type, the following is generated: Figure 6 The approval form for the target object's permission application for the target database is shown. The approval reason is displayed in the approval form. If the approval reason meets the preset approval reason, the approval form is approved, and the permission for the target database is configured for the target object.

[0088] Furthermore, in the process of configuring permissions for the target object to the target database, if the target database is a database managed based on a limited account, the permissions of the target object to the target database need to be verified before configuring permissions for the target object to the target database.

[0089] In an optional implementation, a selection operation for the first permission type or the second permission type is received, permissions of the target object for the target database are verified, and if the verification passes, permissions for the target database are configured for the target object.

[0090] In the embodiment of the present disclosure, taking receiving a selection operation for a first permission type as an example, verifying the permission of the target object for the target database refers to verifying whether the target object has the permission of the first permission type for the target database.

[0091] refer to Figure 7 , which is a flow chart of another permission management method provided by an embodiment of the present disclosure, such as Figure 7 The figure shows virtual authorization. For a database with strict management, accounts cannot be created at will (i.e., a database managed by restricted accounts). In this case, the account corresponding to the organization becomes a virtual account.

[0092] For ease of understanding, the target object is organization 1. Account 1 corresponding to organization 1 cannot directly connect to the target database. Instead, it is based on the actual account corresponding to account 1. When the actual account is used by organization 1, the permissions of organization 1 will be verified. Based on the permission verification result, it is determined whether permissions for the target database are configured for organization 1.

[0093] Specifically, it is possible to query in the authorization record whether there is a permission record of the target object for the target database. If so, the verification is successful, otherwise, the verification fails.

[0094] The authorization records may be derived from the authorization records saved by the above-mentioned active authorization and passive authorization.

[0095] In addition, for databases such as MySQL, multiple accounts can be created to grant different permissions, such as Figure 8 As shown, each organization can have its own actual account. Taking the target object as organization 2, for example, organization 2 can directly connect to the database through account 2 (i.e., the actual account), and the actual account and the actual authority are consistent with each other. This type of authority is called actual authorization, and the authority control is relatively strict.

[0096] The specific authorization process is as follows:

[0097] Start - Data verification (i.e. verifying whether the target database exists) - Verification passed - Get the target database connection - Execute the authorization statement (i.e. configure the permissions for the target database for the target object) - End.

[0098] Start--Data verification--Verification failed--End.

[0099] The actual authorization will go to the database to execute specific authorization statements:

[0100] 1) Authorization statement corresponding to full permission (i.e. the first permission type):

[0101] GRANT SELECT,INSERT,UPDATE,DELETE ON testdb.*TO'test_user'@'localhost'IDENTIFIED BY'jack'.

[0102] 2) Authorization statement corresponding to the query permission (i.e. the second permission type):

[0103] GRANT SELECT ON testdb.testtable to'test_user'@'localhost'IDENTIFIEDBY'jack'.

[0104] After configuring the permission for the target database for the target object, in an optional implementation, a permission revocation operation for the target database is received to revoke the permission for the target database configured for the target object.

[0105] In the embodiment of the present disclosure, after receiving the permission reclaiming operation for the target database, the permission of the target database configured for the target object may be reclaimed.

[0106] Specifically, Figure 2 As shown, taking the target database as database 1 as an example, after receiving Figure 2 After the triggering operation of the deletion control is shown, the first permission type corresponding to the database 1 can be reclaimed.

[0107] In the permission management method provided by the embodiment of the present disclosure, if a permission management operation for a target database is received, a permission configuration page for the target database is displayed; wherein the permission configuration page includes a first permission type and a second permission type, the first permission type and the second permission type are used to configure permissions for the target database for the target object, receive a selection operation for the first permission type or the second permission type, and configure permissions for the target database for the target object. It can be seen that the embodiment of the present disclosure can configure permissions of the first permission type or the second permission type for the target database for the target object, enriching the way of configuring permissions for the target database for the target object.

[0108] In some embodiments of the present disclosure, if a permission management operation for a target data table is received, a permission configuration page for the target data table is displayed, a selected operation for query permission is received, and query permission for the target data table is configured for the target object.

[0109] The target data table includes a table in a target database or a view in a target database, and the permission configuration page includes query permissions, which are used to configure query permissions for the target data table for the target object.

[0110] In the disclosed embodiment, the method of configuring query permissions for the target data table for the target object is similar to the above-mentioned method of configuring permissions for the target database for the target object. For details, please refer to the description of configuring permissions for the target database for the target object.

[0111] In some embodiments of the present disclosure, the target database may include at least one database, the at least one database includes a first database and a second database, and the first database and the second database belong to different database types.

[0112] In the disclosed embodiment, an organization (such as a target object) has an organizational account. In the multi-database permission management, it will be determined whether there is an account identical to the organizational account under each database. If not, an account identical to the organizational account will be automatically created for the corresponding database during the permission management process, thereby facilitating multi-database permission management operations.

[0113] like Fig. 9 As shown, assuming that the first database is database 1 and the second database is database 2, in multi-database permission management, if an organization (such as the target object) has an organizational account, assuming that there is no account identical to the organizational account under database 1, then in the permission management process, an account identical to the organizational account (i.e., database account 1) is automatically created for database 1. By automatically creating the same account, it can be ensured that the same account is used for permission management in multiple databases.

[0114] The above method can help platform administrators better manage the database and maintain data security.

[0115] First, through the interface operation, users do not need to worry about the writing of structured query language SQL, which improves the quality of data operation. Secondly, the embodiment of the present disclosure is applicable to many databases, including various relational databases, which is convenient for platform administrators to develop data. Thirdly, the embodiment of the present disclosure can clearly see the permissions of the database (such as Figure 2 As shown), improving data development efficiency.

[0116] In practical applications, the embodiments of the present disclosure provide a method of active authorization and passive authorization. The method is applicable to a variety of databases to obtain permission management by establishing different database models. At the same time, the embodiments of the present disclosure can perform authorization (i.e., permission management) on databases and data tables (tables in the database or views in the database). Users can manage permissions through a graphical interface, which is convenient for users to coordinate data permissions and provide a solid foundation for subsequent data processing and merging.

[0117] Data source system description:

[0118] For schema-less data sources, such as MySQL, the data source directly contains the database database, and under the database are data tables (i.e., tables in the database and views in the database). For this type of data source, the main permissions control is for database, table, and view.

[0119] For data sources with schemas, such as the advanced enterprise-level open source relational database PostgreSQL, under the data source is the database, then the schema, and under the schema are data tables (i.e., tables and views in the database). For this type of data source, the main permission control is for schemas, tables, and views. Specifically, the permission control for schemas is handled in the same way as that for databases.

[0120] Based on the above method embodiment, the present disclosure also provides a rights management device, referring to Fig.10 , is a schematic diagram of the structure of a rights management device provided by an embodiment of the present disclosure, the device comprising:

[0121] The first display module 1001 is used to display a permission configuration page of the target database when receiving a permission management operation for the target database; wherein the permission configuration page includes a first permission type and a second permission type, and the first permission type and the second permission type are used to configure permissions for the target object for the target database;

[0122] The first configuration module 1002 is used to receive a selection operation for the first permission type or the second permission type, and configure permissions for the target database for the target object.

[0123] In an optional implementation manner, the first display module 1001 is specifically used for:

[0124] If a permission configuration operation of a target database for a target object is received from a platform administrator, a permission configuration page of the target database is displayed.

[0125] In an optional implementation manner, the first display module 1001 is specifically used for:

[0126] If a permission application operation of the target object for the target database is received, a permission configuration page of the target database is displayed;

[0127] Accordingly, the first configuration module 1002 includes:

[0128] A generating submodule, configured to receive a selection operation for the first permission type or the second permission type, and generate an approval form for the permission application of the target object for the target database;

[0129] The configuration submodule is used to configure permissions for the target database for the target object when the approval form is approved.

[0130] In an optional implementation manner, the target database is a database managed based on a limited account, and the first configuration module 1002 is specifically used to:

[0131] A selection operation for the first permission type or the second permission type is received, and permissions of the target object for the target database are verified. If the verification passes, permissions for the target database are configured for the target object.

[0132] In an optional implementation, the target database includes at least one database, the at least one database includes a first database and a second database, and the first database and the second database belong to different database types.

[0133] In an optional implementation, the device further includes:

[0134] The recovery module is used to receive a permission recovery operation for the target database, and recover the permission of the target database configured for the target object.

[0135] In an optional implementation, the device further includes:

[0136] A second display module is used to display a permission configuration page of the target data table when receiving a permission management operation for the target data table; wherein the target data table includes a table in the target database or a view in the target database, and the permission configuration page includes a query permission, and the query permission is used to configure a query permission for the target object for the target data table;

[0137] The second configuration module is used to receive a selection operation for the query permission and configure the query permission for the target data table for the target object.

[0138] In the permission management device provided by the embodiment of the present disclosure, if a permission management operation for a target database is received, a permission configuration page for the target database is displayed; wherein the permission configuration page includes a first permission type and a second permission type, the first permission type and the second permission type are used to configure permissions for the target database for the target object, receive a selection operation for the first permission type or the second permission type, and configure permissions for the target database for the target object. It can be seen that the embodiment of the present disclosure can configure permissions of the first permission type or permissions of the second permission type for the target database for the target object, enriching the way of configuring permissions for the target database for the target object.

[0139] In addition to the above-mentioned method and apparatus, the embodiments of the present disclosure further provide a computer-readable storage medium, in which instructions are stored. When the instructions are executed on a terminal device, the terminal device implements the permission management method described in the embodiments of the present disclosure.

[0140] The embodiments of the present disclosure further provide a computer program product, which includes a computer program / instructions. When the computer program / instructions are executed by a processor, the permission management method described in the embodiments of the present disclosure is implemented.

[0141] In addition, the present disclosure also provides a rights management device, see Fig.11 As shown, this may include:

[0142] Processor 1101, memory 1102, input device 1103 and output device 1104. The number of processors 1101 in the rights management device can be one or more. Fig.11 In some embodiments of the present disclosure, the processor 1101, the memory 1102, the input device 1103 and the output device 1104 may be connected via a bus or other means, wherein: Fig.11 The example of connecting through bus is taken in the following.

[0143] The memory 1102 can be used to store software programs and modules. The processor 1101 executes various functional applications and data processing of the rights management device by running the software programs and modules stored in the memory 1102. The memory 1102 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, at least one application required for a function, etc. In addition, the memory 1102 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage device. The input device 1103 may be used to receive input digital or character information, and to generate signal input related to user settings and function control of the rights management device.

[0144] Specifically in this embodiment, the processor 1101 will load the executable files corresponding to the processes of one or more applications into the memory 1102 according to the following instructions, and the processor 1101 will run the applications stored in the memory 1102, thereby realizing the various functions of the above-mentioned permission management device.

[0145] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0146] The above description is only a specific embodiment of the present disclosure, so that those skilled in the art can understand or implement the present disclosure. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to the embodiments described herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A rights management method, characterized in that: The method comprises: If a permission management operation for a target database is received, a permission configuration page for the target database is displayed; wherein the permission configuration page includes a first permission type and a second permission type, and the first permission type and the second permission type are used to configure permissions for the target object for the target database; A selection operation for the first permission type or the second permission type is received, and permissions for the target object on the target database are configured.

2. The method according to claim 1, characterized in that: If a permission management operation for a target database is received, a permission configuration page for the target database is displayed, including: If a permission configuration operation of a target database for a target object is received from a platform administrator, a permission configuration page of the target database is displayed.

3. The method according to claim 1, characterized in that: If a permission management operation for a target database is received, a permission configuration page for the target database is displayed, including: If a permission application operation of the target object for the target database is received, a permission configuration page of the target database is displayed; Accordingly, the receiving a selected operation for the first permission type or the second permission type and configuring permissions for the target object for the target database includes: receiving a selection operation for the first permission type or the second permission type, and generating an approval form for the permission application of the target object for the target database; If the approval form is approved, the permissions for the target database are configured for the target object.

4. The method according to claim 1, characterized in that: The target database is a database managed based on a limited account, and the receiving a selected operation for the first permission type or the second permission type, and configuring permissions for the target database for the target object, includes: A selection operation for the first permission type or the second permission type is received, and permissions of the target object for the target database are verified. If the verification passes, permissions for the target database are configured for the target object.

5. The method according to claim 1, characterized in that The target database includes at least one database, and the at least one database includes a first database and a second database, and the first database and the second database belong to different database types.

6. The method according to claim 1, characterized in that After receiving the selected operation for the first permission type or the second permission type and configuring the permission for the target object for the target database, the method further includes: A permission reclaiming operation for the target database is received, and the permission of the target database configured for the target object is reclaimed.

7. The method according to claim 1, characterized in that The method further comprises: If a permission management operation for a target data table is received, a permission configuration page for the target data table is displayed; wherein the target data table includes a table in a target database or a view in the target database, and the permission configuration page includes a query permission, and the query permission is used to configure a query permission for the target object for the target data table; A selection operation for the query permission is received, and the query permission for the target data table is configured for the target object.

8. A rights management device, characterized in that: The device comprises: A first display module, configured to display a permission configuration page of the target database upon receiving a permission management operation for the target database; wherein the permission configuration page includes a first permission type and a second permission type, and the first permission type and the second permission type are used to configure permissions for the target object for the target database; The first configuration module is used to receive a selected operation for the first permission type or the second permission type, and configure permissions for the target database for the target object.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed on a terminal device, the terminal device implements the method according to any one of claims 1 to 8.

10. A rights management device, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the method according to any one of claims 1 to 8 is implemented.

Citation Information

Patent Citations

  • Permission processing method, electronic equipment and storage medium

    CN113407918A

  • Authority control method and system, electronic equipment and storage medium

    CN114741705A

  • Method and device for processing data generated by distributed system, equipment and medium

    CN118093716A

  • Data authority control method, computer equipment and computer storage medium

    CN118228223A

  • Data filtering method and related device

    CN118395471A