Project cloud permission management method and device, electronic equipment and storage medium

Abstract

This invention relates to artificial intelligence and discloses a project cloud permission management method, comprising: acquiring service projects to be managed under cloud permissions; defining the hierarchical directory of each project within the service projects; identifying the project attributes of each project within the service projects; calculating the project weight of each project within the service projects based on the project attributes; classifying the project permission level of each project within the service projects based on the hierarchical directory and project weight; querying user roles of the service projects and constructing a relationship mapping table between user roles and project permission levels; receiving project users to be assigned permissions; querying the project roles of the project users; matching the project roles with the user roles in the relationship mapping table; and when a project role successfully matches a user role in the relationship mapping table, using the project permission level corresponding to the user role as the project viewing level for the project user. This invention can realize multi-level permission management for multi-tenant cloud service projects under different scenarios and needs.

Description

Technical Field

[0001] This invention relates to the field of artificial intelligence, and in particular to a project cloud access control method, apparatus, electronic device, and storage medium. Background Technology

[0002] With the development of information technology, cloud technology has gradually become the mainstream method for storing service items. In the process of storing service items through cloud technology, in order to ensure the data privacy and security of the service items, permissions are usually distributed to the users corresponding to the service items in order to achieve secure management of the service items.

[0003] Currently, cloud permissions for service projects are typically implemented using the RBAC (User-Role-Permission) permission management process. This involves authorizing roles for users associated with service projects and configuring the permissions that roles have. However, this permission model lacks a user authorization role configuration template that can balance generality and flexible configuration. As a result, when authorizing user roles for service projects, permission configuration needs to be done according to different user identities, making the configuration of cloud permissions for service projects cumbersome and requiring a lot of permissions. Summary of the Invention

[0004] To address the aforementioned technical problems, or at least partially address them, this application provides a project cloud permission management method, apparatus, electronic device, and storage medium, which can realize multi-level permission management for multi-tenant cloud service projects under different scenarios and requirements.

[0005] In a first aspect, the present invention provides a project cloud access control method, comprising:

[0006] Obtain the service items to be managed by cloud permissions, define the hierarchical directory of each item in the service items, identify the project attributes of each item in the service items, and calculate the project weight of each item in the service items based on the project attributes;

[0007] Based on the hierarchical directory and the project weight, the project permission level of each project in the service project is determined;

[0008] Query the user roles of the service items and construct a mapping table between the user roles and the permission levels of the items;

[0009] Receive project users whose permissions are to be distributed, query the project roles of the project users, and match the project roles with the user roles in the relationship mapping table;

[0010] When the project role successfully matches the user role in the relationship mapping table, the project permission level corresponding to the user role is used as the project viewing level of the project user.

[0011] In one possible implementation of the first aspect, defining the hierarchical directory of each item in the service project includes:

[0012] Identify the permission functions of each item in the project service project;

[0013] Based on the aforementioned permission functions, each project in the project service project is divided into hierarchical levels to obtain the hierarchical directory.

[0014] In one possible implementation of the first aspect, calculating the project weight of each project in the service project based on the project attributes includes:

[0015] Obtain the source code of each project in the service project, extract the code tags of the source code, and query the number of times the code tags are matched;

[0016] The project weight of each project in the service project is calculated based on the number of hits.

[0017] In one possible implementation of the first aspect, calculating the project weight of each project in the service project based on the number of hits includes:

[0018] The project weight of each item in the service projects is calculated using the following formula:

[0019]

[0020] Among them, P i Indicates the project weight, u 2 This represents the u-th item in the service project, m. i 2 This represents the number of hits in the service project.

[0021] In one possible implementation of the first aspect, the user role for querying the service item includes:

[0022] Obtain user data for the service item, and query user configuration information for the service item based on the user data;

[0023] The user roles are obtained by analyzing the user configuration information.

[0024] In one possible implementation of the first aspect, constructing the mapping table between the user roles and the project permission levels includes:

[0025] Obtain the relationship information between the user role and the project permission level, configure the data component of the relationship information, and create a table canvas of the user role and the project permission level;

[0026] Load the data component into the table canvas to obtain a mapping table of the relationship between the user role and the project permission level.

[0027] In one possible implementation of the first aspect, matching the project role with the user role in the relationship mapping table includes:

[0028] The following formula is used to match the project roles with the user roles in the relationship mapping table, including:

[0029]

[0030] Where R represents the matching result, A i B represents the role of the i-th project. i Let represent the i-th user role in the relational mapping table, n represent the n-th project in the project roles, and m represent the m-th project in the relational mapping table.

