4.7 User Application Driver

The User Application driver is responsible for:

  • Storing application-specific environment configuration data.

  • Notifying the directory abstraction layer when important data values change in the Identity Vault. This causes the directory abstraction layer to update its cache.

You can configure the User Application driver to:

  • Allow events in the Identity Vault to trigger workflows.

  • Communicate the success or failure of a workflow's provisioning activity back to the identity applications database, which allows users to view the final status of their requests.

  • Start workflows automatically in response to changes of attribute values in the Identity Vault.

The User Application driver is both a runtime component and a storage wrapper for directory objects (comprising the runtime artifacts of the identity applications).



Driver Set Object

Every Identity Manager installation requires that drivers be grouped into driver sets. Only one driver set can be active at a time (on a given directory server). The drivers within that set can be toggled on or off individually without affecting the driver set as a whole. The User Application driver like any other Identity Manager driver, must exist inside a driver set. The driver set is not automatically created by the identity applications; you must create one, then create the User Application driver within it.


The User Application driver object is the container for a variety of artifacts. The User Application driver implements Publisher and Subscriber channel objects and policies. The Publisher channel is not used by the identity applications but is available for custom use cases.

App Config Object

The AppConfig object is a container for the following identity applications configuration objects.

  • RequestDefs: Container for Provisioning Request Definitions. The definitions stored here (as XML) represent the classes of requests that end users with appropriate rights can instantiate through the identity applications.

  • WorkflowDefs: Container for Workflow objects, including design-time descriptions plus any template or unused flows.

  • ResourceDefs: Container for Provisioned Resource definitions, including design-time descriptions plus any templates or unused targets.

  • ServiceDefs: Container for Service Definition objects, which wrap Web Services called by workflows.

  • DirectoryModel: Directory abstraction layer objects that represent different types of content of the Identity Vault that can be exposed in the identity applications.

  • AppDefs: Container for configuration objects that initialize the runtime environment, such as cache configuration information and email notification properties.

  • ProxyDefs: Container for proxy definitions.

  • DelegateeDefs: Container for delegate definitions.