A method, apparatus, and device for access control that aggregates user attributes.
By calling the multi-party authentication system through the gateway system to query and aggregate user attributes, the problem of permission management in multi-party authentication scenarios is solved, enabling fine-grained permission control and simplifying the permission management process.
Patent Information
- Application Number
- CN202510639249.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-16
- Publication Date
- 2026-11-17
AI Technical Summary
Existing access control technologies struggle to effectively manage user attributes in multi-party authentication scenarios, resulting in insufficiently granular access control, particularly in multi-organizational structures and between different teams.
The gateway system determines the type of business request, calls the multi-party authentication system to query user attributes, aggregates user attributes at the gateway, and sends them to the business system for permission management.
It enables refined permission management in multi-party authentication scenarios, reduces the need to modify business systems, simplifies the permission application process, and improves the efficiency and accuracy of permission control.
Smart Images

Figure CN123122853A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of information security technology, and in particular to a method, apparatus and device for access control that aggregates user attributes. Background Technology
[0002] As business operations and management become increasingly sophisticated, data sensitivity is also rising. Access control has become a fundamental requirement for all teams. Taking systems supporting operational management functions as an example, while some technologies already exist to manage menu and button access, certain pages require further control over data permissions. For example:
[0003] 1) Data displayed on a certain page belongs to different teams, and each team should only see the data of its own team;
[0004] 2) A certain page displays the contact phone number of an organization, and the account manager can only see the information of the organizations within their management scope.
[0005] Currently, the industry generally adopts the RBAC (Role-Based Access Control) concept to design permission systems, realizing a unified permission management solution for multiple users and multiple systems. When configuring data permission control using RBAC, a permission resource is associated with each piece of data, and the resource is associated with a role. Users who have the corresponding role can see that piece of data.
[0006] In related technologies, data access control may involve more than just the role attribute. For example, in scenarios involving organizational structure, different departments or teams may be involved. For different departments or teams, the same position may have different access resources. In such scenarios, relying solely on role authentication is not convenient for access control when making business requests. Therefore, it is necessary to propose corresponding solutions for access control in such scenarios. Summary of the Invention
[0007] The purpose of this application is to provide a method, device, and system for access control that aggregates user attributes. This addresses the existing problem of access control for business requests involving multi-party authentication in business systems.
[0008] In a first aspect, embodiments of this application provide a method for access control that aggregates user attributes, the method comprising:
[0009] In response to a business request triggered by the user login front-end page, determine the type of the current business request;
[0010] Based on at least one authentication system associated with different pre-set business request types, determine at least one target authentication system associated with the current business request type;
[0011] The user's account information is sent to each target authentication system, and each target authentication system queries the corresponding type of user attributes based on the user's account information.
[0012] The system receives user attributes of the corresponding type returned by each target authentication system, aggregates them, and sends them to the business system. The business system then determines the permissions of the business request based on the aggregated user attributes.
[0013] In some possible embodiments, the method further includes:
[0014] Receive the corresponding type of user attributes returned by each target authentication system, and determine the interface of the audit system to be called based on the current business request type;
[0015] The aggregated user attributes and business requests are sent to the audit system. Auditors log in to the audit system and trigger the audit operation. When the audit system determines that the specified user attributes match the auditor's attributes, the aggregated user attributes and business requests are sent to the business system.
[0016] In some possible embodiments, receiving user attributes of the corresponding type returned by each target authentication system, aggregating them, and sending them to the business system includes:
[0017] Receive user attributes of the corresponding type returned by each target authentication system;
[0018] When multiple types of user attributes are determined to be returned, the user attributes of the multiple types are aggregated in a specified order, and the aggregated user attributes are sent to the business system.
[0019] Secondly, embodiments of this application provide a method for access control that aggregates user attributes, the method comprising:
[0020] Receive user account information sent by the gateway through at least one authentication system;
[0021] Each authentication system queries the user's account information to match the corresponding type of user attributes based on the pre-set matching relationship between different user attributes of the corresponding type and different account information.
[0022] Each authentication system sends the matching user attributes of the corresponding type to the gateway.
[0023] In some possible embodiments, at least one of the following steps is also included:
[0024] When new account information is determined, at least one authentication system sets the matching relationship between the corresponding type of user attributes and the new account based on the new account information;
[0025] When any authentication system determines that the user attribute of the corresponding type of account information has changed, update the user attribute of the corresponding type of account information.
[0026] When any authentication system determines that any account information has been deleted, the matching relationship between that account information and the corresponding type of user attributes is deleted.
[0027] In some possible embodiments, the method further includes:
[0028] The system receives aggregated user attributes and business requests sent by the gateway and displays information pending review.
[0029] Based on the audit operation triggered by the auditor who has logged into the audit system, query the auditor's attributes from the specified authentication system according to the specified type of user attributes;
[0030] When it is determined that the attribute of the reviewer is consistent with the attribute of the specified type of user, the aggregated user attributes and business request are sent to the business system.
[0031] In some possible embodiments, the method further includes:
[0032] The business system receives business requests and aggregated user attributes sent by the audit system when the audit system determines that the user attributes of a specified type match the audit personnel attributes. The business requests are data to be processed.
[0033] The aggregated user attributes are matched with data attributes in the database to determine the target data corresponding to the data attributes that match the aggregated user attributes, and the target data is then processed.
[0034] In some possible embodiments, the method further includes:
[0035] When no matching target data is found, the target security level corresponding to the aggregated user attributes is determined based on the user attributes corresponding to different predefined security levels.
[0036] Based on the predefined different data security levels, the data with the target security level is determined to be the target data that matches the aggregated user attributes.
[0037] Thirdly, embodiments of this application provide an access control device that aggregates user attributes, including at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform any of the methods provided in the first aspect above, or to perform any of the methods provided in the second aspect above.
[0038] Fourthly, embodiments of this application also provide an access control system that aggregates user attributes, including:
[0039] A gateway is used to execute the permission control method for aggregating user attributes as described in the first aspect above;
[0040] The server is used to execute the permission control method for aggregating user attributes as described in the second aspect above.
[0041] Fifthly, embodiments of this application also provide an access control device that aggregates user attributes, including:
[0042] The request type determination module is used to determine the type of the current business request in response to a business request triggered by the user login front-end page.
[0043] The authentication system determination module is used to determine at least one target authentication system associated with the current business request type based on at least one authentication system associated with different pre-set business request types.
[0044] The account sending module is used to send the user's account information to each target authentication system, and each target authentication system queries the corresponding type of user attributes based on the user's account information;
[0045] The user attribute aggregation module is used to receive user attributes of the corresponding type returned by each target authentication system, aggregate them and send them to the business system, and the business system determines the permissions of the business request based on the aggregated user attributes.
[0046] Sixthly, embodiments of this application also provide an access control device that aggregates user attributes, including:
[0047] The account receiving module is used to receive user account information sent by the gateway through at least one authentication system;
[0048] The user attribute query module is used by each authentication system to query the user attributes of the corresponding type that match the user's account information based on the pre-set matching relationship between different user attributes of the corresponding type and different account information.
[0049] The user attribute sending module is used by each authentication system to send the matching user attributes of the corresponding type to the gateway.
[0050] In a seventh aspect, another embodiment of this application also provides a computer storage medium storing a computer program for causing a computer to execute any of the permission control methods for aggregating user attributes provided in the embodiments of this application.
[0051] In this embodiment, by configuring the gateway, the associated authentication system can be determined for different business requests. The multi-party authentication system can utilize accounts to query multiple types of user attributes. The gateway aggregates these user attributes and sends them to the business system for permission management. This solves the problem of permission control for corresponding business requests involving multi-party authentication in existing business systems.
[0052] Other features and advantages of this application will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings. Attached Figure Description
[0053] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments of this application will be briefly introduced below. Obviously, the drawings introduced below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0054] Figure 1 This is a schematic diagram of an access control system that aggregates user attributes according to an embodiment of this application;
[0055] Figure 2 This is a schematic diagram of an access control system that aggregates user attributes in a scenario where no review is required, according to an embodiment of this application.
[0056] Figure 3 This is a schematic diagram of an access control system that aggregates user attributes in a scenario requiring review, according to one embodiment of this application.
[0057] Figure 4 This is a flowchart of an access control method for aggregated user attributes applied to a gateway according to an embodiment of this application;
[0058] Figure 5 This is a flowchart of an access control method for aggregated user attributes applied to a server according to an embodiment of this application;
[0059] Figure 6 This is a structural diagram of an access control device for aggregated user attributes applied to a server according to an embodiment of this application. Detailed Implementation
[0060] To further illustrate the technical solutions provided in the embodiments of this application, a detailed description is provided below in conjunction with the accompanying drawings and specific implementation methods. Although the embodiments of this application provide method operation steps as shown in the following embodiments or drawings, more or fewer operation steps may be included in the method based on conventional or non-inventive effort. For steps that do not logically have a necessary causal relationship, the execution order of these steps is not limited to the execution order provided in the embodiments of this application. In actual processing or when the control device executes the method, it may be executed sequentially or in parallel according to the method shown in the embodiments or drawings.
[0061] This application provides an access control system that aggregates user attributes, such as... Figure 1 As shown, it includes:
[0062] Client 100 serves as the front end of the business system. Users log in to the business system through the client and interact with the server to perform business operations by operating the front end page. Specifically, users can log in to the front end page to trigger corresponding business requests.
[0063] Gateway 101 is used to respond to business requests triggered by user login front-end pages, determine the current business request type; determine at least one target authentication system associated with the current business request type based on at least one authentication system associated with different pre-set business request types; send the user's account information to each target authentication system, and each target authentication system queries the corresponding type of user attributes based on the user's account information; receive the corresponding type of user attributes returned by each target authentication system, aggregate them and send them to the business system, and the business system determines the permissions of the business request based on the aggregated user attributes;
[0064] Server 102 is used to receive user account information sent by the gateway through at least one authentication system; each authentication system queries the user attribute of the corresponding type that matches the user's account information according to the pre-set matching relationship between different user attributes of the corresponding type and different account information; each authentication system sends the queried matching user attribute of the corresponding type to the gateway.
[0065] In the embodiments of this application, a server implements a multi-party authentication system and a business system. Each authentication system manages a corresponding type of user attribute. User attributes are pre-assigned in each authentication system based on the user's account information. Specifically, for each user's account information, a matching relationship is established between the account information and the corresponding type of user attribute, thereby recording different types of user attributes for each account. In implementation, a user's account has corresponding user attributes recorded in at least one authentication system. Taking a multi-organizational architecture business scenario as an example, one authentication system is used to determine the user's department, position, or team, while another authentication system distinguishes the permission resources corresponding to different positions within the same department. Of course, other authentication systems can also be used.
[0066] Therefore, this application embodiment can realize the query of at least one type of user attribute of a user through a multi-party authentication system. After a user logs into the business system, the user attributes required for permission management involved in different business requests may be different. This application pre-sets at least one authentication system associated with different business request types in the gateway, that is, associates the authentication system interfaces called by different business request types. Some business request types may only involve one authentication system. For example, the above-mentioned at least one authentication system includes the authentication system for permission resources. That is, it does not consider other user attributes of the user, but only establishes the matching relationship between the user's account and permission resources. For scenarios with multiple organizational structures, it does not distinguish which department or position the user belongs to. Some business request types may involve multiple authentication systems. The gateway will call the interfaces of multiple authentication systems, and the corresponding authentication system will query the corresponding user attributes in the system according to the user's account.
[0067] The aforementioned multi-party authentication system and business system are implemented by servers. They can be implemented by the same server or by different servers, such as... Figure 2 The diagram illustrates a possible architecture of the user attribute aggregation access control system according to an embodiment of this application. The first authentication system and the second authentication system can be defined as needed. For example, the first authentication system records the user's team, department, and job level; the second authentication system is a permission resource authentication system that records user business permission information, such as a list of organizations managed by an account manager, recorded in the portal data. It should be noted that for some users, the corresponding type of user attribute may only be recorded in the permission resource authentication system. Therefore, when the gateway receives any business request from that user, it will only search for the corresponding type of user attribute in the permission resource authentication system.
[0068] Since this application embodiment uses a multi-party authentication system to assign corresponding user attributes to different users, when user attributes are changed, the user attribute modification is completed in the corresponding authentication system without the need to modify other data. In some possible embodiments, the above-mentioned server is also used to perform at least one of the following steps:
[0069] When new account information is determined, at least one authentication system sets a matching relationship between the corresponding type of user attributes and the new account based on the new account information. The new account may involve multiple authentication systems or only one. In this case, the new account and the corresponding type of user attributes are added to the relevant authentication systems. It should be noted that the corresponding type of user attribute may be newly added or may be existing in the authentication system; that is, multiple users may share a single user attribute in the authentication system. If it is a newly added user attribute, the corresponding data attribute needs to be updated in the database to be consistent with the newly added user attribute, so that the new account has the permission to make business requests to the corresponding data in the database.
[0070] When any authentication system determines that the user attribute of any account information has changed, the corresponding user attribute of that account information is updated. If the user attribute of an account changes, only the matching relationship needs to be changed. The updated matching relationship's user attribute may be newly added or may be an existing attribute from the authentication system. If it is a newly added user attribute, the corresponding data attribute in the database needs to be updated to match the newly added user attribute, so that the new account has the permission to make business requests to the corresponding data in the database.
[0071] When any authentication system determines that any account information has been deleted, the matching relationship between that account information and the corresponding user attribute type is deleted. If an account is deleted, only the corresponding matching relationship needs to be deleted in the relevant authentication system; there is no need to update the database of the business system.
[0072] The aforementioned business request types are categorized into scenarios requiring review and scenarios that do not require review. For example... Figure 2 The first scenario illustrates a case where no approval is required. In this case, after the gateway receives the aggregated user attributes, it sends the business request and the aggregated user attributes to the business system. The corresponding business request in this scenario can be a data viewing request. The second scenario involves business requests that require approval. The following describes the permission control method for business requests in this scenario.
[0073] In some possible embodiments, the gateway is further configured to: receive user attributes of the corresponding type returned by each target authentication system; determine the interface of the audit system to be called based on the current business request type; send the aggregated user attributes and business requests to the audit system; have auditors log in to the audit system and trigger audit operations; and when the audit system determines that the specified user attributes are consistent with the auditor's attributes, send the aggregated user attributes and business requests to the business system.
[0074] In some possible embodiments, the server is further configured to: receive aggregated user attributes and business requests sent by the gateway through the auditing system, and display information to be audited; query the auditing personnel attributes from the designated authentication system according to the auditing operation triggered by the auditing personnel logged into the auditing system, based on the specified type of user attributes; and when it is determined that the auditing personnel attributes are consistent with the specified type of user attributes, send the aggregated user attributes and business requests to the business system.
[0075] like Figure 3 As shown, the aforementioned server is also used to implement an auditing system. This auditing system, the multi-party authentication system, and the business system can be on the same server or separate servers. In this embodiment, when the current business request type is data processing (i.e., involving the addition, modification, or deletion of data), it needs to be reviewed by an auditor. When an auditor reviews a business request, different users have corresponding auditors with a binding relationship. This embodiment obtains the user's specified type of user attributes through the auditing system, and then, based on the specified type, the auditing system determines which authentication system in the multi-party authentication system to call, sending the auditor's account to the corresponding authentication system to obtain the auditor attributes consistent with the user type. For example, auditors in the same department can only audit the data processing operations of personnel in that department.
[0076] In this embodiment of the application, to achieve matching between aggregated user attributes and data attributes, when the aggregated user attributes include multiple types, the gateway is specifically used to receive the corresponding types of user attributes returned by each target authentication system; when it is determined that multiple types of user attributes are returned, the gateway aggregates the multiple types of user attributes in a specified order and sends the aggregated user attributes to the business system. The corresponding data attributes pre-set in the database are also set in a specified order.
[0077] In this embodiment, data attributes are pre-assigned in the business system, and the encoding of the data attributes must be consistent with the encoding of the user attributes of users with corresponding permissions. The business system may receive aggregated user attributes and business requests from the gateway, or it may receive aggregated user attributes and business requests from the approval system.
[0078] In some possible embodiments, the server is further configured to: receive business requests and aggregated user attributes sent by the gateway through the business system; match the aggregated user attributes with data attributes in the database to determine the target data corresponding to the data attribute that matches the aggregated user attributes; when the business request is to view data, display the target data; when the business request is to process data, perform processing on the target data.
[0079] In some possible embodiments, the server is further configured to: receive, through the business system, a business request and aggregated user attributes sent when the audit system determines that a specified type of user attribute matches the auditer attribute, wherein the business request is processing data; match the aggregated user attributes with data attributes in the database, determine the target data corresponding to the data attribute that matches the aggregated user attributes, and perform processing on the target data.
[0080] In this embodiment, the aforementioned business system manages access permissions for business requests based on aggregated user attributes. This involves two scenarios: In a scenario where no review is required, the corresponding business request might be a data viewing request. In this case, the gateway sends the aggregated user attributes and the business request to the business system. Since the business system has pre-configured data attributes in its database, the aggregated user attributes are matched against the data attributes. In the other scenario, where review is required, the corresponding business request might be a data processing request. In this case, the review system sends the aggregated user attributes and the business request to the business system.
[0081] In some possible embodiments, the server is further configured to, when no target data corresponding to a defined matching data attribute is found, determine the target security level corresponding to the aggregated user attributes based on the user attributes corresponding to different predefined security levels; and determine the data with the target security level as the target data matching the aggregated user attributes based on the predefined security levels of different data.
[0082] In this embodiment, the business system can define different data security levels and pre-establish the correspondence between different security levels and user attributes. After receiving user attributes, the business system determines the corresponding security level, thereby determining the target data.
[0083] In this embodiment, user attributes are obtained through a third-party multi-party authentication system, such as an IAM (Identity and Access Management) organizational management system, an account manager organizational relationship maintenance system, or a permission resource system. When adding new data, the association between user attributes and data is stored, and the association method can be configured using parameters to reduce the need for modification to the business system. When querying data, the corresponding business system is queried based on the user attributes (organization, responsible organization, or permission resource) carried by the user.
[0084] The solution provided in this application is friendly to historical systems, requiring little or no modification to the database and backend systems; it is friendly to business systems, requiring only modification to the corresponding attribute management, without needing to adapt to its own system based on attribute adjustments; it does not require the configuration of additional permission resources, is user-friendly, and eliminates the complicated permission application process.
[0085] Based on the same inventive concept, embodiments of this application also provide a method for access control that aggregates user attributes. This method is applied to a gateway, such as... Figure 4 As shown, the method includes:
[0086] Step 401: In response to the business request triggered by the user login front-end page, determine the current business request type;
[0087] Step 402: Determine at least one target authentication system associated with the current business request type based on at least one authentication system associated with different pre-set business request types.
[0088] Step 403: Send the user's account information to each target authentication system, and each target authentication system queries the corresponding type of user attributes based on the user's account information;
[0089] Step 404: Receive the corresponding user attributes returned by each target authentication system, aggregate them, and send them to the business system. The business system then determines the permissions of the business request based on the aggregated user attributes.
[0090] In some possible embodiments, the method further includes:
[0091] Receive the corresponding type of user attributes returned by each target authentication system, and determine the interface of the audit system to be called based on the current business request type;
[0092] The aggregated user attributes and business requests are sent to the audit system. Auditors log in to the audit system and trigger the audit operation. When the audit system determines that the specified user attributes match the auditor's attributes, the aggregated user attributes and business requests are sent to the business system.
[0093] In some possible embodiments, receiving user attributes of the corresponding type returned by each target authentication system, aggregating them, and sending them to the business system includes:
[0094] Receive user attributes of the corresponding type returned by each target authentication system;
[0095] When multiple types of user attributes are determined to be returned, the user attributes of the multiple types are aggregated in a specified order, and the aggregated user attributes are sent to the business system.
[0096] Based on the same inventive concept, embodiments of this application also provide a method for access control that aggregates user attributes. This method is applied to a server, such as... Figure 5 As shown, the method includes:
[0097] Step 501: Receive user account information sent by the gateway through at least one authentication system;
[0098] Step 502: Each authentication system queries the user's account information to find the corresponding type of user attributes based on the pre-set matching relationship between different user attributes of the corresponding type and different account information.
[0099] Step 503: Each authentication system sends the matching user attributes of the corresponding type to the gateway.
[0100] In some possible embodiments, at least one of the following steps is also included:
[0101] When new account information is determined, at least one authentication system sets the matching relationship between the corresponding type of user attributes and the new account based on the new account information;
[0102] When any authentication system determines that the user attribute of the corresponding type of account information has changed, update the user attribute of the corresponding type of account information.
[0103] When any authentication system determines that any account information has been deleted, the matching relationship between that account information and the corresponding type of user attributes is deleted.
[0104] In some possible embodiments, the method further includes:
[0105] The system receives aggregated user attributes and business requests sent by the gateway and displays information pending review.
[0106] Based on the audit operation triggered by the auditor who has logged into the audit system, query the auditor's attributes from the specified authentication system according to the specified type of user attributes;
[0107] When it is determined that the attribute of the reviewer is consistent with the attribute of the specified type of user, the aggregated user attributes and business request are sent to the business system.
[0108] In some possible embodiments, the method further includes:
[0109] The business system receives business requests and aggregated user attributes sent by the gateway.
[0110] The aggregated user attributes are matched with data attributes in the database to determine the target data corresponding to the data attributes that match the aggregated user attributes.
[0111] When the business request is determined to be viewing data, the target data is displayed.
[0112] When a business request is determined to be for processing data, the processing of the target data is performed.
[0113] In some possible embodiments, the method further includes:
[0114] The business system receives business requests and aggregated user attributes sent by the audit system when the audit system determines that the user attributes of a specified type match the audit personnel attributes. The business requests are data to be processed.
[0115] The aggregated user attributes are matched with data attributes in the database to determine the target data corresponding to the data attributes that match the aggregated user attributes, and the target data is then processed.
[0116] In some possible embodiments, the method further includes:
[0117] When no matching target data is found, the target security level corresponding to the aggregated user attributes is determined based on the user attributes corresponding to different predefined security levels.
[0118] Based on the predefined different data security levels, the data with the target security level is determined to be the target data that matches the aggregated user attributes.
[0119] Having introduced the method and apparatus for managing aggregated user attributes according to exemplary embodiments of this application, we will now introduce an apparatus for managing aggregated user attributes according to another exemplary embodiment of this application.
[0120] In some possible implementations, the access control device for aggregated user attributes according to this application may include at least one processor and at least one memory. The memory stores program code that, when executed by the processor, causes the processor to perform the steps in the access control method for aggregated user attributes applied to a gateway according to the various exemplary embodiments of this application described above, or to perform the steps in the access control method for aggregated user attributes applied to a server.
[0121] The following reference Figure 6 This application describes an access control device 160 that aggregates user attributes according to this embodiment. Figure 6 The illustrated permission control device 160 that aggregates user attributes is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.
[0122] like Figure 6 As shown, the permission control device 160 that aggregates user attributes is manifested in the form of a general electronic device. The components of the permission control device 160 that aggregates user attributes may include, but are not limited to: at least one processor 161, at least one memory 162, and a bus 163 connecting different system components (including memory 162 and processor 161).
[0123] Bus 163 represents one or more of several bus architectures, including a memory bus or memory controller, peripheral bus, processor, or local bus using any of the various bus architectures.
[0124] The memory 162 may include a readable medium in the form of volatile memory, such as random access memory (RAM) 1621 and / or cache memory 1622, and may further include read-only memory (ROM) 1623.
[0125] The memory 162 may also include a program / utility 1625 having a set (at least one) of program modules 1624, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.
[0126] The user attribute aggregation access control device 160 can also communicate with one or more external devices 164 (e.g., keyboard, pointing device, etc.), one or more devices that enable users to interact with the user attribute aggregation access control device 160, and / or any device that enables the user attribute aggregation access control device 160 to communicate with one or more other electronic devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 165. Furthermore, the user attribute aggregation access control device 160 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 166. As shown, network adapter 166 communicates with other modules used for the user attribute aggregation access control device 130 via bus 163. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with the user attribute aggregation access control device 160, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0127] In some possible implementations, various aspects of the permission control method for aggregating user attributes provided in this application can also be implemented in the form of a program product, which includes program code. When the program product is run on a computer device, the program code is used to cause the computer device to perform the steps in the permission control method for aggregating user attributes according to various exemplary embodiments of this application described above.
[0128] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0129] The monitoring program product of the embodiments of this application may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on an electronic device. However, the program product of this application is not limited thereto. In this document, the readable storage medium may be any tangible medium that contains or stores a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.
[0130] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.
[0131] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.
Claims
1. A method for access control that aggregates user attributes, characterized in that, The method includes: In response to a business request triggered by the user login front-end page, determine the type of the current business request; Based on at least one authentication system associated with different pre-set business request types, determine at least one target authentication system associated with the current business request type; The user's account information is sent to each target authentication system, and each target authentication system queries the corresponding type of user attributes based on the user's account information. The system receives user attributes of the corresponding type returned by each target authentication system, aggregates them, and sends them to the business system. The business system then determines the permissions of the business request based on the aggregated user attributes.
2. The method according to claim 1, characterized in that, Also includes: Receive the corresponding type of user attributes returned by each target authentication system, and determine the interface of the audit system to be called based on the current business request type; The aggregated user attributes and business requests are sent to the audit system. Auditors log in to the audit system and trigger the audit operation. When the audit system determines that the specified user attributes match the auditor's attributes, the aggregated user attributes and business requests are sent to the business system.
3. The method according to claim 1, characterized in that, Receive user attributes of the corresponding type returned by each target authentication system, aggregate them, and send them to the business system, including: Receive user attributes of the corresponding type returned by each target authentication system; When multiple types of user attributes are determined to be returned, the user attributes of the multiple types are aggregated in a specified order, and the aggregated user attributes are sent to the business system.
4. A method for access control that aggregates user attributes, characterized in that, The method includes: Receive user account information sent by the gateway through at least one authentication system; Each authentication system queries the user's account information to match the corresponding type of user attributes based on the pre-set matching relationship between different user attributes of the corresponding type and different account information. Each authentication system sends the matching user attributes of the corresponding type to the gateway.
5. The method according to claim 4, characterized in that, It also includes at least one of the following steps: When new account information is determined, at least one authentication system sets the matching relationship between the corresponding type of user attributes and the new account based on the new account information; When any authentication system determines that the user attribute of the corresponding type of account information has changed, update the user attribute of the corresponding type of account information. When any authentication system determines that any account information has been deleted, the matching relationship between that account information and the corresponding type of user attributes is deleted.
6. The method according to claim 4, characterized in that, Also includes: The system receives aggregated user attributes and business requests sent by the gateway and displays information pending review. Based on the audit operation triggered by the auditor who has logged into the audit system, query the auditor's attributes from the specified authentication system according to the specified type of user attributes; When it is determined that the attribute of the reviewer is consistent with the attribute of the specified type of user, the aggregated user attributes and business request are sent to the business system.
7. The method according to claim 4, characterized in that, Also includes: The business system receives business requests and aggregated user attributes sent by the gateway. The aggregated user attributes are matched with data attributes in the database to determine the target data corresponding to the data attributes that match the aggregated user attributes. When the business request is determined to be viewing data, the target data is displayed. When a business request is determined to be for processing data, the processing of the target data is performed.
8. The method according to claim 7, characterized in that, Also includes: The business system receives business requests and aggregated user attributes sent by the audit system when the audit system determines that the user attributes of a specified type match the audit personnel attributes. The business requests are data to be processed. The aggregated user attributes are matched with data attributes in the database to determine the target data corresponding to the data attributes that match the aggregated user attributes, and the target data is then processed.
9. The method according to claim 7 or 8, characterized in that, Also includes: When no matching target data is found, the target security level corresponding to the aggregated user attributes is determined based on the user attributes corresponding to different predefined security levels. Based on the predefined different data security levels, the data with the target security level is determined to be the target data that matches the aggregated user attributes.
10. A permission control device that aggregates user attributes, characterized in that, The method includes at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the method as described in any one of claims 1-3, or to perform the method as described in any one of claims 4-9.
11. A permission control system that aggregates user attributes, characterized in that, include: A gateway for executing the access control method for aggregating user attributes as described in any one of claims 1-3; A server is configured to execute the permission control method for aggregating user attributes as described in any one of claims 4-9.