[0031] Secondly, the present invention provides a project cloud access control device, the device comprising:

[0032] The weight calculation module is used to obtain the service items to be managed by cloud permissions, define the hierarchical directory of each item in the service items, identify the project attributes of each item in the service items, and calculate the project weight of each item in the service items based on the project attributes.

[0033] The hierarchy module is used to classify the project permission level of each project in the service project according to the hierarchical directory and the project weight;

[0034] The relationship mapping module is used to query the user roles of the service items and construct a relationship mapping table between the user roles and the permission levels of the items;

[0035] The role matching module is used to receive project users whose permissions are to be distributed, query the project users' project roles, and match the project roles with the user roles in the relationship mapping table.

[0036] The level viewing module is used to set the project permission level corresponding to the user role as the project viewing level of the project user when the project role is successfully matched with the user role in the relationship mapping table.

[0037] Thirdly, the present invention provides an electronic device, comprising:

[0038] At least one processor; and a memory communicatively connected to said at least one processor;

[0039] The memory stores a computer program that can be executed by the at least one processor, enabling the at least one processor to execute the project cloud access control method as described in any of the first aspects above.

[0040] Fourthly, the present invention provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the project cloud permission management method as described in any one of the first aspects above.

[0041] Compared with existing technologies, the technical principles and beneficial effects of this solution are as follows:

[0042] This solution first obtains the service items to be managed by cloud permissions, which allows understanding of the various service requirements of these items. Defining the hierarchical directory of each item within the service items enables more detailed classification of the service items, facilitating subsequent authorization and management. Identifying the project attributes of each item within the service items determines their characteristics, thus clarifying their proportion or importance. Second, by calculating the project weight of each item based on the project attributes, this embodiment clarifies the project level of each item, providing a prerequisite for determining subsequent permission levels. Classifying the permission levels of each item within the service items provides a clearer understanding of the role permission levels for subsequent service providers, facilitating subsequent permission allocation and management. Furthermore, querying the user roles of the service items allows for role location, ensuring the construction of a mapping table between user roles and project permission levels. This mapping table allows for convenient viewing of the correspondence between user roles and project permission levels. Matching project roles with user roles in the mapping table reveals the permission level of the user in the project. Therefore, the project cloud permission management method, device, electronic device and storage medium proposed in this embodiment of the invention can realize multi-level permission management for multi-tenant cloud service projects under different scenarios and different needs. Attached Figure Description

[0043] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0044] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0045] Figure 1 This is a flowchart illustrating a project cloud permission management method according to an embodiment of the present invention;

[0046] Figure 2 This is a schematic diagram of a project cloud permission management device according to an embodiment of the present invention;

[0047] Figure 3 This is a schematic diagram of the internal structure of an electronic device that implements a project cloud permission management method according to an embodiment of the present invention. Detailed Implementation

[0048] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0049] This invention provides a project cloud permission management method. The execution subject of this method includes, but is not limited to, at least one of the following: a server, a terminal, or other electronic devices that can be configured to execute the method provided in this invention. In other words, the project cloud permission management method can be executed by software or hardware installed on a terminal device or a server device. The software can be a blockchain platform. The server includes, but is not limited to, a single server, a server cluster, a cloud server, or a cloud server cluster. The server can be an independent server or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0050] See Figure 1 The diagram shown is a flowchart illustrating a project cloud permission management method according to an embodiment of the present invention. Figure 1 The project cloud permission management method described in the document includes the following steps S1-S5:

[0051] S1. Obtain the service items to be managed by cloud permissions, define the hierarchical directory of each item in the service items, identify the project attributes of each item in the service items, and calculate the project weight of each item in the service items based on the project attributes.

[0052] By acquiring the service items to be managed by cloud permissions, this embodiment of the invention can understand the various service requirements of the service items. The cloud permissions refer to user management permissions and cloud resource permissions. The service items refer to business items generated in different business scenarios. For example, in the e-commerce order scenario, the service items include order after-sales service and order inquiry. In the car insurance claim scenario, the service items include claim conditions and claim scope.

[0053] Furthermore, in this embodiment of the invention, by defining a hierarchical directory for each item in the service project, the service projects can be divided into more detailed categories to facilitate the subsequent authorization and management of the service projects. The hierarchical directory refers to the level position of each item in the service project.

