Skip to main content
Skip table of contents

Deduplication Policies

Definition

A Deduplication Policy describes how duplicates should be searched for when creating a managed object. 

If and only if the Policy is activated, the Policy will check defined Attributes on the Deduplication Scope each time an Object is created and updated (if and only if the "Check Duplicates On Update" is set to ON).

Configuration

You can access the Deduplication Policy configuration :

  • by clicking on "Policy" → “Deduplication Policy”

  • by clicking on "System" → "Configurations" → "Data Model" and perform an import/export.

Properties - Informations

Property name

Type

Mandatory

Description

Values (default value in bold)

id

String

YES

The identifier is the unique identifier of each Deduplication Policy.

It is case sensitive and no special characters (except - or _) are allowed.

-

name

String

YES

The Deduplication Policy name.

The name may be different from the identifier.
Specifying the name at first allows to automatically define the identifier.
Must be at least 4 characters long.

-

active

Boolean

NO

Allows to define if the Deduplication Policy is activated or not.

ON, OFF

description

String

NO

Allows to describe the purpose of the Deduplication Policy.

-

objectKind

Enum

YES

Allows to link the Deduplication Policy to an Object kind.
The Policy will apply to this Object kind.

Identity, Organization, Resource, Role, Role Publication

Properties - Assignment

Property name

Type

Mandatory

Description

Value (default value in bold)

priority

Integer

YES

Indicates the priority of the Policy when resolving which Policy to apply on an Object (1 having more precedence).

If the Object is part of the Deduplication Scope of several Policies, the Policy with the highest prority will be taken into account.

Setting the priority for Policies which have the same Object kind is forbidden.

0, 1, 2, 3...

assignmentScope

Scope

YES

Allows to configure on which Identities the Deduplication Policy will be applied.

It is possible to define several Identity Types.

-

Properties - Deduplication

Property name

Type

Mandatory

Description

Value (default value in bold)

transformRule

Script

NO

The transform rule can be used to generate context variables from the existing context information. Those variables will be available on the search expression when it is resolved.

Use Attributes related to the Object to calculate a variable that will be used in the search expression.

Only on searchable Attributes.

-

scope

Scope

YES

Allows to configure on which objects and in particular on which attributes the Policy will have to compare the duplicated objects.

-

checkDuplicatesOnUpdate

Boolean

NO

Allows to indicate whether or not duplicates should be checked when updating an object.

ON, OFF

Example

Deduplication Policy Example
XML 
<?xml version="1.0" encoding="UTF-8"?>
<kit:DataSet xmlns:atlastcf="http://www.memority.com/atlas/tcf/1_0" xmlns:ctd="http://www.memority.com/citadel/1_0" xmlns:ctdcore="http://www.memority.com/citadel/core/1_0" xmlns:ctdidm="http://www.memority.com/citadel/idm/1_0" xmlns:ctdrep="http://www.memority.com/citadel/rep/1_0" xmlns:ctdrule="http://www.memority.com/citadel/rule/1_0" xmlns:ctdtnt="http://www.memority.com/citadel/tnt/1_0" xmlns:i18n="http://www.memority.com/toolkit/addons/i18n/1_0" xmlns:kit="http://www.memority.com/toolkit/1_0" xmlns:netfilter="http://www.memority.com/toolkit/network-filtering/1_0" xmlns:rule="http://www.memority.com/toolkit/rule/1_0" xmlns:ruleaddon="http://www.memority.com/toolkit/addons/rule/1_0" xmlns:search="http://www.memority.com/toolkit/search-expression/1_0" xmlns:settings="http://www.memority.com/toolkit/addons/settings/1_0" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <ctdidm:DeduplicationPolicy id="internal-deduplicationPolicy">

      <name>Internal Deduplication Policy</name>
      <description>Internal Deduplication Policy ex</description>
      <assignmentPriority>1</assignmentPriority>
      <assignmentScope type="EXPRESSION" objectKind="IDENTITY">
         <searchExpression>
            <search:And/>
         </searchExpression>
         <objectTypes>
            <objectType>internal</objectType>
         </objectTypes>
      </assignmentScope>
      <scope type="EXPRESSION" objectKind="IDENTITY">
         <searchExpression>
            <search:And>
               <search:Prop op="LIKE" name="lastName">
                  <value script="true">OBJECT.lastName</value>
               </search:Prop>
               <search:Prop op="LIKE" name="firstName">
                  <value script="true">OBJECT.firstName</value>
               </search:Prop>
            </search:And>
         </searchExpression>
         <objectTypes>
            <objectType>internal</objectType>
         </objectTypes>
      </scope>
      <objectKind>IDENTITY</objectKind>
      <active>true</active>
      <checkDuplicatesOnUpdate>false</checkDuplicatesOnUpdate>
   </ctdidm:DeduplicationPolicy>
</kit:DataSet>

Read Next

Business Policies — A Business Policy allows to configure how to trigger actions on Object Types through a Feature with an optional configured Workflow.
Object Policies — An Object Policy is an Identity Management Service Policy allowing to execute arbitrary actions on Managed Objects, either on a scheduled basis, or in reaction to an Object Operation.
Deduplication Policies — A Deduplication Policy describes how duplicates should be searched for when creating a managed object.
Feature Access Policies — A Feature Access Policy is composed of a right which encompasses several Features.
Manual Provisioning Policies — A Manual Provisioning Policy allows to define that manual provisioning or deprovisioning Workflow is launched when the Role assignment status changes.
Object Lifecycle Policies — An Object Lifecycle Policy allows to configure rules, on all Object Types, that will alter an Object attribute directly when certain lifecycle events occur.
Password Policies — A Password Policy determines how passwords should be composed and which rules apply to their lifecycle.
Role Request Policies — A Role Request Policy allows to define if a Role can be requested, for whom, by whom, and using which Workflow.
Workflow Administration Policies — A Workflow Administration Policy is composed of a right which encompasses several Features.
Memority MFA Account Policies — A Memority MFA Policy allows to configure how multi factor authentication should be applied to a population of user
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close