Late constraint management

Patent metadata

Field	Value
Publication number	US-9818085-B2
Application number	US-201414150015-A
Country	US
Kind code	B2
Filing date	Jan 8, 2014
Priority date	Jan 8, 2014
Publication date	Nov 14, 2017
Grant date	Nov 14, 2017

Abstract

A method and system for integrating restrictions in an identity management system is provided. The method includes generating a role/account attribute table storage from static and dynamic rule defined values. A role request for a first role associated with a user is received and a set of attributes comprising a result of the role request are calculated. The set of attributes are transmitted to a target system for evaluation and a result is received.

First claim

What is claimed is:

1. A memory storage compliance method comprising:
dynamically generating, by a computer processor of an identity management system, a role/account attribute table for memory device storage from static and dynamic rule defined values such that a resulting set of attribute values are linked to an originating role, wherein said role/account attribute table comprises:
a plurality of rows, wherein each row of said plurality of rows comprises a an originating role associated with computer access control: and
a plurality of columns intersecting said plurality of rows to define said attribute values:

calling, by said computer processor, an internal and external programmatic function resulting in execution of a set of conflicting values based on constraints within a target computer system comprising a resulting set of attribute values linked to said originating role of said role/account attribute table:
mapping, by said computer processor executing said internal and external programmatic function, a set of roles to said set of attribute values for storage in said role/account attribute table, wherein said mapping is executed with respect to mapping/joining set operations and programmatic scripting computer functions;
receiving from said set of roles, by said computer processor from a user, a role request for a first role associated with said user;
calculating, based on said mapping by said computer processor, a set of attributes and associated parent role details comprising a result of said role request;
storing, by said computer processor within a role attribute map data store comprising said role/account attribute table storage, said set of attributes and said associated parent role details;
requesting, by said computer processor executing a policy enforcer component, a constraint compliance check with respect to said set of attributes executed by an external constraint provider component, wherein said external constraint provider component is external to said identity management system;
transmitting, by said computer processor to a target system in response to said requesting, said set of attributes, wherein said target system evaluates said set of attributes for constraints;
generating, by said computer processor based on said target system evaluating said set of attributes for constraints, a false reading for attributes of said set of attributes;
flagging, by said computer processor based on said false reading, said first role as an external violation;
receiving, by said computer processor based on said flagging, a result of said target system evaluating said set of attributes for constraints such that said role attribute map data store retrieves specified parent roles from said associated parent role details for non-compliant attributes of said set of attributes;
determining, by said computer processor, based on results of said calling, said mapping, and said flagging, memory storage conflicts associated with storing said mapping/joining set operations and programmatic scripting computer functions; and
removing, by said computer processor based on said non-compliant attributes, said first role from said role request thereby resolving said memory storage conflicts and system limitations resulting in a provisioning solution for non-compliant memory storage.

2. The method of claim 1 , wherein said result indicates that said set of attributes does not comprise constraints, and wherein said method further comprises:
receiving, by said computer processor from said target system, a message indicating a success status.

3. The method of claim 1 , wherein said result indicates that said set of attributes comprises constraints, and wherein said method further comprises:
receiving, by said computer processor from said target system, account attribute value constraints indicating said constraints;
enabling, by said computer processor, said role/account attribute table storage;
expressing, by said computer processor in response to said enabling, said account attribute value constraints as role constraints;
executing, by said computer processor, an identity management process for management of said role constraints; and
generating, by said computer processor, results of said executing.

4. The method of claim 1 , wherein said executing said identity management process comprises:
mapping said role constraints to a set of similar constraints of said role/account attribute table storage; and
generating a remedy action associated with said role constraints.

5. The method of claim 4 , wherein said remedy action comprises an action selected from the group consisting of removal of roles from said role request and approval of exceptions for said role request.

6. The method of claim 1 , further comprising:
evaluating, by said computer processor, a separation of duty on programmatic assigned values for said set of attributes.

7. The method of claim 1 , wherein said role/account attribute table storage comprises a role column, an entitlement parameter column, an account attribute value column, an existing account attribute value column, an account attribute value join policy column, and a final account attribute value column.

8. The method of claim 1 , further comprising:
providing at least one support service for at least one of creating, integrating, hosting, maintaining, and deploying computer-readable code in the computing system, said code being executed by the computer processor to implement: said dynamically generating, said receiving said role request, said calculating, said storing, said transmitting, and said receiving said result.

9. A computing system comprising a computer processor coupled to a computer-readable memory unit, said memory unit comprising instructions that when executed by the computer processor implements a memory storage compliance method comprising:
dynamically generating, by said computer processor, a role/account attribute table for memory device storage from static and dynamic rule defined values such that a resulting set of attribute values are linked to an originating role, wherein said role/account attribute table comprises;
a plurality of rows, wherein each row of said plurality of rows comprises a an originating role associated with computer access control; and
a plurality of columns intersecting said plurality of rows to define said attribute values;

calling, by said computer processor, an internal and external programmatic function resulting in execution of a set of conflicting values based on constraints within a target computer system comprising a resulting set of attribute values linked to said originating role of said role/account attribute table;
mapping, by said computer processor executing said internal and external programmatic function, a set of roles to said set of attribute values for storage in said role/account attribute table, wherein said mapping is executed with respect to mapping/joining set operations and programmatic scripting computer functions; receiving from said set of roles, by said computer processor from a user, a role request for a first role associated with said user;
calculating, based on said mapping by said computer processor, a set of attributes and associated parent role details comprising a result of said role request;
storing, by said computer processor within a role attribute map data store comprising said role/account attribute table storage, said set of attributes and said associated parent role details;
requesting, by said computer processor executing a policy enforcer component, a constraint compliance check with respect to said set of attributes executed by an external constraint provider component, wherein said external constrai

Assignees

• IBM

Inventors

• Larsen Rune H
• Moore David P
• Wolfhagen Franz

Classifications

• G06F2221/21

  Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity · CPC title

• G06Q10/103 Primary

  Workflow collaboration or project management · CPC title

• G06F21/00

  Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity · CPC title