Implementation Guide › Managing Identities and Access › Customization and Extensibility

Customization and Extensibility

You customize these CA IdentityMinder features:

• The CA IdentityMinder directory, which describes a user store structure to CA IdentityMinder.
• The appearance and functionality of the user interface.
• User entry screens, which determine the fields and layout of each task screen.
• Validation of user data entry, through regular expression, JavaScript, or Java implementations.
• Workflow, which defines automated workflow processes. Create or modify processes by linking approvers and actions in the WorkPoint Process Designer.
• Email messages, which inform users of a task’s status.
• Task submission, which can be sent by a third-party application to the CA IdentityMinder Task Execution Web Service (TEWS). TEWS processes the remote task request. Remote task requests comply with WSDL standards.

You can extend CA IdentityMinder’s functionality using the following APIs:

• Logical Attribute API—Enables you to display an attribute differently than how it is stored physically in a user directory.
• Business Logic Task Handler API—Allows you to perform custom business logic during data validation or transformation operations.
• Workflow API—Provides information to a custom script in a workflow process. The script evaluates the information and determines the path of the workflow process accordingly.
• Participant Resolver API—Enables you to specify the list of participants who are authorized to approve a workflow activity.
• Event Listener API—Enables you to create a custom event listener that listens for a specific CA IdentityMinder event or group of events. When the event occurs, the event listener can perform custom business logic.
• Notification Rule API—Lets you determine the users who should receive an email notification.
• Email Template API—Includes event-specific information in an email notification.

Note: For more information on the CA IdentityMinder APIs, see the Programming Guide for Java.

When CA IdentityMinder includes provisioning, you can also extend provisioning functionality as follows:

• Custom connectors—Enable communication between a Provisioning Server and an endpoint system. The code that makes up a connector can include a GUI plug-in, server plug-in, and agent plug-in.

  A dynamic connector can be generated by Connector Xpress, and a custom static connector can be developed in Java or C++.

  Note: For more information, see the Connector Xpress Guide.

• Program exits—Let you reference custom code from the Provisioning Server process flow.

Note: For more information about extending provisioning functionality, see the Programming Guide for Provisioning, which is available in the Legacy Components media.