[0054] As an embodiment of the present invention, defining the hierarchical directory of each item in the service project includes: identifying the permission functions of each item in the service project, and dividing each item in the service project into hierarchical levels according to the permission functions to obtain the hierarchical directory.

[0055] The permission function refers to the function or capability of the permission corresponding to each project in the service project. Optionally, the permission function of each project in the service project is identified by querying a preset project function permission table, and the hierarchical division of all projects according to the permission function is performed by the pre-defined hierarchical division rules.

[0056] Furthermore, by identifying the project attributes of each project in the service project, the characteristics of each project can be determined, thereby clarifying the proportion or importance of each project in the service project. The project attributes refer to the dimensional information used to characterize the corresponding project, such as category, ID, and time.

[0057] Furthermore, by calculating the project weight of each project in the service project based on the project attributes, the project level of each project can be clearly defined, which can serve as a prerequisite for determining the permission level. The project weight refers to the proportion or importance of each project in the total number of projects in the service project.

[0058] As an embodiment of the present invention, the step of calculating the project weight of each project in the service project according to the project attributes includes: obtaining the project source code of each project in the service project, extracting the code tags of the project source code, querying the number of query hits of the code tags, and calculating the project weight of each project in the service project based on the number of hits.

[0059] The project source code refers to the initial compiled code of the project file, the code tag refers to a special symbol added when the code is created, which has the function of indication and identification, and the hit count refers to the corresponding number of times the project tag appears in the search engine of the cloud system.

[0060] Optionally, the source code of each project in the service project can be obtained by directly viewing the properties function of the project page; the code tags of the project source code can be extracted by an HTML code tag extraction tool; and the query hit count of the project tags can be achieved by a query counting toolkit, which can be compiled using the JAVA language.

[0061] Furthermore, in an optional embodiment of the present invention, the project weight of each project in the service project is calculated using the following formula based on the number of hits:

[0062]

[0063] Among them, P i Indicates the project weight, u 2 This represents the u-th item in the service project, m. i 2 This represents the number of hits in the service project.

[0064] S2. Based on the hierarchical directory and the project weight, classify the project permission level of each project in the service project.

[0065] The embodiments of the present invention, by dividing the project permission levels of each project in the service projects, can more clearly understand the role permission levels for subsequent project services, so as to facilitate the subsequent allocation and management of permissions;

[0066] As an embodiment of the present invention, the step of dividing the project permission level of each project in the service project according to the hierarchical directory and the project weight includes: creating a weight value data table according to the hierarchical directory and the project weight, recording the weight values ​​in the weight value data table, and obtaining the project permission level according to the weight value data table and the hierarchical directory.

[0067] The weight value data table refers to a data list that records or statistically analyzes the weight values. Optionally, the weight value data table is created using a data table creation program in the cloud system, which can be generated using HTML programming language. The weight values ​​are recorded in the weight value data table using storage media in the cloud system. The project permission level is obtained by combining the weight value data table with the hierarchical directory and then dividing the permissions according to predefined permission level division rules.

[0068] S3. Query the user roles of the service items and construct a mapping table between the user roles and the permission levels of the items.

[0069] In this embodiment of the invention, by querying the user roles of the service project, the role can be located, which is a prerequisite for the construction of the mapping table of the relationship between user roles and the permission level of the project. The user role can be understood as a special label defined by the system for the user, such as engineer, supervisor, director, etc.

[0070] As an embodiment of the present invention, the step of querying the user role of the service item includes: obtaining user data of the service item, querying user configuration information of the service item based on the user data, and analyzing the user configuration information to obtain the user role.

[0071] The user data refers to the user's information data, and the configuration information refers to the specific content configured for the user. Optionally, the user data of the service item is obtained by extracting it from the system's project database, and the user configuration information of the service item is queried through a user information query interface, such as an SQL interface.

[0072] Furthermore, this embodiment of the invention constructs a mapping table between user roles and project permission levels, allowing for a more convenient viewing of the correspondence between user roles and project permission levels in a tabular format. The mapping table refers to a data table reflecting the correspondence between the two.

[0073] Furthermore, as an embodiment of the present invention, constructing the relationship mapping table between the user role and the project permission level includes: obtaining the relationship information between the user role and the project permission level, configuring the data component of the relationship information, creating a table canvas of the user role and the project permission level, loading the data component into the table canvas, and obtaining the relationship mapping table between the user role and the project permission level.

