6.3 Creation - Require Attributes

This rule prevents User objects from being created unless the required attributes are populated. Implement the rule on the Subscriber Creation policy or the Publisher Creation policy in the driver.

There are two steps involved in using the predefined rules: creating a policy in the Creation policy set, and importing the predefined rule. If you already have a Creation policy that you want to add this rule to, skip to Importing the Predefined Rule.

6.3.1 Creating a Policy

  1. Open the Identity Manager Driver Overview for the driver you want to manage.

    For instructions on how to access the Identity Manager Driver Overview page, see Accessing the Identity Manager Driver Overview Page.

  2. Click the Creation Policy set object on the Publisher or Subscriber channel.

  3. Click Insert.

  4. Name the policy, make sure to implement the policy with the Policy Builder, then click OK.

    The Policy Builder is launched.

  5. Continue with Section 6.3.2, Importing the Predefined Rule.

6.3.2 Importing the Predefined Rule

  1. In the Policy Builder, click Insert.

  2. Select Creation - Required Attributes.

  3. Expand the predefined rule.

    Creation - required attributes

  4. To edit the rule, click Creation - Required Attributes in the Policy Builder.

    The Rule Builder is launched.

  5. In the Conditions section, click the Browse icon next to the Value field.

  6. Browse to and select the attribute you require for a User object to be created.

  7. (Optional) If you want more than one required attribute, click the plus icon to add a new action.

  8. Select Veto if operation attribute not available, then browse to and select the additional required attribute.

  9. Click OK twice.

6.3.3 How the Rule Works

This rule is used when your business processes require that a user has specific attributes populated in the source User object before the destination User object can be created. When a User object is created in the source data store, the rule vetoes the creation of the object in the destination data store unless the required attributes are provided when the User object is created. You can have one or more required attributes.