Permission system design method and device
By analyzing the permission levels, identifying the degree of transformation and building a tenant system, multiple external systems docking and permission correlation problems are solved, and unified permission management between portals and multiple systems is realized, and docking efficiency and consistency are improved.
Patent Information
- Application Number
- CN202410997071.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-24
- Publication Date
- 2024-11-15
AI Technical Summary
The existing technology cannot connect multiple different external systems at the same time, and lacks a clear relationship between portals and docking system permission elements, resulting in the inability to conduct top-level design and help portals connect with each system.
A method for designing a permission system, including analyzing the permission levels of the docking system, identifying the degree of transformation, identifying permission factors, building a tenant system for the portal, determining permission relationships, adjusting requirements and docking forms, forming a docking plan, and through a modular device Realize this process.
It realizes a unified permission view, simplifies departmental collaboration, reduces the degree of permission transformation of the docking system, improves docking efficiency, ensures the consistency, accuracy and fluency of permissions between systems, and meets users' needs for data combination and isolation.
Smart Images

Figure CN118965387A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of software design, and in particular relates to a permission system design method and device. Background Art
[0002] In order to meet the needs of users for data combination and data isolation, and to have higher flexibility and scalability, the portal adopts a multi-tenant form rather than a traditional portal form. The reason is that a multi-tenant portal is a portal platform based on the SaaS (Software as a Service) architecture. Its core feature is to provide shared system or program components for multiple tenants while ensuring the isolation of data between tenants. This means that on the same system or platform, different tenants can have their own independent data and operating environment without interfering with each other.
[0003] A large enterprise with multiple subsidiaries and business departments may need to use different systems to manage its business processes and data in each department. To meet this demand, building a unified portal requires docking with a variety of third-party system platforms. These system platforms themselves already have their own mature permission systems. When docking with the portal, they face many challenges such as data unification, isolation, and data / function permission mapping. In addition, with limited costs, whether to make changes and what kind of changes to make are evaluation problems that need to be dealt with during top-level design.
[0004] The existing technology does not support simultaneous connection to multiple different external systems, nor does it clearly define the relationship between the authority elements of the portal and the connection system. It lacks an overall architecture and cannot provide assistance for the top-level design of the connection between the portal and various systems. Summary of the invention
[0005] In view of the above deficiencies in the prior art, the purpose of the invention is to provide a method and device for designing a permission system, which can simultaneously connect to multiple different external systems to achieve permission control of multiple combination portals.
[0006] A first aspect of the present invention provides a method for designing a permission system, comprising:
[0007] Analyze the permission level of the docking system;
[0008] According to the permission level, analyze the similarities and differences between the portal permission requirements and the permission level of the docking system itself, and identify the transformation degree value;
[0009] According to the similarities and differences and the transformation degree values, identifying the authority factors of the docking system;
[0010] Build the portal's tenant system;
[0011] Determining the authority relationship between the portal and the docking system according to the authority factor;
[0012] According to the authority relationship, the requirements and docking forms are adjusted to form a docking plan.
[0013] A second aspect of the present invention provides a device for implementing a method for designing a permission system, comprising:
[0014] A permission level analysis module, configured to analyze the permission level of the docking system;
[0015] A transformation degree value identification module is configured to analyze the similarities and differences between the portal authority requirements and the authority level of the docking system according to the authority level, and identify the transformation degree value;
[0016] an authority factor identification module configured to identify the authority factor of the docking system according to the similarities and differences and the transformation degree value;
[0017] A tenant system building module is configured to build a tenant system of a portal;
[0018] an authority relationship determination module, configured to determine the authority relationship between the portal and the docking system according to the authority factor;
[0019] The docking scheme determination module is configured to adjust the requirements and docking forms according to the authority relationship to form a docking scheme.
[0020] A second aspect of the present invention provides a device for implementing a method for designing a permission system, comprising:
[0021] Memory, processor and user interface;
[0022] The memory is used to store computer programs;
[0023] The user interface is used to interact with the user;
[0024] The processor is used to read the computer program in the memory, and when the processor executes the computer program, any one of the above-mentioned permission system design methods is implemented.
[0025] The beneficial effects of the present invention are as follows:
[0026] The method and device described in the present invention can establish a unified permission view, simplify departmental collaboration, reduce the permission modification degree value of the docking system, improve the efficiency of docking, and assist in providing a set of top-level design methods and docking estimation methods based on the needs of both parties involved in the docking. On the premise of not destroying the internal permission system of the docking system as much as possible, the consistency, accuracy and smoothness of the permission docking between systems are guaranteed, the docking of portals with multiple systems is realized, and the user's needs for data combination and data isolation are met in the form of multiple tenants. BRIEF DESCRIPTION OF THE DRAWINGS
[0027] The accompanying drawings are only used to illustrate specific embodiments and are not considered to limit the present invention. In the entire drawings, the same reference symbols represent the same components. Obviously, the drawings described below are only some embodiments recorded in the embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings.
[0028] Figure 1 A flowchart of a method for designing a permission system according to an embodiment of the present invention;
[0029] Figure 2 A schematic diagram of a tenant system according to an embodiment of the present invention;
[0030] Figure 3 A flowchart of another method for designing a permission system according to an embodiment of the present invention;
[0031] Figure 4 A schematic diagram of a device for designing a permission system according to an embodiment of the present invention;
[0032] Figure 5 A schematic diagram of another permission system design device according to an embodiment of the present invention.
[0033] Reference numerals:
[0034] S1, step 1; S2, step 2; S3, step 3; S4, step 4; S5, step 5; S6, step 6; S301, step 301; S302-1, step 302 sub-step 1; S302-2, step 302 sub-step 2; S302-3, step 302 sub-step 3; S303, step 303; S304, step 304; S305-1, step 305 sub-step 1; S305-2, step 305 sub-step 2; S306-1, step 306 sub-step 1; S306-2, step 306 sub-step 2; 401, permission hierarchy analysis module; 402, transformation amount identification module; 403, permission factor identification module; 404, tenant system construction module; 405, permission relationship determination module; 406, docking solution determination module; 501, processor; 502, memory; 503, user interface. DETAILED DESCRIPTION
[0035] In order to enable those skilled in the art to better understand the technical solutions in the embodiments of the present invention, the technical solutions of the present invention will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all of the embodiments. It should be understood that these descriptions are only exemplary and are not intended to limit the scope of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in the field without making creative work should fall within the scope of protection of the present invention.
[0036] Furthermore, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessarily obscuring the concepts disclosed in the present invention.
[0037] In the description of the present invention, it should be noted that, unless otherwise clearly specified and limited, the orientation or position relationship indicated by the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inside", "outside", etc. is based on the orientation or position relationship shown in the drawings, which is only for the convenience of describing the present invention and simplifying the description, and does not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation of the present invention. In addition, the terms "first", "second", and "third" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. The terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be a connection between the two elements. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.
[0038] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of methods and systems consistent with some aspects of the present invention as detailed in the appended claims.
[0039] Some terms involved in the present invention are explained below.
[0040] 1. Portal: Portal is used to describe a website that integrates diverse content services, that is, a network portal.
[0041] 2. Unified portal: The unified portal can integrate multiple systems and platforms, provide a unified access point, and realize data sharing and efficient management.
[0042] 3. Tenant: In IT systems, "tenant" is used to refer to a multi-tenancy architecture, which is a software architecture pattern that allows multiple users or organizations to share the same application or system instance, but the data and configurations between them are isolated, with their own users, data, configurations and permissions, to ensure the data privacy and security of each tenant.
[0043] 4. RBAC (Role-Based Access Control) is a method for implementing system permission management. In RBAC, permissions are associated with roles rather than directly with users. Users are assigned corresponding roles and thus obtain the permissions of the roles.
[0044] 5. Permission: System permissions refer to the need to obtain relevant permission before operating a certain function, otherwise the operation will be rejected. Permission here can also be called permission. A system has multiple permissions, such as function permissions, menu permissions, data permissions, etc.
[0045] The present invention proposes a method and device for designing a permission system, which solves the problems of not supporting simultaneous docking with multiple different external systems, not clarifying the association between the permission elements of the portal and the docking system, lacking an overall architecture, and being unable to provide assistance for the top-level design of the docking between the portal and various systems.
[0046] The permission system design method proposed in the present invention includes permission hierarchy analysis of the docking system, analysis of similarities and differences between the portal permission requirements and the docking system's own permission hierarchy and identification of the degree of transformation, identification of permission factors of the docking system, construction of the portal's tenant system, determination of the permission relationship between the portal and the docking system (factor mapping), and formation of a docking plan.
[0047] The embodiments of the present invention are described in detail below with reference to the accompanying drawings.
[0048] Method Embodiment
[0049] The present invention provides a method for designing a permission system, such as Figure 1 As shown, specifically, the method includes steps S1 to S6:
[0050] S1, analyze the permission level of the docking system.
[0051] In the embodiment of the present invention, the permission levels include:
[0052] Page-level permissions, operation-level permissions, and business-level permissions;
[0053] Page-level permissions are the same for users who can see the page. As long as the user can see this page, the permissions are the same, and there is no need to break down the specific operations and data that can be viewed by whom.
[0054] Operation-level permissions are based on the premise that the page can be seen, and permissions are differentiated by managing the operation portal. The premise of operation-level permissions is that the page can be seen, and permissions are differentiated by managing the operation portal. Data that does not involve the operation portal does not distinguish users. Data that involves the operation portal is controlled by blocking or opening the operation portal to control whether the user can click the operation and perform subsequent data processing.
[0055] Business-level permissions are based on the premise that users can see the page, and the displayed content is differentiated according to different categories of users. If you have permission to see the page, the displayed content is differentiated according to different categories of users. It is judged to be business-level, which not only classifies data, but also operations need to be classified by user.
[0056] In this step, the input is the content that each docking system needs to be docked with by the portal, the object of analysis is the permission level of the content that each docking system needs to be docked with by the portal, and the output is the permission level determination of the content that each docking system needs to be docked with the portal, and the determination content includes page level, business level and operation level.
[0057] As a preferred example, common data structures include three categories: menu / module permissions, page operation permissions, and data permissions. Specifically:
[0058] Overall page permissions: whether a certain menu / page should be visible to a certain type of user.
[0059] Operation function permissions: whether a certain type of user should be able to see a certain operation button in a menu / page.
[0060] Data range permission: For data in a menu / page, whether users of different categories see the same data range.
[0061] Field / area display permissions: data in a certain menu / page, whether a certain field should be visible to a certain type of user (such as certain fields in a list); data in a certain menu / page, whether a certain area should be visible to a certain type of user.
[0062] It should be noted that in a certain menu page, the above permissions are a combination of each other. For example, if the menu cannot see the corresponding data, it cannot be seen. For example, if the data in a menu needs to be displayed / operated differently for different objects, then we need a set of tags to identify the permission levels of these pages that need to be connected.
[0063] As an optional example, for all the content that needs to be connected to the portal of the docking system, the above tags (i.e., page level, operation level, business level) are used to identify the permission level of all the content according to the determination of the following matching table:
[0064] Table 1: Permission level matching table:
[0065]
[0066] As shown in Table 1, √ means yes, × means no, and \ means that such combination does not exist and no judgment is required.
[0067] As shown in Table 1, the first row indicates the permission level, and the second row indicates the detailed classification of the permission level. For example, the value of the fourth row of the first column is ×, which means that a certain type of user cannot see the page, so there is no other permission judgment. The value of the third row of the first column is √, which means that a certain type of user can see the page, and then the operation-level permission is determined. The value of the fourth row of the second column is ×, which means that the functions within the page cannot be operated, but the business-level permission can be further determined, that is, the value of the seventh row of the fourth column is √, which means that the data range within the page distinguishes users, and then further determines whether the field / area display of the data within the page distinguishes users. For example, the value of the eleventh row of the fifth column is √, which means that the field / area display of the data within the page distinguishes users.
[0068] For another example, in the third row of Table 1, the values of the first to fifth columns are all √, indicating that the page is seen by a certain type of user, the functions on the page are operable, the functions on the page differentiate user operations, the data range on the page differentiates users, and the field / area display of the data on the page differentiates users.
[0069] S2, according to the authority level, analyzing the similarities and differences between the portal authority requirements and the authority level of the docking system itself, and identifying the transformation degree value.
[0070] As an optional example, the input of this step is the user's demand for the portal and the result of the permission level analysis of S1. The analysis objects of this step are the user's demand for the portal (including the demand for each docking system accessed through the portal) and the permission level of the docking system (i.e., the result of the permission level analysis of S1). The output is the subsequent processing and transformation required for each content to be docked according to different docking forms and docking permission levels.
[0071] Based on the degree of transformation, the requirements can be converged according to various external factors (such as project cycle, human factors, etc.) and the docking form can be selected to reduce the degree of transformation.
[0072] As an optional example, this step includes: analyzing whether the permission level of the docking system matches the portal docking function or data permission requirement, and determining a transformation degree value;
[0073] The portal authority requirements include: portal own function or data authority requirements, portal docking function or data authority requirements.
[0074] Among them, the transformation degree value includes a first transformation degree value, a second transformation degree value and a third transformation degree value. The first transformation degree value indicates that no transformation is required; the second transformation degree value indicates that the data authority is consistent with the docking system, and there is no need to transform the authority logic of the docking system itself, but it is necessary to find the mapping relationship between the factors affecting the data authority logic of both the portal and the docking system; the third transformation degree value indicates that the data authority is completely inconsistent with the docking system, or the docking system itself lacks the data authority subdivision logic required by the portal, and the docking system needs to make additional modifications.
[0075] It should be noted that the portal's needs are divided into two categories: portal-owned functions / data and portal-connected functions / data. For portal-owned functions / data, since they do not involve connection and are convenient for internal adjustment and modification, the corresponding permission control priority is low. Priority is given to functions / data that need to be connected. In S1, it is determined which functions / data to be connected to the connection system and the corresponding permission levels. In this step, combined with the portal's permission requirements, the permission level of the connection system is further analyzed to determine whether it matches the portal's needs and whether modifications are required.
[0076] As an optional example, the portal's requirements are divided into menu level, operation level and business level. When docking with the docking system, there are two forms: data / interface and page embedding. Whether the portal needs to be modified after docking with the original permission level of the docking system through different docking forms can be judged according to Table 2 below, and the modification degree value of each docking content can be determined by Table 2 below. As an optional example, the modification degree value can be divided into a first modification degree value, a second modification degree value and a third modification degree value. The first modification degree value is represented by 0, the second modification degree value is represented by 1, and the third modification degree value is represented by 2.
[0077] Specific:
[0078] The first modification degree value is 0: it means no modification is needed. Because the level of refinement is not high, there is no need to modify the docking system. The permissions can be easily filtered on the portal. The docking system only needs to give the highest permission role of the system to dock with the portal, and the portal will do the secondary filtering.
[0079] The second modification degree value 1: indicates that the data authority is consistent with the docking system, and there is no need to modify the inherent authority logic of the docking system, but it is necessary to find the mapping relationship between the factors that affect the data authority logic of both the portal and the docking system. Because the data authority logic of the portal and the docking system are consistent, there is no need to modify the inherent authority logic of the docking system, but it is necessary to find the mapping relationship between the factors that affect the data authority logic of both the portal and the docking system, which involves the design and development of synchronization technology for the consistency of relevant content.
[0080] The third modification degree value 2: indicates that the data authority is completely inconsistent with the docking system, or the docking system itself lacks the data authority subdivision logic required by the portal, and the docking system needs to be supplemented and modified. Because the data authority logic portal and the docking system are completely inconsistent, or the docking system itself lacks the data authority subdivision logic required by the portal, the docking system needs to be supplemented and modified.
[0081] Table 2: Determination table of transformation degree
[0082]
[0083]
[0084]
[0085] In the embodiment of the present invention, the design scheme can be adjusted according to the analysis result of the transformation degree value. The docking mode between the portal and the docking system can be adjusted, and the authority requirements of the portal can also be implemented according to the development cycle and cost assessment to determine whether to use a method with a high degree of transformation value, or to use a method with a small degree of transformation value first according to the development cycle, and then gradually iterate the method with a large degree of transformation value to improve the fineness of the authority.
[0086] S3, identifying the authority factors of the docking system according to the similarities and differences and the transformation degree values.
[0087] In this step, the input is the conclusion in S2 above, that is, the result of the transformation degree value determination. The object of analysis is the authority factor of the docking system. The output is to combine the conclusion of S2 above to get which content needs to map the authority factors of the docking system and the portal system, which does not need to be mapped, and which needs the docking system to supplement the authority factors according to the needs.
[0088] As an optional example, in this embodiment, the permission model is the RBAC (Role-Based Access Control) model, that is, a role-based access control model. By creating multiple roles for the platform system, operation permissions can be formed into access / operation permissions through types (directories, menus, buttons, etc.) in conjunction with routing addresses, permission identifiers, etc., and then by assigning different roles to users and checking different access / operation permissions, more detailed permission control can be achieved.
[0089] As an optional example, different platforms and systems may have different control over data permissions. Some relatively fixed data permissions are defined and controlled only by roles. For example, administrators can see the user data of the entire company, but ordinary users cannot see it. In this case, you can set role A to see the user data, and role B to not see the user data. Then, you can configure the administrator user with role A and ordinary users with role B. However, if data permissions change at any time based on specific logic, or are more segmented, you cannot simply control them using roles. For example, the administrator of department X needs to see the user data of department X and its subordinate departments, while the administrator of department Y under department X should only see the user data of department Y, and not the user data of department X or another department Z under department X. At this time, if you still only use roles to control data permissions, you have to build all departments into roles separately and then configure them, which is unreasonable. At this point, you need to understand how the platform / system and the data to be connected comprehensively determine the user permissions through multiple conditions or factors, that is, how the combined control can achieve the classification of users mentioned in S1 and S2.
[0090] As an optional example, combined control includes factors outside of roles, as well as factors such as organization, position / rank, project, user group, tenant, or custom factors, and combinations of factors. Role factors are called R, and factors outside of roles are called O. The functions or data to be connected to the docking system are split, the factors in the permissions are refined, and they are identified according to the role factors R and the factors outside of roles O.
[0091] As an optional example, based on the similarities and differences and the transformation degree value, the content that needs to be mapped between the permission factors of the docking system and the portal system is determined, specifically including the following situations:
[0092] Case 1: If the portal system and the docking system are docked at the page level, the permission factors of the docking system are not identified. In other words, if the portal and a certain page / data of the docking system are docked at the page level, it only involves whether the page / batch of data can be seen, and does not involve segmentation. It is not necessary to care about the permission factors of the docking system, and the permission factors of the docking system can be not identified.
[0093] Case 2: If the portal system requires an operation level, and the docking system is connected through data, the authority factor of the docking system is not identified. In other words, if the portal requires an operation level, and the docking system is connected through data, since the data does not involve operations, it is only necessary to control the operation authority on the portal, and the authority factor of the docking system does not need to be identified.
[0094] Case 3: If the portal system requires an operation level, it is embedded with the docking system through a page, and the docking system's own authority is at the page level, or if the portal system requires a business level, and the docking system's own authority is at the page level or operation level, then supplement it in the docking system. In other words, if the portal requires an operation level, it is embedded with the docking system through a page, and the docking system's own authority is at the page level; or if the portal requires a business level, and the docking system's own authority is at the page level / operation level, these cases indicate that the docking system's authority factors are missing and need to be supplemented in the docking system.
[0095] Case 4: If the portal system requires an operation level, and is embedded with the docking system through a page, and the docking system's own authority is an operation level or a business level, or if the portal system requires a business level, and the docking system's own authority is also a business level, then the authority factors of the portal system are mapped with the authority factors of the docking system. In other words, if the portal requires an operation level, and is embedded with the docking system through a page, and the docking system's own authority is an operation level / business level; or if the portal requires a business level, and the docking system's own authority is also a business level, these cases require the portal's authority factors to be mapped with the docking system's authority factors.
[0096] Among them, the authority factors include role factors R and extra-role factors O. Among the authority factors, R is a fixed user classification that needs to be actively configured. If the authority factor of the docking system is R, and R controls only visible and invisible (such as menus / operations), then there is no need to synchronize R's data. What needs to be done is that the corresponding page portal only needs to pass the visible R or invisible R identifier of the docking system to the docking system. O is an unfixed user classification, and user groups may be passively classified at any time. There are multiple Os in the docking system, and it is impossible to match each docking system and maintain the same types of O on the portal at the same time.
[0097] For example, Table 3 below is a permission factor mapping table.
[0098] Table 3: Permission factor mapping table
[0099]
[0100] S4, build the portal's tenant system.
[0101] In this step, we build a portal tenant system to meet the requirements of flexible planning of data grouping or isolation on demand. The purpose is to prepare for S5.
[0102] In order to meet the needs of users for data combination and data isolation, and to have higher flexibility and scalability, the portal adopts a multi-tenant form rather than a traditional portal. The reason is that the multi-tenant portal is a portal platform based on the SaaS (Software as a Service) architecture, which provides shared system or program components for multiple tenants (such as enterprise users) while ensuring the isolation of data between tenants. On the same system or platform, different tenants can have their own independent data and operating environment without interfering with each other. In the prior art, the portal platform does not have this multi-tenant feature and data isolation capability, but provides services for a single user or organization.
[0103] In the present invention, tenants are the classification of users, and the association between users and tenants can be a many-to-many relationship, that is, one tenant can contain multiple users, and one user can also belong to multiple tenants. The portal that connects to multiple systems adopts a multi-level tenant architecture to achieve refined resource management and authority control. On top of the basic characteristics of tenant isolation, it also supports the upper and lower management logic of the organization, with hierarchical or tree-like characteristics.
[0104] In the present invention, the relationship between tenants, roles and users is: if the tenant is an out-of-role authority factor O, then the authority factor of the portal also requires a role. Like every docking system, the authority control is achieved by the combination of O and R.
[0105] As an optional example, the role factor R and the role-external factor O are combined to implement permission control, including one of the following methods:
[0106] Method 1: Bind roles to users, and assign a specific group role to the user. In any tenant, the permissions the user has are the permissions corresponding to the role the user has been assigned to, and the role factor R permissions of different tenants are universal. In this method 1, a group of roles is assigned to the user (for example, the number of roles >= 1). In any tenant, the permissions the user has are the permissions corresponding to the role the user has been assigned to, and the R permissions of different tenants are universal. However, if a user has different identities in multiple tenants and requires different controls, this method 1 cannot support this.
[0107] Method 2: Roles are bound to tenants, and a specified group of roles is configured for the tenants. The role factor R permissions of the same user are not universal between tenants, but the user role factor R permissions within a tenant are exactly the same. In this method 2, a group of roles is configured for tenants (for example, the number of roles >= 1). The R permissions of the same user are not universal between tenants, but the user R permissions within a tenant are exactly the same. However, if different users in a tenant want to do different things, they cannot be distinguished.
[0108] Method 3: Roles are bound to tenants and users. A specified group role is configured for a specified user in the tenant. The role-factor R permissions of users in the tenant are not universal, and the role-factor R permissions of the same user in different tenants are not universal. In this method 3, a group role is configured for a user in the tenant (for example, the number of roles >= 1). The R permissions of users in the tenant are not universal, and the R permissions of the same user in different tenants are not universal. A user can have different R permissions in different tenants, and different users in a tenant can also have different R permissions.
[0109] Among them, a tenant contains one or more users, and a user belongs to one or more tenants; different tenants have their own independent data and operating environment and do not interfere with each other.
[0110] In the present invention, from the perspective of authority, tenants and organizations are both extra-role authority factors O, which can be combined to control authority, but do not need to establish a relationship with each other. From a management perspective, users belong to organizations. For the convenience of management, even if users within a tenant cross organizations, there needs to be a responsible department to be responsible for the relevant management / data of the tenant. The organization can be configured as an attribute of the tenant for easy identification and display, and the data of the organizational dimension can also be counted through the tenant.
[0111] In an embodiment of the present invention, different tenant levels may have different scopes. For example, a high-level tenant is a company, a middle-level tenant is a department, and a sub-level tenant is a project. For another example, a high-level tenant is a platform, a middle-level tenant is a type of application, and a sub-level tenant is some systems. For another example, multiple sub-tenants under a parent tenant may correspond to different concepts. If the parent tenant corresponds to a company, sub-tenant A may correspond to a certain platform, sub-tenant B corresponds to a certain project, and sub-tenant C corresponds to a certain type of application. It should be noted that if there needs to be a subordinate relationship between tenants and the data scope / jurisdiction has an inclusive relationship, it should be planned in a superior-subordinate manner; if there is no subordinate requirement, data and control need to be isolated, and there should be no traceable relationship between tenants.
[0112] For example, building a portal tenant system such as Figure 2 shown.
[0113] S5, according to the authority factors, determine the authority relationship between the portal and the docking system.
[0114] In this step, the input is the conclusion of S3 and the tenant system in S4. The analysis object is the authority factors of the portal tenants and the docking system, including how to do the mapping, what synchronization and mapping to do. The output is the docking content / transformation content of the authority factor docking and the corresponding workload.
[0115] According to the authority factors and tenant system, determine the content of the authority factor docking or transformation, as well as the corresponding workload of the transformation content.
[0116] The combination of authority factors includes one of the following: pure basic elements, role factor R, extra-role factor O, role factor R and extra-role factor O, multiple extra-role factors O, role factor R and multiple extra-role factors O;
[0117] Among them, pure basic elements include users and organizations.
[0118] It should be noted that the users of the portal and each docking system should be completely consistent in order to provide users with the experience of seamless switching of data between systems.
[0119] As an optional example, determining the workload corresponding to the transformation content includes one of the following situations:
[0120] Case 1: If both parties have only pure basic elements in their authority factors, the docking work content is to add synchronized organizations on the basis of the already synchronized users if the organizations are involved; if the organizations are not involved, the docking workload is recorded as 0.1, and if the organizations are involved, the docking workload is recorded as 0.5. In other words, if both parties are only affected by pure basic elements, the combination is only users (such as work order data to determine applicants) or users + organizations (such as work order data to determine approvers). In this case, on the basis of the already synchronized users, if the organizations are involved, the synchronized organizations are added. This docking workload is recorded as 0.1 if the organizations are not involved, and 0.5 if the organizations are involved.
[0121] Case 2: If both parties have only role factor R as their authority factor, and the docking work content is the single role factor R identifier passed by the portal to the docking system, then the docking workload is recorded as 1. That is to say, if both parties (in the present invention, both parties refer to the portal and the system to be docked) only have R influence: when initiating the corresponding request, the portal only needs to pass the identifier of the docking system R, or the portal defines the meaning of the docking system R, and after the docking system passes the identifier of R, it controls the authority according to the definition. No mapping is required, and the identifier of the docking system R is passed. This kind of docking workload is recorded as 1.
[0122] Case 3: If the authority factors of both parties are a single external role factor O, or a single role factor R and an external role factor O, the docking work content is that the portal needs to synchronize the portal tenant and the relationship between the tenant and the user to the docking system, and map it to the external role factor O of the docking system; when the role factor R is not included, the docking workload is recorded as 2, and when the role factor R is included, the docking workload is recorded as 3. In other words, if both parties are a single O or a single O and R: the portal needs to synchronize the portal tenant and the relationship between the tenant and the user to the docking system, and map it to the O of the docking system. For example, if the organization of the docking system can distinguish permissions according to customer needs, then the tenant of the portal is synchronized to the organization of the docking system, and when initiating a request or receiving data, the tenant ID, or the tenant ID and the system R ID, is passed. This kind of docking workload is recorded as 2 without R and 3 with R.
[0123] Case 4: If the authority factors of both parties are multiple external factors O, or role factors R and multiple external factors O, first evaluate the ratio of the authority factors required by the customer to the original authority factors of the docking system, and then determine the docking workload according to the following rules 4-1 to 4-3. In other words, if the docking party is multiple O or multiple O and R: it is necessary to evaluate whether the authority factors required by the customer are more or less than the original authority factors of the docking system. For example, in a statistical analysis view, the factors affecting the docking system are not only R, but also affected by the department (O1) and the position level (O2). Customer needs may have three situations 4-1 to 4-3:
[0124] Case 4-1: If the permission factors required by the customer are less than the original permission factors of the docking system, the portal needs to synchronize the portal tenants and the relationship between the tenants and the users to the docking system, mapping them to one of the docking system's extra-role factors O1 and the tenant identifier superimposed on a fixed-value identifier in the docking system's extra-role factor O2; the docking workload is recorded as 2.5 when the role factor R is not included, and as 3.5 when the role factor R is included. In this case, managers in the same department see the same data and do not need to be distinguished by job level. The portal needs to synchronize the portal tenants and the relationship between the tenants and the users to the docking system, mapping them to the docking system's O1, and then superimposing the tenant identifier on a fixed-value identifier (for example, C) in the docking system O2 to achieve transmission. In this case, the docking workload is recorded as 2.5 without R and 3.5 with R.
[0125] Case 4-2: If the authority factors required by the customer are consistent with the original authority factors of the docking system, the portal needs to synchronize the portal tenants and the relationship between the tenants and the users to the docking system, map them to the docking system's role-outside factor O, and pass the tenant ID, the docking system's role factor R ID, and the second role-outside factor O2 ID; when the role factor R is not included, the docking workload is recorded as 4, and when the role factor R is included, the docking workload is recorded as 5. For example, when there are multiple Os, if only one O needs to be mapped, and the values of the remaining Os are finite attributes that can be summarized, then R can be used for processing when the dictionary value is known. A department is a large amount of data, but the number of job levels may not exceed 10. In this case, the portal needs to synchronize the portal tenants and the relationship between the tenants and the users to the docking system, map them to the docking system's O, and pass the tenant ID, system R ID, and O2 ID. In this case, the docking workload is recorded as 4 without R and 5 with R.
[0126] Case 4-3: If multiple non-role permission factors are involved, and the permission factors required by the user are more than the permission factors of the docking system, or they cannot be completely matched, the relationship between the non-role permission factor O and the data is first established in the docking system, and then docking is done with the portal, and the docking workload is recorded as 10. For example, when more portal-specific Os that tenants do not have are involved, this O needs to be evaluated whether to be considered, because the docking system does not have it at all but the user requires it, and the data comes from the docking system. No matter how much the portal is modified, it is useless. The relationship between this O and the data must be established in the docking system before docking with the portal can be done - this docking workload is recorded as 10.
[0127] In the embodiment of the present invention, the two parties refer to the portal and the system to be connected.
[0128] It should be noted that because the starting point is the portal, the user's needs for management / control are met from the perspective of the portal. Each system connected to the portal can be regarded as a set of data, and each set of data is a type of permission logic. For example, when connecting to system S1, if the portal's permission requirements are the portal's tenant O1 and other factors O2, for S1, the portal's requirements for each connected page / data are O1+O2; when connecting to system S2, if the portal's permission requirements are the portal's tenant O1 and other factors O3, for S2, the portal's requirements for each connected page / data are O1+O3. This ensures that when the portal's permission factors are mapped to the permission factors of a certain docking system, for example, after the portal tenant is mapped to the organization of S1, the other requirements for connecting to S1 will not rely on the portal's organization to control permissions, thus avoiding conflicts in permission factors.
[0129] As an optional example, the following docking workload estimation table is determined according to this step:
[0130] Table 4: Docking workload estimation table
[0131]
[0132] S6, adjusting the requirements and docking forms according to the authority relationship to form a docking plan.
[0133] In this step, according to the conclusion of step S5 above, the requirements and docking form are adjusted again, and finally a docking design plan and workload estimation are formed. The final output content is:
[0134] 1. For each docking content, evaluate the docking workload, ranging from 1 to 3, with 1 being the lowest and 3 being the highest;
[0135] 2. Design a tenant system for the portal.
[0136] For example, after S1 to S6 above, the following permission system design is formed:
[0137] Table 5: Authorization system design
[0138]
[0139]
[0140] Among them, XXX1 to XXX7 represent docking items, XXXXXX1 to XXXXXX7 represent the names of function / data permission requirements, and when implementing the present invention, the specific names can be determined according to the specific projects.
[0141] Combine the following Figure 3 , the authority system design method of the present invention is further described, such as Figure 3 As shown, the authority system design method of the present invention includes S301 to S306:
[0142] S301, analyzing the permission level of the docking system. In this step, the analysis of the permission level is the same as S1, and will not be repeated here.
[0143] S302-1, analyzing whether the permission level of the docking system matches the portal docking function or data permission requirements. In this step, the permission level of the docking system matches the portal docking function or data permission requirements to determine the transformation degree value. The details are the same as S2 and will not be repeated here.
[0144] S302-2, obtain the transformation degree value. The transformation degree value includes a first transformation degree value, a second transformation degree value and a third transformation degree value. The first transformation degree value indicates that no transformation is required; the second transformation degree value indicates that the data authority is consistent with the docking system, and there is no need to transform the docking system's own authority logic, but it is necessary to find the mapping relationship between the factors that affect the data authority logic of both the portal and the docking system; the third transformation degree value indicates that the data authority is completely inconsistent with the docking system, or the docking system itself lacks the data authority subdivision logic required by the portal, and the docking system needs to make additional modifications. In this step, a transformation degree determination table is obtained. It is the same as S2 and will not be repeated here.
[0145] S302-3, according to the transformation degree value, adjust the demand and the docking form, and then obtain the docking transformation determination table according to the adjusted content. In this step, the transformation degree determination table is obtained. It is the same as S2 and will not be repeated here.
[0146] S303, identify the authority factors of the docking system, and obtain the authority factor analysis results of each docking system that needs to be docked according to the transformation determination table, and determine whether mapping is required. In this step, the authority factors of the docking system are identified according to the similarities and differences and the transformation degree value, which will not be repeated here.
[0147] S304, constructing the tenant system of the portal. The method of constructing the tenant system in this step is the same as S4, and will not be described in detail. The constructed tenant system is used as input for S305 and S306.
[0148] S305-1, analyze the authority factors of the portal tenants and the docking system, determine the docking situation, and obtain each docking content. In this step, according to the authority factors and the tenant system, determine the content of the authority factor docking or the content of the transformation, which is the same as S5 and will not be repeated here.
[0149] S305-2, obtain the transformation workload. The expression of the transformation workload is the same as S5, and will not be repeated here.
[0150] S306-1, for each docking content, evaluate the docking workload. In this step, the docking workload is obtained according to the expression form of S305-2. The specific method is the same as the docking workload estimation method in S5, and the output workload estimation table is the same as S5, which will not be repeated here.
[0151] S306-2, based on the tenant system and the docking workload evaluation result of S306-1, form a tenant system design plan for the portal.
[0152] The authority system design method of the present invention analyzes the authority level of the docking system, analyzes the similarities and differences between the portal authority requirements and the authority level of the docking system, identifies the amount of modification, identifies the authority factors of the docking system, builds the tenant system of the portal, and determines the authority relationship between the portal and the docking system (factor mapping) to form a docking solution. Using the authority system design method of the present invention, a unified authority view can be established to simplify departmental collaboration, reduce the amount of authority modification of the docking system, and improve the efficiency of docking. It can assist in providing a set of top-level design methods and docking estimation methods based on the needs of both parties involved in the docking. On the premise of not destroying the internal authority system of the docking system as much as possible, it ensures the consistency, accuracy and fluency of authority docking between systems, realizes the docking of the portal with multiple systems, and meets the user's needs for data combination and data isolation in the form of multiple tenants.
[0153] Device Embodiment
[0154] Another specific embodiment of the present invention discloses a permission system design device, such as Figure 4 As shown, incl.
[0155] The permission level analysis module 401 is configured to analyze the permission level of the docking system;
[0156] The transformation degree value identification module 402 is configured to analyze the similarities and differences between the portal authority requirements and the authority level of the docking system according to the authority level, and identify the transformation degree value;
[0157] The authority factor identification module 403 is configured to identify the authority factor of the docking system according to the similarities and differences and the transformation degree value;
[0158] A tenant system building module 404 is configured to build a tenant system of the portal;
[0159] The authority relationship determination module 405 is configured to determine the authority relationship between the portal and the docking system according to the authority factor;
[0160] The docking solution determination module 406 is configured to adjust the requirements and docking forms according to the authority relationship to form a docking solution.
[0161] The permission levels include:
[0162] Page-level permissions, operation-level permissions, and business-level permissions;
[0163] The page-level permissions are for users who can see the page, and the permissions are the same;
[0164] The operation-level permissions are based on the premise of being able to see the page, and are differentiated by the management operation entrance;
[0165] The business-level permissions refer to the content displayed based on different categories of users, provided that the page can be viewed.
[0166] As an optional example, the authority relationship determination module 405 is further configured to:
[0167] Analyze whether the permission level of the docking system matches the portal docking function or data permission requirements, and determine the degree of transformation;
[0168] The portal authority requirements include: portal own function or data authority requirements, portal docking function or data authority requirements;
[0169] The modification degree values include a first modification degree value, a second modification degree value and a third modification degree value. The first modification degree value indicates that no modification is required; the second modification degree value indicates that the data permissions are consistent with the docking system, and there is no need to modify the permission logic of the docking system itself, but it is necessary to find a mapping relationship between the factors that affect the data permission logic of both the portal and the docking system; the third modification degree value indicates that the data permissions are completely inconsistent with the docking system, or the docking system itself lacks the data permission subdivision logic required by the portal, and the docking system needs to make additional modifications.
[0170] As an optional example, the authority factor identification module 403 is configured to determine the content that needs to be mapped between the authority factors of the docking system and the portal system according to the similarities and differences and the transformation degree value, including:
[0171] If the portal system and the docking system are docked at the page level, the authority factor of the docking system is not identified;
[0172] If the portal system requires an operation level, and is connected to the docking system through data docking, the authority factor of the docking system is not identified;
[0173] If the portal system requires an operation level, and is embedded with the docking system through a page, and the docking system's own authority is at the page level, or if the portal system requires a business level, and the docking system's own authority is at the page level or operation level, then supplement it in the docking system;
[0174] If the portal system requires an operation level and is embedded with the docking system through a page, and the docking system's own authority is an operation level or a business level, or if the portal system requires a business level and the docking system's own authority is also a business level, then the authority factors of the portal system are mapped with the authority factors of the docking system;
[0175] The authority factors include role factors R and extra-role factors O.
[0176] As an optional example, the tenant system building module 404 is configured to implement permission control by combining the role factor R and the role-external factor O, including one of the following methods:
[0177] Method 1: Roles are bound to users. A specified group role is configured for the user. In any tenant, the permissions the user has are the permissions corresponding to the configured role. The role factor R permissions of different tenants are universal.
[0178] Method 2: Roles are bound to tenants. A specified group role is configured for the tenant. The role factor R permissions of the same user are not universal between tenants, but the role factor R permissions of the user within a tenant are exactly the same.
[0179] Method 3: Roles are bound to tenants and users. A specified group role is configured for a specified user in a tenant. The role factor R permissions of users within a tenant are not universal, and the role factor R permissions of the same user in different tenants are not universal.
[0180] Among them, a tenant contains one or more users, and a user belongs to one or more tenants; different tenants have their own independent data and operating environment and do not interfere with each other.
[0181] As an optional example, the authority relationship determination module 405 is further configured to determine the authority relationship between the portal and the docking system, including:
[0182] According to the authority factor and the tenant system, determine the content of the authority factor docking or the content of the transformation, and the corresponding workload of the transformation content;
[0183] The combination of the authority factors includes one of the following: pure basic elements, role factors R, extra-role factors O, role factors R and extra-role factors O, multiple extra-role factors O, role factors R and multiple extra-role factors O;
[0184] The pure basic elements include users and organizations.
[0185] The workload corresponding to the determination of the transformation content includes:
[0186] If the authority factors of both parties only have pure basic elements, the docking work content is to synchronize the organizations on the basis of the synchronized users, if any; if no organization is involved, the docking workload is recorded as 0.1, and if an organization is involved, the docking workload is recorded as 0.5;
[0187] If both parties have only role factor R as their authority factor, and the docking work content is the single role factor R identifier passed by the portal to the docking system, then the docking workload is recorded as 1;
[0188] If the authority factors of both parties are a single role-external factor O, or a single role factor R and a role-external factor O, the docking work content is that the portal needs to synchronize the portal tenants and the relationship between the tenants and users to the docking system, and map them to the role-external factor O of the docking system; when the role factor R is not included, the docking workload is recorded as 2, and when the role factor R is included, the docking workload is recorded as 3;
[0189] If the authority factors of both parties are multiple external factors O, or role factors R and multiple external factors O, first evaluate the ratio of the authority factors required by the customer to the authority factors originally owned by the docking system, and then determine the docking workload according to the following rules:
[0190] If the permission factors required by the customer are less than the original permission factors of the docking system, the portal needs to synchronize the portal tenant and the relationship between the tenant and the user to the docking system, and map it to one of the docking system's extra-role factors O1 and the tenant identifier plus a fixed value identifier in the docking system's extra-role factor O2; when the role factor R is not included, the docking workload is recorded as 2.5, and when the role factor R is included, the docking workload is recorded as 3.5;
[0191] If the permission factors required by the customer are consistent with the original permission factors of the docking system, the portal needs to synchronize the portal tenant and the relationship between the tenant and the user to the docking system, map it to the docking system's role-outside factor O, and pass the tenant ID, the docking system's role factor R ID, and the second role-outside factor O2 ID; when the role factor R is not included, the docking workload is recorded as 4, and when the role factor R is included, the docking workload is recorded as 5;
[0192] If multiple non-role permission factors are involved, and the permission factors required by the user are more than the permission factors of the docking system, or they cannot be completely matched, the relationship between the non-role permission factor O and the data is first established in the docking system, and then docking is performed with the portal, and the docking workload is recorded as 10;
[0193] The two parties refer to the portal and the system to be connected.
[0194] It should be noted that the permission level analysis module 401 in this embodiment can implement all the method steps of S1 in the above method embodiment, which will not be repeated here;
[0195] It should be noted that the transformation degree value identification module 402 in this embodiment can implement all the method steps of S2 in the above method embodiment, which will not be repeated here;
[0196] It should be noted that the authority factor identification module 403 in this embodiment can implement all the method steps of S3 in the above method embodiment, which will not be repeated here;
[0197] It should be noted that the tenant system building module 404 in this embodiment can implement all the method steps of S4 in the above method embodiment, which will not be repeated here;
[0198] It should be noted that the authority relationship determination module 405 in this embodiment can implement all the method steps of S5 in the above method embodiment, which will not be repeated here;
[0199] It should be noted that the docking solution determination module 406 in this embodiment can implement all the method steps of S6 in the above method embodiment, which will not be repeated here.
[0200] The device of this embodiment and the method embodiment described above belong to the same inventive concept, solve the same technical problem, and achieve the same technical effect, and the similarities will not be repeated here.
[0201] In a third aspect, the present invention provides a permission system design device, such as Figure 5 As shown, it includes: a memory 502 and one or more processors 501.
[0202] One or more application programs are stored in the memory 502 , and the one or more application programs are suitable for being executed by the one or more processors 501 to implement the permission system design method described in the first aspect.
[0203] like Figure 5 As shown, the processor 501 and the memory 502 are connected, for example, via a bus interface.
[0204] The structure of the device does not constitute a limitation on the embodiments of the present invention.
[0205] Processor 501 may be a CPU, a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of the present invention. Processor 501 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.
[0206] The bus may include a path to transmit information between the above components. The bus may be a PCI bus or an EISA bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.
[0207] The memory 502 may be a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, or an EEPROM, a CD-ROM or other optical disk storage, an optical disk storage (including a compressed optical disk, a laser disk, an optical disk, a digital versatile disk, a Blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to these.
[0208] In a fourth aspect, the present invention proposes a computer-readable storage medium having a computer program stored thereon, wherein the computer program can be loaded and executed by a processor according to the permission system design method described in the first aspect.
[0209] The applicant of the present invention has made a detailed explanation and description of the implementation examples of the present invention in conjunction with the drawings in the specification. However, those skilled in the art should understand that the above implementation examples are only preferred implementation schemes of the present invention, and the detailed description is only to help readers better understand the spirit of the present invention, but not to limit the scope of protection of the present invention. On the contrary, any improvements or modifications based on the inventive spirit of the present invention should fall within the scope of protection of the present invention.
[0210] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the embodiments of the present invention, rather than to limit them. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions recorded in the above embodiments, or replace some of the technical features therein by equivalents; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention. Any changes or replacements that can be easily thought of by those skilled in the art within the technical scope disclosed in the present invention should be covered within the protection scope of the present invention.
Claims
1. A method for designing a permission system, characterized in that: include: S1, analyze the permission level of the docking system; S2, according to the permission level, analyzing the similarities and differences between the portal permission requirements and the permission level of the docking system itself, and identifying the transformation degree value; S3, identifying the authority factor of the docking system according to the similarities and differences and the transformation degree value; S4, build the tenant system of the portal; S5, determining the authority relationship between the portal and the docking system according to the authority factor; S6, adjusting the requirements and docking forms according to the authority relationship to form a docking plan.
2. A method for designing a permission system according to claim 1, characterized in that: In S1, the permission levels include: Page-level permissions, operation-level permissions, and business-level permissions; The page-level permissions are for users who can see the page, and the permissions are the same; The operation-level permissions are based on the premise of being able to see the page, and are differentiated by the management operation entrance; The business-level permissions refer to the content displayed based on different categories of users, provided that the page can be viewed.
3. A method for designing a permission system according to claim 1, characterized in that: In S2, the analysis of the similarities and differences between the portal authority requirements and the authority level of the docking system according to the authority level, and the identification of the transformation degree value includes: Analyze whether the permission level of the docking system matches the portal docking function or data permission requirements, and determine the degree of transformation; The portal authority requirements include: portal own function or data authority requirements, portal docking function or data authority requirements; The modification degree values include a first modification degree value, a second modification degree value and a third modification degree value. The first modification degree value indicates that no modification is required; the second modification degree value indicates that the data permissions are consistent with the docking system, and there is no need to modify the permission logic of the docking system itself, but it is necessary to find a mapping relationship between the factors that affect the data permission logic of both the portal and the docking system; the third modification degree value indicates that the data permissions are completely inconsistent with the docking system, or the docking system itself lacks the data permission subdivision logic required by the portal, and the docking system needs to make additional modifications.
4. A method for designing a permission system according to claim 2, characterized in that: In S3, the authority factors for identifying the docking system according to the similarities and differences and the modification degree values include: According to the similarities and differences and the transformation degree value, the content that needs to be mapped between the permission factors of the docking system and the portal system is determined.
5. A method for designing a permission system according to claim 4, characterized in that: The content of determining the authority factors that need to be mapped between the docking system and the portal system includes: If the portal system and the docking system are docked at the page level, the authority factor of the docking system is not identified; If the portal system requires an operation level, and is connected to the docking system through data docking, the authority factor of the docking system is not identified; If the portal system requires an operation level, and is embedded with the docking system through a page, and the docking system's own authority is at the page level, or if the portal system requires a business level, and the docking system's own authority is at the page level or operation level, then supplement it in the docking system; If the portal system requires an operation level and is embedded with the docking system through a page, and the docking system's own authority is an operation level or a business level, or if the portal system requires a business level and the docking system's own authority is also a business level, then the authority factors of the portal system are mapped with the authority factors of the docking system; The authority factors include role factors R and extra-role factors O.
6. A method for designing a permission system according to claim 5, characterized in that: In S4, the tenant system for building the portal includes: The role factor R and the external role factor O are combined to realize the authority control, including one of the following methods: Method 1: Roles are bound to users. A specified group role is configured for the user. In any tenant, the permissions the user has are the permissions corresponding to the configured role. The role factor R permissions of different tenants are universal. Method 2: Roles are bound to tenants. A specified group role is configured for the tenant. The role factor R permissions of the same user are not universal between tenants, but the role factor R permissions of the user within a tenant are exactly the same. Method 3: The role is bound to the tenant and the user. A specified group role is configured for a specified user in the tenant. The role factor R permissions of users in the tenant are not universal, and the role factor R permissions of the same user in different tenants are not universal. Among them, a tenant contains one or more users, and a user belongs to one or more tenants; different tenants have their own independent data and operating environment and do not interfere with each other.
7. A method for designing a permission system according to claim 6, characterized in that: In S5, determining the authority relationship between the portal and the docking system according to the authority factor includes: According to the authority factor and the tenant system, determine the content of the authority factor docking or the content of the transformation, and the corresponding workload of the transformation content; The combination of the authority factors includes one of the following: pure basic elements, role factors R, extra-role factors O, role factors R and extra-role factors O, multiple extra-role factors O, role factors R and multiple extra-role factors O; The pure basic elements include users and organizations.
8. A method for designing a permission system according to claim 7, characterized in that: The workload corresponding to the determination of the transformation content includes: If the authority factors of both parties only have pure basic elements, the docking work content is to synchronize the organizations on the basis of the already synchronized users if the organizations are involved; if the organizations are not involved, the docking workload is recorded as 0.1, and if the organizations are involved, the docking workload is recorded as 0.5; If both parties have only role factor R as their authority factor, and the docking work content is the single role factor R identifier passed by the portal to the docking system, then the docking workload is recorded as 1; If the authority factors of both parties are a single role-external factor O, or a single role factor R and a role-external factor O, the docking work content is that the portal needs to synchronize the portal tenants and the relationship between the tenants and users to the docking system, and map them to the role-external factor O of the docking system; when the role factor R is not included, the docking workload is recorded as 2, and when the role factor R is included, the docking workload is recorded as 3; If the authority factors of both parties are multiple external factors O, or role factors R and multiple external factors O, first evaluate the ratio of the authority factors required by the customer to the authority factors originally owned by the docking system, and then determine the docking workload according to the following rules: If the permission factors required by the customer are less than the original permission factors of the docking system, the portal needs to synchronize the portal tenant and the relationship between the tenant and the user to the docking system, and map it to one of the docking system's extra-role factors O1 and the tenant identifier plus a fixed value identifier in the docking system's extra-role factor O2; when the role factor R is not included, the docking workload is recorded as 2.5, and when the role factor R is included, the docking workload is recorded as 3.5; If the permission factors required by the customer are consistent with the original permission factors of the docking system, the portal needs to synchronize the portal tenant and the relationship between the tenant and the user to the docking system, map it to the docking system's role-outside factor O, and pass the tenant ID, the docking system's role factor R ID, and the second role-outside factor O2 ID; when the role factor R is not included, the docking workload is recorded as 4, and when the role factor R is included, the docking workload is recorded as 5; If multiple non-role permission factors are involved, and the permission factors required by the user are more than the permission factors of the docking system, or they cannot be completely matched, the relationship between the non-role permission factor O and the data is first established in the docking system, and then docking is performed with the portal, and the docking workload is recorded as 10; The two parties refer to the portal and the system to be connected.
9. A permission system design device, characterized in that: Used to implement the permission system design method according to any one of claims 1 to 8, the device comprises: A permission level analysis module, configured to analyze the permission level of the docking system; A transformation degree value identification module is configured to analyze the similarities and differences between the portal authority requirements and the authority level of the docking system according to the authority level, and identify the transformation degree value; an authority factor identification module configured to identify the authority factor of the docking system according to the similarities and differences and the transformation degree value; A tenant system building module is configured to build a tenant system of a portal; an authority relationship determination module, configured to determine the authority relationship between the portal and the docking system according to the authority factor; The docking scheme determination module is configured to adjust the requirements and docking forms according to the authority relationship to form a docking scheme.
10. A device for designing a permission system, characterized in that: including a memory, a processor and a user interface; The memory is used to store computer programs; The user interface is used to interact with the user; The processor is used to read the computer program in the memory, and when the processor executes the computer program, it implements a method for designing a permission system as described in any one of claims 1 to 8.