[0074] The relationship information refers to information reflecting the connection and common characteristics between the two; the component refers to a part that encapsulates data and methods; and the table canvas refers to a blank user interface that can be used to place the component. Optionally, the relationship information between the user role and the project permission level is obtained by obtaining it from the system information database; the data component is generated by a JavaScript language component generation function; and the table canvas is generated by a system interface creation program.

[0075] S4. Receive the project users whose permissions are to be distributed, query the project roles of the project users, and match the project roles with the user roles in the relationship mapping table.

[0076] In this embodiment of the invention, the project user receiving the permission to be distributed can determine the object of the subsequent permission to be distributed. Optionally, the project user receiving the permission to be distributed receives it through the project information receiving port of the cloud system. Further, in this embodiment of the invention, the user's permission level can be determined by querying the project user's project role. The project role refers to the level positioning of the project. The method of querying the project user's project role is the same as the method of querying the user role of the service project described in s3, and will not be described in detail here.

[0077] Furthermore, in this embodiment of the invention, by matching the project role with the user role in the relationship mapping table, the permission level of the project user can be determined through the matching result.

[0078] Furthermore, as an embodiment of the present invention, the project role is matched with the user role in the relationship mapping table using the following formula, including:

[0079]

[0080] Where R represents the matching result, A i B represents the role of the i-th project. i Let represent the i-th user role in the relational mapping table, n represent the n-th project in the project roles, and m represent the m-th project in the relational mapping table.

[0081] S5. When the project role is successfully matched with the user role in the relationship mapping table, the project permission level corresponding to the user role is used as the project viewing level of the project user.

[0082] It should be understood that when the project role is successfully matched with the user role in the relationship mapping table, it means that the project role and the role in the relationship mapping table are all corresponding and the information is correct. The subsequent allocation of the permission level of the service project can be carried out in this way. Therefore, by using the project permission level corresponding to the user role as the project viewing level of the project user, the embodiments of the present invention can realize multi-level permission management for multi-tenant cloud service projects under different scenarios and different needs.

[0083] As can be seen, this solution first obtains the service items to be managed by cloud permissions, thereby understanding the various service requirements of the service items. Defining the hierarchical directory of each item in the service items allows for a more detailed division of the service items, facilitating subsequent authorization and management. Identifying the project attributes of each item in the service items determines the characteristics of each item, thus clarifying the proportion or importance of each item in the service items. Secondly, by calculating the project weight of each item in the service items based on the project attributes, the project level of each item can be clarified, providing a prerequisite for determining the permission level. Dividing the project permission levels of each item in the service items allows for a clearer understanding of the role permission levels for subsequent project services, facilitating subsequent permission allocation and management. Furthermore, querying the user roles of the service items allows for the location of roles, ensuring the construction of a mapping table between user roles and project permission levels. This mapping table allows for convenient viewing of the correspondence between user roles and project permission levels in a tabular format. Matching project roles with user roles in the mapping table reveals the permission level of the project user. Therefore, the project cloud permission management method, device, electronic device and storage medium proposed in this embodiment of the invention can realize multi-level permission management for multi-tenant cloud service projects under different scenarios and different needs.

[0084] like Figure 2 The diagram shown is a functional block diagram of the cloud permission management device of this invention.

[0085] The project cloud permission management device 200 described in this invention can be installed in an electronic device. Depending on the functions implemented, the project cloud permission management device may include a weight calculation module 201, a level classification module 202, a relationship mapping module 203, a role matching module 204, and a level viewing module 205. The module described in this invention can also be called a unit, which refers to a series of computer program segments that can be executed by the processor of an electronic device and can perform a fixed function, and are stored in the memory of the electronic device.

[0086] In this embodiment of the invention, the functions of each module / unit are as follows:

[0087] The weight calculation module 201 is used to obtain the service items to be managed by cloud permissions, define the hierarchical directory of each item in the service items, identify the project attributes of each item in the service items, and calculate the project weight of each item in the service items based on the project attributes.

[0088] The level classification module 202 is used to classify the project permission level of each project in the service project according to the hierarchical directory and the project weight;

[0089] The relationship mapping module 203 is used to query the user roles of the service items and construct a relationship mapping table between the user roles and the permission levels of the items.

[0090] The role matching module 204 is used to receive project users whose permissions are to be distributed, query the project users' project roles, and match the project roles with the user roles in the relationship mapping table.

[0091] The level viewing module 205 is used to, when the project role and the user role in the relationship mapping table are successfully matched, use the project permission level corresponding to the user role as the project viewing level of the project user.

