CA Identity Manager Implementation Guide - CA Technologies

Transforming Data in the User Store■Policy Validation through Smart ProvisioningCA Identity Manager administrators can validate proposed changes toprovisioning roles and user attributes against Business Policy Rules (BPRs) inCA RCM before committing changes. BPRs represent various constraints onprivileges. For example, a BPR may prevent users who have a purchasingdepartment role, which allows members to order stock from subcontractors,from also having the subcontractor payment role. A system administrator,business manager, auditor, or role engineer creates BPRs in CA RCM.Note: For more information about BPRs, see the CA RCM Sage DNA UserGuide.Note: For more information about preventative identity policies and SmartProvisioning, see the CA Identity Manager Administration Guide.Transforming Data in the User StoreIn some cases, you may want CA Identity Manager to transform data before it isstored in the user store. For example, you may want to store information in adifferent format than it is entered, or you may want changes applied whencertain types of information are present.CA Identity Manager includes the following features for transforming data:■■Identity PoliciesLogical Attribute HandlersNote: You can also use identity policies and logical attribute handlers toimplement custom business logic.Logical Attribute HandlersLogical attribute handlers are custom Java code that transform user attributevalues used on Identity Manager task screens. Using logical attribute handlers,you can control how a physical attribute is displayed on a task screen. You canalso use logical attribute handlers to transform a display value, such as cost, onthe task screen to one or more physical attributes, such as unit price andquantity, that are stored in the user store.Note: For more information about logical attribute handlers, see theProgramming Guide for Java.26 Implementation Guide