Oracle International Corporation

Joan C Teng

Thomas B Remahl

Richard Sinn

Sachin Agarwal

Chi-Cheng Lee

Srinivasagopalan Ramamurthy

Technology is disclosed for using workflows based on domains in a hierarchical data structure (e.g. LDAP directory) or other type of data structure. When a workflow is created, it is associated with domain. The domain is defined by a selected node and all nodes below that selected node in the hierarchical data structure. At run time, the system identifies which workflows perform a requested task and are associated with a domain that includes the target of the task. If multiple workflows are determined, the user is provided with the ability to choose one of the identified workflows for performing the tasks.

Domain based workflows

An Identity System manages certificate related actions for organization members and affiliates. Examples of certificate related actions include certificate enrollment, renewal, and revocation. The Identity System maintains and employs different certificate related workflows for different organization members and affiliates. After receiving a request for a certificate related action, the Identity System retrieves a workflow for responding to the request. The Identity System selects the workflow from a plurality of workflows for responding to the type of certificate related action being requested. Each workflow in the plurality corresponds to a different set of user characteristics. The Identity System selects the workflow that corresponds to the requested certificate related action, as well as the type of user for which the request is made.

Employing electronic certificate workflows

Workflows are used to automate processes. When a first workflow is performed, it may invoke a set of one or more nested workflows, workflows in other applications or services in other applications. The first workflow can be configured to pause and wait for the invoked set of one or more nested workflows, workflows in other applications, or services in other applications. Alternatively, the first workflow can be configured to proceed without waiting. Various means are disclosed for re-staring the first workflow and providing data back for the first workflow.

Workflows with associated processes

Technology is disclosed for defining workflows based on a template. The template defines a set of parameters for actions available to various workflow types. In one embodiment, the template is an XML document that is used to determine a set of options to provide a user via a graphical user interface. The user selects the options desired and the resulting workflow definition is stored for later use. Any entity with sufficient access privileges can start and/or participate in a workflow that operates according to the stored workflow definition.

Template based workflow definition

The present invention is directed to technology for using a proxy in an Identity System. When a first entity is on vacation, on a business trip or otherwise unavailable to perform certain actions on an Identity System, a second entity can act as a proxy for the first entity. The Identity System will provide the second entity, acting as a proxy, with the privileges, access and rights of the first entity. In one embodiment, Identity System is part of an integrated Identity and Access System, and the second entity is a proxy in the Identity System but not in the Access System.

Proxy system

Technology is disclosed for limiting the number of central data store accesses required when performing a series of steps, such as a workflow. A local data store is coupled between a central data store and a system carrying out a workflow. Alternatively, a Transfer Engine is coupled between the local data store and the central data store to transfer data between the local data store and central data store. The Transfer Engine allows the data formats in the central data store and local data store to be independent of each other. During a workflow step, the system stores attributes related to the workflow in the local data store&#x2014;updating modified attribute values and creating entries for newly added attributes. The system determines whether any attributes in the central data store need to be updated with attribute information from the local data store. The system only updates the central data store with local data store attribute values for new and modified attributes when necessary&#x2014;avoiding central data store updates after every workflow step.

Employing local data stores to maintain data during workflows

An identity management system manages identity profiles that store information about various entities. A localized access feature for an identity management system allows for a set of identity profiles to be grouped together in order to define a locale. Users outside the locale can be restricted from accessing identity profiles inside the locale. Alternatively, users outside the locale can be restricted from accessing certain attributes of identity profiles inside the locale.

Growing community of inventors

Foster City, CA, United States of America

Joan C Teng