[0092] In detail, the modules in the project cloud permission management device 200 described in this embodiment of the invention adopt the same usage as described above. Figure 1 The project cloud permission management method described herein uses the same technical means and can produce the same technical effect, so it will not be repeated here.

[0093] like Figure 3 The diagram shown is a structural schematic of the electronic device that implements the project cloud permission management method of the present invention.

[0094] The electronic device may include a processor 30, a memory 31, a communication bus 32, and a communication interface 33. It may also include a computer program, such as a project cloud access control program, stored in the memory 31 and capable of running on the processor 30.

[0095] In some embodiments, the processor 30 may be composed of integrated circuits, such as a single packaged integrated circuit or multiple integrated circuits with the same or different functions, including combinations of one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and various control chips. The processor 30 is the control unit of the electronic device, connecting various components of the entire electronic device through various interfaces and lines. It executes programs or modules stored in the memory 31 (e.g., executing a project cloud permission management program) and calls data stored in the memory 31 to perform various functions of the electronic device and process data.

[0096] The memory 31 includes at least one type of readable storage medium, including flash memory, portable hard drive, multimedia card, card-type memory (e.g., SD or DX memory), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 31 can be an internal storage unit of an electronic device, such as a portable hard drive. In other embodiments, the memory 31 can be an external storage device of the electronic device, such as a plug-in portable hard drive, Smart Media Card (SMC), Secure Digital (SD) card, Flash Card, etc. Furthermore, the memory 31 can include both internal and external storage units of the electronic device. The memory 31 can be used not only to store application software and various types of data installed on the electronic device, such as the code of a project cloud permission management program, but also to temporarily store data that has been output or will be output.

[0097] The communication bus 32 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be divided into an address bus, a data bus, a control bus, etc. The bus is configured to enable communication between the memory 31 and at least one processor 30, etc.

[0098] The communication interface 33 is used for communication between the aforementioned electronic device and other devices, including a network interface and a user interface. Optionally, the network interface may include a wired interface and / or a wireless interface (such as a Wi-Fi interface, Bluetooth interface, etc.), typically used to establish communication connections between the electronic device and other electronic devices. The user interface may be a display, an input unit (such as a keyboard), or, optionally, a standard wired or wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, or an OLED (Organic Light-Emitting Diode) touchscreen, etc. The display may also be appropriately referred to as a screen or display unit, used to display information processed in the electronic device and to display a visual user interface.

[0099] Figure 3 Only electronic devices with components are shown; it will be understood by those skilled in the art that... Figure 3 The structure shown does not constitute a limitation on the electronic device and may include fewer or more components than shown, or combine certain components, or have different component arrangements.

[0100] For example, although not shown in the figure, the electronic device may also include a power supply (such as a battery) to power the various components. Preferably, the power supply can be logically connected to the at least one processor 30 through a power management device, thereby enabling functions such as charging management, discharging management, and power consumption management. The power supply may also include one or more DC or AC power supplies, recharging devices, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components. The electronic device may also include various sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be elaborated here.

[0101] It should be understood that the embodiments described are for illustrative purposes only and are not limited to this structure in terms of the scope of the patent invention.

[0102] The project cloud permission management program stored in the memory 31 of the electronic device is a combination of multiple computer programs. When run in the processor 30, it can implement the following methods:

[0103] Obtain the service items to be managed by cloud permissions, define the hierarchical directory of each item in the service items, identify the project attributes of each item in the service items, and calculate the project weight of each item in the service items based on the project attributes;

[0104] Based on the hierarchical directory and the project weight, the project permission level of each project in the service project is determined;

[0105] Query the user roles of the service items and construct a mapping table between the user roles and the permission levels of the items;

[0106] Receive project users whose permissions are to be distributed, query the project roles of the project users, and match the project roles with the user roles in the relationship mapping table;

[0107] When the project role successfully matches the user role in the relationship mapping table, the project permission level corresponding to the user role is used as the project viewing level of the project user.

[0108] Specifically, the processor 30's implementation method of the above-mentioned computer program can be found in [reference needed]. Figure 1 The descriptions of the relevant steps in the corresponding embodiments are not repeated here.

[0109] Furthermore, if the modules / units integrated into the electronic device are implemented as software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium. The computer-readable storage medium can be volatile or non-volatile. For example, the computer-readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, or a read-only memory (ROM).

[0110] The present invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor of an electronic device, can implement the following methods:

[0111] Obtain the service items to be managed by cloud permissions, define the hierarchical directory of each item in the service items, identify the project attributes of each item in the service items, and calculate the project weight of each item in the service items based on the project attributes;

