Rights management platform, method, server and storage medium
By introducing a permission management platform into embedded products, fine-grained access control at all levels in the project is solved, and traditional methods cannot meet the security and controllability of embedded products are improved. The security and security of embedded products are improved. Controllability.
Patent Information
- Application Number
- CN202311663027.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-12-05
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2043-12-05
AI Technical Summary
Traditional role-based access control methods are difficult to achieve fine-grained access control in embedded products and cannot meet the security and controllability requirements of embedded products.
Provide a permission management platform, including project permission management unit, product and package permission management unit and file permission management unit. By controlling permissions at all levels in the project, it allows setting permissions at specific levels according to different users and roles to achieve detailed implementation Granular access control.
It improves the security and controllability of embedded products and meets the fine-grained access control needs of application scenarios.
Smart Images

Figure CN117592083B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of server technology, and in particular to a rights management platform, method, server and storage medium. Background Art
[0002] Since embedded products are widely used in various scenarios with precise working requirements, such as industrial control and smart home, fine-grained permission management is very important in embedded products to ensure that only authorized entities can access and / or operate resources. The resources of embedded devices include projects, products, packages, and files.
[0003] Traditional permission management methods, such as role-based access control (RBAC), usually perform access control based on roles. However, the role-based access control method has limitations in fine-grained control. This method is achieved by assigning permissions to roles and mapping roles to resources, and the above mapping is coarse-grained.
[0004] During the development of embedded products, fine-grained control is required for each level of the project. However, the traditional permission management method cannot perform fine-grained access control on the hierarchical structure within each project, which makes it difficult for the security and controllability of embedded products to meet the requirements of application scenarios. Summary of the invention
[0005] The present application provides a permission management platform, method, server and storage medium, which solves the problem that it is difficult to implement fine-grained access control on the hierarchical structure within the project. This solution can define the project hierarchically and involve permission control at each level to achieve fine-grained access control.
[0006] In a first aspect, the present application provides a rights management platform for performing rights management on a server, which includes a project rights management unit, a product and package rights management unit, and a file rights management unit.
[0007] The project authority management unit records the visible attributes of each project and the member information associated with each project. The visible attributes are used to determine the scope of access rights of different users to the project. The member information includes a user ID corresponding to the user and a number of role parameters corresponding to the user ID. The project authority management unit is used to establish a mapping relationship between the role parameters and the project authority and / or product authority, and authenticate the initiator of the access request according to the established mapping relationship.
[0008] The product and package permission management unit is used to determine the target user identifier based on the mapping relationship, configure the package permissions and product permissions of the role parameters corresponding to the target user identifier at each applicable stage and generate a role permission table, the target user identifier includes a number of role parameters corresponding to the product permissions, and the product and package permission management unit is also used to authenticate the package operation of the access request according to the generated role permission table;
[0009] The file permission management unit is used to configure the file permission of the user ID when configuring the package permission.
[0010] In a second aspect, the present application further provides a rights management method, which is applied to the above-mentioned rights management platform, and the method includes:
[0011] In response to the received access request from the initiator to the server, the initiator is authenticated by the project authority management unit to determine whether the initiator has the authority to create the project;
[0012] If the initiator has the authority to create a project, the project is created, and according to the configuration operation of the initiator, the member information of the created project is configured through the project authority management unit to establish a mapping relationship between the role parameters of each user identification and the project authority and / or product authority;
[0013] Configure the role permission table through the product and package permission management unit to determine the package permissions of each role parameter;
[0014] Create products within the project and configure package policies for the products based on predefined configuration information.
[0015] In a third aspect, the present application further provides a server, which includes the above-mentioned rights management platform and further includes:
[0016] one or more processors;
[0017] The storage device is used to store one or more programs. When the one or more programs are executed by one or more processors, the one or more processors implement the above-mentioned permission management method.
[0018] In a fourth aspect, the present application also provides a storage medium storing computer executable instructions, which are used to execute the permission management method as described above when executed by a processor.
[0019] This application uses a permission management platform to control permissions at each level of the project-product-package-file structure in the server. It no longer manages permissions based on a single role, but allows permissions to be set at specific levels within the project based on different users and roles, and implements fine-grained access control for embedded products, so that the security and controllability of the server meet the requirements of the application scenario. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] Figure 1 A schematic diagram of the architecture of a rights management platform provided in one embodiment of the present application;
[0021] Figure 2 A schematic diagram of the steps of a rights management method provided in one embodiment of the present application;
[0022] Figure 3 A schematic diagram of steps for authenticating an access request to create a product provided in an embodiment of the present application;
[0023] Figure 4 A schematic diagram of the steps for performing verification during a package registration process provided in an embodiment of the present application;
[0024] Figure 5 A schematic diagram of steps for authenticating an access request for creating a package provided in an embodiment of the present application;
[0025] Figure 6 A schematic diagram of the structure of a server provided in one embodiment of the present application. DETAILED DESCRIPTION
[0026] The embodiments of the present application are further described in detail below in conjunction with the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are only used to explain the embodiments of the present application, rather than to limit the embodiments of the present application. It should also be noted that, for ease of description, only the parts related to the embodiments of the present application rather than all structures are shown in the accompanying drawings, and those skilled in the art should be able to think of it after reading the specification of this application that as long as the technical features do not contradict each other, any combination of the technical features can constitute an optional implementation method.
[0027] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally a class, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally represents that the objects associated with each other are in an "or" relationship. In the description of the present application, "multiple" means two or more, and "several" means one or more.
[0028] In the server, a project is also called a project, which is used to manage products. Products are intermediate or final products produced during the server development process. It can be imagined that a project includes several products, a product includes several packages, and a package includes several files. For the access control scheme for the above-mentioned projects, products, packages, and files, the relevant technology is through role-based access control, but this scheme is difficult to achieve fine-grained access control at all levels within the project.
[0029] In this regard, this application provides a permission management platform to control access to each level within the project and implement permission management. Figure 1 As shown, Figure 1 This is a schematic diagram of the architecture of a rights management platform provided in an embodiment of the present application. The rights management platform includes a project rights management unit 110 , a product and package rights management unit 120 , and a file rights management unit 130 .
[0030] Each project in the server is set with a corresponding visible attribute to determine the users who can perform access control on the project, that is, different visible attributes correspond to different access rights ranges, and the access rights range is used to determine the users who can perform access control on the project. It can be imagined that for different visible attributes, corresponding visible attribute parameters are set to determine the corresponding users. For example, if the project is visible to all users, the visible attribute parameter can be Public, and then all users have the right to access the project. For example, if the project is visible to some users, the visible attribute parameter can be Private, and then only some users can access the project.
[0031] In this solution, the identifier of the device or terminal that controls access to the server's resources is used as the user identifier. Different user identifiers may correspond to different role parameters to achieve the association of one user with different roles. For example, roles such as developers, managers, anonymous users, non-member users, and ordinary users are set. A user identifier may correspond to the role parameters of any one or more of the above roles to indicate that the user corresponding to the user identifier has one or more roles. In this regard, the above user identifier and the corresponding role parameters of the user identifier may be recorded in member information.
[0032] The project authority management unit 110 records the above-mentioned visible attributes and member information, and the member information is also associated with the project, and the project authority management unit 110 can be used to configure the users who can access the project to define the users associated with the project, and the role parameters corresponding to each user identifier can be mapped with the project authority and / or the role parameters with the product authority, so as to establish a corresponding mapping relationship. In addition, the initiator of the access request can be authenticated according to the established mapping relationship to determine whether the user as the initiator has the corresponding authority.
[0033] Exemplarily, project permissions are permissions that act on projects, which may be permissions such as creating new projects, deleting projects, closing / opening projects, editing projects, and managing; and product permissions are permissions that act on products, which may be permissions such as creating products, querying products, and deleting products. If a user corresponds to multiple roles, that is, his user ID corresponds to multiple role parameters, such as corresponding to developers and managers, then in the process of establishing a mapping relationship through the project permission management unit 110, permissions such as creating new projects, deleting projects, closing / opening projects, and editing projects can be configured corresponding to the role parameters of developers, and permissions such as creating new projects, deleting projects, closing / opening projects, editing projects, and managing can be configured corresponding to the role parameters of managers. Similarly, corresponding product permissions can also be configured, such as permissions such as closing / opening products and creating products. Therefore, when the user accesses the server, the project permission management unit 110 can obtain his user ID and role parameters accordingly, and authenticate the user's permissions based on the established mapping relationship.
[0034] The product and package permission management unit 120 determines the target user ID according to the mapping relationship established in the engineering permission management unit 110. It can be understood that the several role parameters corresponding to the target user ID correspond to the product permissions, that is, the user corresponding to the target user ID has some product permissions. Then, the product and package permission management unit 120 can provide the configuration of the package permissions of the role parameters corresponding to the target user ID at each applicable stage, so as to configure permissions at the package level. Among them, the applicable stage corresponds to different stages in the server development process of the product, such as the development stage, the review stage, the testing stage and the product stage.
[0035] Moreover, after completing the configuration of the above-mentioned package permissions through the product and package permission management unit 120, the product and package permission management unit 120 can output a role permission table to record the product permissions of each role parameter and the package permissions in each applicable stage. For example, package permissions can be to create packages, read packages, update packages, delete packages, product visibility, etc. If a user with the role of "developer" can create packages and update packages in a product with the stage of "development stage", then correspondingly, the role parameters corresponding to the developer, the package permission parameters corresponding to the creation and update of packages, and the applicable stage parameters of the corresponding development stage can be recorded in the role permission table. Therefore, in the process of creating a package, the product and package permission management unit 120 can determine whether the user has the package permission to create a package by obtaining the role permission table.
[0036] It is conceivable that after determining the role permission table corresponding to each role parameter, the role permission table can also be unified and integrated, such as integrated into a permission group, to record the permissions of each role parameter at each applicable stage, so as to facilitate unified management.
[0037] The file permission management unit 130 is used to configure the file permissions of the user identifier when configuring the package permissions, that is, the file permissions integrate the corresponding product permissions and package permissions, and in the process of configuring the package permissions, the file permissions are configured through the file permission management unit 130. It can be imagined that the file permissions are permissions acting on files. For example, file permissions can be permissions such as creating files, reading files, updating files, and deleting files. In the configuration process, the permissions of each user identifier can be set. It can be imagined that there is a corresponding relationship between the user identifier and the role parameter. Therefore, in the configuration process, the file permissions can also be configured through the corresponding role parameters. It should be noted that in some embodiments, the file permissions configured for each user identifier can also be recorded in the form of a permission table.
[0038] From the above solution, it can be seen that in the management of the server, the permission management platform is used to control the permissions of each level in the project-product-package-file structure, and the permissions are no longer managed based on a single role. Instead, it allows permissions to be set for specific levels according to different users and roles within the project, and implements fine-grained access control for embedded products, so that the security and controllability of the server meet the requirements of the application scenario.
[0039] Figure 2 This is a schematic diagram of the steps of a rights management method provided in an embodiment of the present application. The method can be applied to the above-mentioned rights management platform, such as Figure 2 As shown, the specific steps are as follows:
[0040] Step S210: In response to the received access request from the initiator to the server, the project authority management unit authenticates the initiator to determine whether the initiator has the authority to create a project.
[0041] It is understandable that when the user as the initiator performs access control, the server needs to authenticate the permissions of the corresponding user at each level in the project. Therefore, after the server receives the initiator's access request to the server, the server authenticates the initiator through the project permission management unit.
[0042] It can be imagined that the project permission management unit records the mapping relationship between role parameters and project permissions. After determining the user identification of the initiator and the corresponding role parameters, the server can use the mapping relationship recorded in the project permission management unit to judge the permissions corresponding to the above role parameters to determine whether the initiator has the permission to create a project.
[0043] Step S220: If the initiator has the authority to create a project, the project is created, and according to the configuration operation of the initiator, the member information of the created project is configured through the project authority management unit to establish a mapping relationship between the role parameters of each user identifier and the project authority and / or product authority.
[0044] If the initiator has the authority to create a project, the server will create the project accordingly, and can provide the initiator with an interface for configuring member information of the created project, so as to allocate member information associated with the project. The server configures the member information of the created project through the project authority management unit according to the configuration operation of the initiator, and re-establishes the mapping relationship between the role parameters of each user ID and the project authority and / or product authority, such as updating the original mapping relationship or allocating product authority to each user ID.
[0045] Step S230: configuring the role permission table through the product and package permission management unit to determine the package permission of each role parameter.
[0046] After determining the product permissions corresponding to each user, the role permission table can also be configured through the product and package permission management unit to configure the permissions of the role parameters corresponding to each user ID. For example, the role parameters, corresponding package permission parameters, and corresponding applicable stage parameters can be recorded in the role permission table to authenticate each user ID when creating a package.
[0047] Step S240: Create a product in the project, and configure the package policy for the product according to the predefined configuration information to register the package.
[0048] After completing the configuration of package permissions, create a product in the project and enter the product level, so as to configure the package policy in the product for package registration. It can be understood that the package policy configuration is used to configure the version, release type and other attributes of the package created in the product, and then obtain the corresponding file list through package registration, so as to create the corresponding configured package in the product and the corresponding files of the package.
[0049] In some embodiments, the configuration information stored in the product and package authority management unit includes package version parameters, package release type parameters, verification paths, and package permissions. Therefore, in the process of package policy configuration, the server can configure the parameter items of the filtering conditions according to the package version parameters, package release type parameters, verification paths, and package permissions. It can be imagined that the parameter items of the filtering conditions are used to verify the information provided by the initiator of the package creation request during the package registration process, so that the version, release type, etc. of the created package can be predefined through the package policy configuration. Then, in the process of package registration, the parameter items of the filtering conditions are called for verification to determine whether to terminate the registration package.
[0050] It is conceivable that the configuration information pre-stored in the product and package permission management unit defines the package version, package release type, verification path, and package permissions, i.e., the above-mentioned package version parameters, package release type parameters, verification path, and package permissions, and then uses this as a filtering condition to determine whether the information provided by the initiator meets the requirements for registering the package. Therefore, after receiving the information provided by the initiator, if the same conditions as the information are detected in the filtering conditions, it can be considered that the initiator has the permission to register the package, so as to perform the operation of registering the package.
[0051] From the above solution, it can be seen that based on the permission management platform, server developers can set permissions for each level within the project according to different users and roles within the project, and implement fine-grained access control for embedded products, so as to improve the security and controllability of the server.
[0052] Figure 3 A schematic diagram of the steps for authenticating an access request for creating a product provided in an embodiment of the present application. Taking creating a product in a project as an example, the authentication process is shown in the figure. The specific steps are as follows:
[0053] Step S310: The project authority management unit determines whether the member information associated with the project carries the user identification of the initiator of the access request.
[0054] Step S320: If the member information carries the user ID of the initiator of the access request, then based on the mapping relationship established by the project authority management unit, determine whether the role parameter corresponding to the user ID has the authority to create a product.
[0055] Step S330: If the initiator has the authority to create a product, create the product in the project.
[0056] It is understandable that the project authority management unit accesses the project to obtain the member information associated with the project, so as to determine whether the member information includes the user ID of the initiator. In addition, the mapping relationship recorded by the project authority management unit records the product authority corresponding to the role parameter. Therefore, after determining that the member information carries the user ID of the initiator of the access request, the project authority management unit obtains the role parameter of the user ID, and based on the established mapping relationship, determines whether the corresponding role parameter has the authority to create a product, and then creates the product in the project if the initiator has the authority to create a product.
[0057] Exemplarily, the user ID of the initiator has a role parameter corresponding to a developer, and in the mapping relationship, the role parameter corresponding to the developer is configured with permissions such as creating products, querying products, and deleting products. Therefore, when the user ID of the initiator is recorded in the member information corresponding to the project, the project permission management unit can determine that the initiator with the role of developer has the permission to create products by searching the mapping relationship, and then create products in the project.
[0058] Figure 4 A schematic diagram of the steps for verification in the package registration process provided in an embodiment of the present application. The initiator provides corresponding package identification information and file information. The server can perform conditional filtering according to the predefined package policy configuration. The specific steps are as follows:
[0059] Step S410: In response to the package registration operation of the initiator, based on the parameter items of the filtering conditions, a matching check is performed on the package identification information provided in the package registration operation to determine whether the package identification information includes a package version parameter, a package release type parameter, and a package permission.
[0060] Step S420: Based on the parameter items of the filtering condition, a path check is performed on the file information provided in the package registration operation to determine whether the file information includes a check path.
[0061] Step S430: When both the package identification information and the file information pass verification, the package is allowed to be registered.
[0062] It can be understood that each parameter item of the filtering condition corresponds to a predefined package policy configuration, such as the parameter items of the filtering condition include predefined package version parameters, package release type parameters, verification path and package permissions, and the package identification information carries information such as the package version, release type and package permissions. For the package identification information, matching is performed according to the filtering condition, so as to verify the package identification information to determine whether the package identification information includes the package version parameter, package release type parameter and package permissions. Similarly, for file information, the parameter items corresponding to the verification path in the filtering condition are recorded for path verification to determine whether the verification path is included in the file information. Therefore, when both the package identification information and the file information pass the verification, the package is allowed to be registered so as to facilitate the subsequent creation of the package in the product according to the corresponding package policy configuration.
[0063] It should be noted that, in one embodiment, a regular matching algorithm is used when performing path verification to determine whether the file information includes a verification path.
[0064] In some embodiments, the files in the package are stored in a file server, and the file information corresponding to the file is recorded in the rights management platform, so as to access the file server according to the file information, wherein the file information includes the storage path of the file in the file server, the file size, etc. Therefore, the authentication of the file rights is performed through the file server, and the server synchronizes the file rights with the file server based on the file rights recorded by the file rights management unit, so that the file server can authenticate the user identification, thereby ensuring the security of the file.
[0065] Figure 5 A schematic diagram of steps for authenticating an access request for creating a package provided in an embodiment of the present application. Taking creating a package in a product as an example, the authentication process is shown in the figure. The specific steps are as follows:
[0066] Step S510: Obtain member information of the project corresponding to the product through the product and package permission management unit to determine the role parameters of the initiator of the access request.
[0067] Step S520: Based on the role permission table recorded by the product and package permission management unit, authenticate whether the initiator has the permission to create a package according to the role parameters.
[0068] Step S530: If the initiator has the authority to create a package according to the role parameter, a package is created in the product.
[0069] It is understandable that after receiving the corresponding access request, the server determines the role parameters corresponding to the user ID of the initiator through the member information of the project corresponding to the product in the product and package permission management unit. A role permission table is recorded in the product and package permission management unit. After determining the role parameters corresponding to the initiator, it is determined according to the role permission table whether the role parameters corresponding to the initiator have the permission to create a package, so as to create a package in the product if the role parameters corresponding to the initiator have the permission to create a package.
[0070] Exemplarily, the user ID of the initiator has the role parameters corresponding to the developer, and the role parameters corresponding to the developer and the package permission parameters corresponding to the package creation and update are recorded in the role permission table. Accordingly, the product and package permission management unit can determine that the initiator has the permission to create a package according to the role permission table, and then create a package in the product.
[0071] In some embodiments, when creating a child project for an already created project (i.e., a parent project), the server will perform an inheritance operation on the child project, thereby synchronizing and locking the member information of the parent project and the permissions corresponding to each role parameter in the member information. It can be understood that the inheritance operation is used to synchronize the member information in the parent project to the child project, and the permissions corresponding to each role parameter in the member information are also synchronized to the child project; in addition, the above-mentioned member information and permissions are also locked in the child project, that is, the child project cannot delete the above-mentioned member information and permissions.
[0072] For example, the members of the parent project include user 1 and user 2, where the corresponding role of user 1 is manager, and the corresponding role of user 2 is developer. The corresponding permissions of managers include the permission to create products, and the corresponding permissions of developers include the permission to create products and configure products. When performing inheritance operations on sub-projects, the sub-project integrates user 1 and user 2 of the parent project, as well as the corresponding roles of user 1 and user 2, and can also inherit the permissions of the corresponding roles of user 1 and user 2. In addition, the inherited member information and corresponding permissions are also locked in the sub-project. Therefore, users can configure new member information and corresponding permissions, but cannot delete the locked member information and permissions.
[0073] Figure 6A schematic diagram of the structure of a server provided in an embodiment of the present application, which is used to execute the rights management method provided in the above embodiment, and has functional modules and beneficial effects corresponding to the execution method. As shown in the figure, it includes a processor 601, a memory 602, an input device 603 and an output device 604. The number of processors 601 can be one or more, and one processor 601 is taken as an example in the figure; the processor 601, the memory 602, the input device 603 and the output device 604 can be connected by a bus or other means, and the figure takes the connection through a bus as an example. The memory 602, as a computer-readable storage medium, can be used to store software programs, computer executable programs and modules, such as program instructions / modules corresponding to the rights management method in the embodiment of the present application. The processor 601 executes various corresponding functional applications and data processing by running the software programs, instructions and modules stored in the memory 602, that is, realizing the above-mentioned rights management method.
[0074] The memory 602 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system and at least one application required for a function; the data storage area may store data recorded or created during use, etc. In addition, the memory 602 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 non-volatile solid-state storage device. In some embodiments, the memory 602 may further include a memory remotely arranged relative to the processor 601, and these remotely arranged memories may be connected to the terminal device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0075] The input device 603 can be used to input corresponding digital or character information to the processor 601, and to generate key signal input related to the user settings and function control of the device; the output device 604 can be used to send or display key signal output related to the user settings and function control of the device.
[0076] An embodiment of the present application also provides a storage medium storing computer executable instructions, which, when executed by a processor, are used to perform relevant operations in the rights management method provided in any embodiment of the present application.
[0077] Computer-readable storage media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.
[0078] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity 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, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.
[0079] Note that the above are only preferred embodiments of the present application and the technical principles used. Those skilled in the art will understand that the present application is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present application. Therefore, although the present application is described in more detail through the above embodiments, the present application is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present application, and the scope of the present application is determined by the scope of the appended claims.
Claims
1. A rights management platform, characterized in that: Used to manage the rights of the server, the rights management platform includes: A project authority management unit, wherein the project authority management unit records visible attributes of each project and member information associated with each project, wherein the visible attributes are used to determine the scope of access rights of different users to the project, wherein the member information includes a user identifier corresponding to the user and a number of role parameters corresponding to the user identifier, and wherein the project authority management unit is used to establish a mapping relationship between the role parameters and project authority and / or product authority, and authenticate the initiator of the access request according to the established mapping relationship, wherein the mapping relationship records the project authority and / or product authority corresponding to the role parameters; A product and package permission management unit, the product and package permission management unit is used to determine the target user identifier based on the mapping relationship, configure the package permissions and product permissions of the role parameters corresponding to the target user identifier in each applicable stage and generate a role permission table, the target user identifier includes several role parameters corresponding to product permissions, and the product and package permission management unit is also used to authenticate the package operation of the access request according to the generated role permission table, the product and package permission management unit stores configuration information, the configuration information includes package version parameters, package release type parameters, verification path and package permissions, the product and package permission management unit is also used to create products in the project, and according to predefined configuration information, configure package policies for the products, and also to authenticate the package operations of the access request according to the generated role permission table, The product and package permission management unit is further used for responding to the package registration operation of the initiator, and based on the parameter items of the filtering condition, performing a matching check on the package identification information provided in the package registration operation to determine whether the package identification information includes the package version parameter, the package release type parameter and the package permission, and performing a path check on the file information provided in the package registration operation based on the parameter items of the filtering condition to determine whether the file information includes the verification path, and allowing the package to be registered if both the package identification information and the file information pass the verification; A file permission management unit is used to configure the file permission of the user identifier when configuring the package permission.
2. A rights management method, characterized in that: Applied to the rights management platform of claim 1, the method comprises: In response to a received access request from the initiator to the server, based on the mapping relationship recorded in the project authority management unit, the project authority management unit authenticates the initiator to determine whether the initiator has the authority to create a project; If the initiator has the authority to create a project, the project is created, and according to the configuration operation of the initiator, the member information of the created project is configured through the project authority management unit to establish a mapping relationship between the role parameters of each user identification and the project authority and / or product authority; Configure the role permission table through the product and package permission management unit to determine the package permissions of each role parameter; Creating a product within the project and configuring a package strategy for the product according to predefined configuration information; The product and package authority management unit stores the configuration information, which includes package version parameters, package release type parameters, verification path and package authority; The step of creating a product in the project and configuring a package strategy for the product according to predefined configuration information includes: Configure the parameter items of the filtering condition according to the package version parameter, the package release type parameter, the verification path and the package authority; In the process of performing package registration, the parameter item of the filtering condition is called for verification to determine whether to terminate the registration package; In the package registration process, calling the parameter item of the filtering condition for verification to determine whether to terminate the registration package includes: In response to the package registration operation of the initiator, based on the parameter items of the filtering condition, performing a matching check on the package identification information provided in the package registration operation to determine whether the package identification information includes the package version parameter, the package release type parameter, and the package permission; Based on the parameter items of the filtering condition, performing a path check on the file information provided in the package registration operation to determine whether the file information includes the check path; In the case that both the package identification information and the file information pass verification, registration of the package is allowed.
3. The rights management method according to claim 2, characterized in that: For creating an access request for a product within the project, the method further comprises: Determining, by the project authority management unit, whether the member information associated with the project carries the user identification of the initiator of the access request; If the member information carries the user ID of the initiator of the access request, then based on the mapping relationship established by the engineering authority management unit, determining whether the role parameter corresponding to the user ID has the authority to create a product; In a case where the initiator has the authority to create the product, a product is created in the project.
4. The rights management method according to claim 2, characterized in that: The path verification uses a regular matching algorithm to determine whether the file information includes the verification path.
5. The rights management method according to claim 2, characterized in that: For an access request to create a package within the product, the method further comprises: Obtaining member information of the project corresponding to the product through the product and package permission management unit to determine the role parameters of the initiator of the access request; In combination with the role permission table recorded by the product and package permission management unit, authenticating whether the initiator corresponding to the role parameter has the permission to create a package; If the initiator has the authority to create a package corresponding to the role parameter, a package is created in the product.
6. The rights management method according to claim 2, characterized in that: The method further comprises: When a subproject is created, an inheritance operation is performed on the subproject to synchronize and lock member information of a parent project associated with the subproject and permissions corresponding to each role parameter in the member information, where the parent project is a created project.
7. A server, characterized in that: The server comprises the rights management platform as claimed in claim 1, wherein the server further comprises: one or more processors; A storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, enables the one or more processors to implement the permission management method as described in any one of claims 2-6.
8. A storage medium storing computer executable instructions, characterized in that: When the computer executable instructions are executed by a processor, they are used to execute the rights management method according to any one of claims 2 to 6.
Citation Information
Patent Citations
Enterprise In-house IOS APP automatic update system and method
CN104317607A
Test method and storage medium for Web engineering automatic verification
CN108628749A
Project cloud authority management method and device, electronic equipment and storage medium
CN115544488A
System and method for hierarchical role-based entitlements
CN1842785A
