Modifying permission trees in a virtualization environment

• US 9,712,534 B2
• Filed: 11/02/2015
• Issued: 07/18/2017
• Est. Priority Date: 08/29/2012
• Status: Active Grant

• Current Assignee: Red Hat Israel Ltd. (International Business Machines Corporation)
• Original Assignee: Red Hat Israel Ltd. (International Business Machines Corporation)
• Inventors: Mureinik, Allon
• Primary Examiner(s): Leung, Robert
• Application Number:
  US14/930,056
• Publication Number:
  US 20160057147A1
• Time in Patent Office: 624 Days
• CPC Class Codes: G06F 16/2246 Trees, e.g. B+trees
• CPC Class Codes: G06F 16/2445 Data retrieval commands; View definitions
• CPC Class Codes: G06F 16/245 Query processing
• CPC Class Codes: G06F 16/24539 using cached or materialised query results
• CPC Class Codes: G06F 2009/45587 Isolation or security of virtual machine instances
• CPC Class Codes: G06F 21/00 Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
• CPC Class Codes: G06F 21/121 Restricting unauthorised execution of programs
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 21/53 by executing in a restricted environment, e.g. sandbox or secure virtual machine
• CPC Class Codes: G06F 21/604 Tools and structures for managing or administering access control systems
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: G06F 21/629 to features or functions of an application
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: G06F 2221/2145 Inheriting rights or properties, e.g., propagation of permissions or restrictions within a hierarchy
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: H04L 63/105 : Multiple levels of security
• CPC Class Codes: H04W 12/08 : Access security

Abstract

A processing device receives a permission request indicating a user and an entity. The processing device modifies a permissions database to generate a modified database view. Using the modified database view, the processing device determines whether the user has permission to access the entity and returns an indication of whether the user has permission to access the entity.

Claims

1. A method comprising:

receiving a permission request, the request indicating a user and an entity;

flattening, by a processing device, a permissions database to generate a flattened database view, wherein flattening the permissions database comprises;

identifying a first set of entities for which either the user or a role to which the user is assigned has explicit permissions defined in the permissions database;

identifying a second set of entities that inherit the explicit permissions; and

creating a separate entry in the flattened database view for each unique combination of the user and one of the entities in the first or second sets of entities, wherein the flattened database view comprises a stored query accessible as a virtual table in the permissions database computed from data stored in the permissions database;

determining, using the flattened database view, whether the user has permission to access the entity by querying the flattened database view for a single entry associated with a combination of the user and the entity; and

returning an indication of whether the user has permission to access the entity.

2. The method of claim 1, wherein the permission request is received from a client device.

3. The method of claim 1, wherein flattening the permissions database comprises:

identifying a first entity for which the user has explicit permissions defined in the permissions database; and

identifying a second entity that is a child of the first entity using a labeling hierarchy of entities.

4. The method of claim 3, wherein flattening the permissions database further comprises:

identifying the role to which the user is assigned;

identifying a third entity for which the role has permissions defined in the permissions database; and

identifying a fourth entity that is a child of the third entity using the labeling hierarchy of entities.

5. The method of claim 4, wherein flattening the permissions database further comprises:

creating a separate entry in the flattened database view for each unique combination of the user and one of the first, second, third and fourth entities.

6. The method of claim 1, wherein determining whether the user has permission to access the entity comprises issuing a single query to the flattened database view for an entry comprising the user and the entity.

7. The method of claim 6, wherein the indication of whether the user has permission to access the entity is affirmative if the entry in the flattened database view comprising the user and the entity is located.

8. The method of claim 6, wherein the indication of whether the user has permission to access the entity is negative if the entry in the flattened database view comprising the user and the entity is not located.

9. A system comprising:

a memory; and

a processing device operatively coupled to the memory, the processing device to;

receive a permission request from a client, the request indicating a user and an entity;

flatten a permissions database to generate a flattened database view, wherein to generate the flattened database view, the processing device to;

identify a first set of entities for which either the user or a role to which the user is assigned has explicit permissions defined in the permissions database;

identify a second set of entities that inherit the explicit permissions; and

create a separate entry in the flattened database view for each unique combination of the user and one of the entities in the first or second sets of entities, wherein the flattened database view comprises a stored query accessible as a virtual table in the permissions database computed from data stored in the permissions database;

determine, using the flattened database view, whether the user has permission to access the entity by querying the flattened database view for a single entry associated with a combination of the user and the entity; and

return an indication of whether the user has permission to access the entity.

10. The system of claim 9, wherein to flatten the permissions database, the processing device to:

identify a first entity for which the user has explicit permissions defined in the permissions database; and

identify a second entity that is a child of the first entity using a labeling hierarchy of entities.

11. The system of claim 10, wherein to flatten the permissions database, the processing device to:

identify the role to which the user is assigned;

identify a third entity for which the role has permissions defined in the permissions database; and

identify a fourth entity that is a child of the third entity using the labeling hierarchy of entities.

12. The system of claim 11, wherein to flatten the permissions database, the processing device further to:

create a separate entry in the flattened database view for each unique combination of the user and one of the first, second, third and fourth entities.

13. The system of claim 9, wherein to determine whether the user has permission to access the entity, the processing device to issue a single query to the flattened database view for an entry comprising the user and the entity.

14. The system of claim 13, wherein the indication of whether the user has permission to access the entity is affirmative if the entry in the flattened database view comprising the user and the entity is located.

15. The system of claim 13, wherein the indication of whether the user has permission to access the entity is negative if the entry in the flattened database view comprising the user and the entity is not located.

16. A non-transitory machine-readable storage medium storing instructions which, when executed, cause a processing device to:

receive a permission request, the request indicating a user and an entity;

flatten, by the processing device, a permissions database to generate a flattened database view, wherein to flatten the permissions database, the instructions to cause the processing device to;

identify a first set of entities for which either the user or a role to which the user is assigned has explicit permissions defined in the permissions database;

identify a second set of entities that inherit the explicit permissions; and

create a separate entry in the flattened database view for each unique combination of the user and one of the entities in the first or second sets of entities, wherein the flattened database view comprises a stored query accessible as a virtual table in the permissions database computer from data stored in the permissions database;

determine, using the flattened database view, whether the user has permission to access the entity by querying the flattened database view for a single entry associated with a combination of the user and the entity; and

return an indication of whether the user has permission to access the entity.

17. The non-transitory machine-readable storage medium of claim 16, wherein to flatten the permissions database, the instructions to cause the processing device to:

identify a first entity for which the user has explicit permissions defined in the permissions database;

identify a second entity that is a child of the first entity using a labeling hierarchy of entities;

identify the role to which the user is assigned;

identify a third entity for which the role has permissions defined in the permissions database;

identify a fourth entity that is a child of the third entity using the labeling hierarchy of entities; and

create a separate entry in the flattened database view for each unique combination of the user and one of the first, second, third and fourth entities.

18. The non-transitory machine-readable storage medium of claim 16, wherein to determine whether the user has permission to access the entity, the instructions to cause the processing device to issue a single query to the flattened database view for an entry comprising the user and the entity.

19. The non-transitory machine-readable storage medium of claim 18, wherein the indication of whether the user has permission to access the entity is affirmative if the entry in the flattened database view comprising the user and the entity is located.

20. The non-transitory machine-readable storage medium of claim 18, wherein the indication of whether the user has permission to access the entity is negative if the entry in the flattened database view comprising the user and the entity is not located.