[0112] Based on the hierarchical directory and the project weight, the project permission level of each project in the service project is determined;

[0113] Query the user roles of the service items and construct a mapping table between the user roles and the permission levels of the items;

[0114] Receive project users whose permissions are to be distributed, query the project roles of the project users, and match the project roles with the user roles in the relationship mapping table;

[0115] When the project role successfully matches the user role in the relationship mapping table, the project permission level corresponding to the user role is used as the project viewing level of the project user.

[0116] In the several embodiments provided by this invention, it should be understood that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and other division methods may be used in actual implementation.

[0117] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0118] Furthermore, the functional modules in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in the form of hardware plus software functional modules.

[0119] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the present invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the present invention.

[0120] Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of the invention is defined by the appended claims rather than the foregoing description. Thus, all variations falling within the meaning and scope of equivalents of the claims are intended to be embraced within the invention. No appended diagram markings in the claims should be construed as limiting the scope of the claims.

[0121] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0122] The above description is merely a specific embodiment of the present invention, enabling those skilled in the art to understand or implement the invention. Various modifications to these embodiments will be readily 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 invention. Therefore, the present invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features of the invention herein.

Claims

1. A project cloud access control method, characterized in that, The method includes: Obtain the service items to be managed by cloud permissions, define the hierarchical directory of each item in the service items, identify the project attributes of each item in the service items, and calculate the project weight of each item in the service items based on the project attributes; Based on the hierarchical directory and the project weight, create a weight value data table, record the weight value of the project weight in the weight value data table, and obtain the project permission level based on the weight value data table and the hierarchical directory; Query the user roles of the service items, obtain the relationship information between the user roles and the permission levels of the items, configure the data components of the relationship information, create a table canvas of the user roles and the permission levels of the items, load the data components into the table canvas, and obtain the relationship mapping table of the user roles and the permission levels of the items. Receive project users whose permissions are to be distributed, query the project roles of the project users, and match the project roles with the user roles in the relationship mapping table; When the project role successfully matches the user role in the relationship mapping table, the project permission level corresponding to the user role is used as the project viewing level of the project user.

2. The method according to claim 1, characterized in that, The definition of the hierarchical directory for each project in the service project includes: Identify the permission functions of each item in the project service project; Based on the aforementioned permission functions, each project in the project service project is divided into hierarchical levels to obtain the hierarchical directory.

3. The method according to claim 1, characterized in that, The step of calculating the project weight of each project in the service project based on the project attributes includes: Obtain the source code of each project in the service project, extract the code tags of the source code, and query the number of times the code tags are matched; The project weight of each project in the service project is calculated based on the number of hits.

4. The method according to claim 1, characterized in that, The user roles for querying the service include: Obtain user data for the service item, and query user configuration information for the service item based on the user data; The user roles are obtained by analyzing the user configuration information.

5. The method according to claim 1, characterized in that, The step of matching the project role with the user role in the relationship mapping table includes: The following formula is used to match the project roles with the user roles in the relationship mapping table, including: Wherein, R represents the matching result. This represents the role of the i-th project. Let represent the i-th user role in the relational mapping table, n represent the n-th project in the project roles, and m represent the m-th project in the relational mapping table.

6. A project cloud access control device, characterized in that, The device includes: The weight calculation module is used to obtain the service items to be managed by cloud permissions, define the hierarchical directory of each item in the service items, identify the project attributes of each item in the service items, and calculate the project weight of each item in the service items based on the project attributes. The level classification module is used to create a weight value data table based on the hierarchical directory and the project weight, record the weight value of the project weight in the weight value data table, and obtain the project permission level based on the weight value data table and the hierarchical directory. The relationship mapping module is used to query the user roles of the service project, obtain the relationship information between the user roles and the project permission levels, configure the data components of the relationship information, create a table canvas of the user roles and the project permission levels, load the data components into the table canvas, and obtain the relationship mapping table of the user roles and the project permission levels. The role matching module is used to receive project users whose permissions are to be distributed, query the project users' project roles, and match the project roles with the user roles in the relationship mapping table. The level viewing module is used to set the project permission level corresponding to the user role as the project viewing level of the project user when the project role is successfully matched with the user role in the relationship mapping table.

7. An electronic device, characterized in that, The electronic device includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the project cloud access control method as described in any one of claims 1 to 5.

8. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements a project cloud permission management method as described in any one of claims 1 to 5.

Images