Skip to content
Søren Granfeldt edited this page Dec 1, 2016 · 5 revisions

NOTICE: This element/function is deprecated (use ConditionalRename instead)

The RenameDnFlow element allows for specifying information for performing renames in a connector space. Renames are typically used against LDAP source, such as Active Directory for moving objects between OUs.

Currently, the rename supports changing the DN or any other primary key. It is also possible to perform de-provisioning and (re-)provisioning instead of an actual rename. This is useful for systems, such as SAP, that does not support renaming.

  • Source element - This is the source attribute containing the new anchor value, e.g. distinguishedName could be used against Active Directory. Allowed values are the name of any metaverse attribute.
  • Target element - This is the target attribute (anchor) that holds the value to be renamed. If you specify the target value {"[DN]"} including the surrounding brackets the built-in DN value in FIM will be used for the target; this is useful with the Active Directory Management Agent if you wish to move objects between OU’s. Allowed values are {"[DN]"} or the name of a valid connector space object attribute.
  • ProvisionOnRename element - This is a Boolean specifying whether a de-provisioning and re-provisioning should be done upon rename (if values of source and target attributes are different). This is useful for systems that does not support rename, i.e. current versions of SAP. Note that the current version has the restriction that if multiple provisioning rules targets the same MA, you should only include the rename rule on one of the [rules]. Allowed values are 'true' or 'false' (case-sensitive).
Clone this wiki locally