Patent ID: 8375113
Filing Date: 2013-02-12
Classification: G06F,H04L

Abstract:
1. A method of controlling profile access, comprising the steps of: identifying a first and second profile each including multiple objects and attribute sets, the first and second profiles each configured to identify an entity in a directory server, wherein each of the attribute sets describing at least one trait of each entity, and wherein each attribute set is included in each of the multiple objects; identifying a template for each attribute set including configuration information other than schema information for at least one attribute in each attribute set; configuring the first and second profiles by configuring each attribute set, based at least in part on the configuration information, wherein each attribute set includes at least a first attribute of a first type and a second attribute of a second type, and wherein the first attribute of the first profile is set to a first value and the first attribute of the second profile is set to a second value; creating a wrapper profile for the first profile, wherein: setting a locking state of said locking status attribute of said wrapper profile for said first profile by a first entity, wherein when said locking status attribute of said wrapper profile is locked, said first profile is locked and not accessible by another entity for writing or modifying, and wherein when said locking status attribute of said wrapper profile is locked, said first profile is accessible for viewing by the first entity or a second entity; performing a task related to said first profile after said setting step is performed, which setting step causes said first profile to be not locked and accessible by another entity, shared and accessible by a plurality of entities, or locked and not accessible by another entity; enabling provisioning of said first profile using a provisioning system, said provisioning system receiving a request from a provisioning bridge server to grant or remove access to an external resource, and said provisioning bridge server being coupled to said directory server, wherein said provisioning bridge server uses said wrapper profile to ensure that said first profile is not being locked by said second entity; determining said wrapper profile is no longer needed for the first workflow; and in response to determining said wrapper profile is no longer needed for the first workflow, deleting said wrapper profile.