Merge and replace actions for security assets

If a security asset with the same identity exists in the target repository, then the new asset is merged with the existing asset.

The merge rules depend on the type of the security asset:
User
If a matching user exists in the target repository, the import implements the following merge rules:
  • All empty or null attributes of the existing user are replaced by the attributes from the imported user.
  • A union is made of all group memberships between the existing user and the imported user. That is, any group memberships of the imported user that do not already exist for the target user are added to the target user.
  • A union is made of all user roles between the existing user and the imported user. That is, any user roles of the imported user that do not already exist for the target user are added to the target user.
  • The user credentials of a target user are not overwritten by the user credentials of the imported user.
  • The credential mappings of a target user are not overwritten by the credential mappings of the imported user. If the target user has no credential mappings, then the import creates the credential mappings of the imported user.
Group
If a matching user exists in the target repository, the import implements the following merge rules:
  • All empty or null attributes of the existing group are replaced by the attributes from the imported group.
  • A union is made of all user memberships between the existing group and the imported group. That is, any user memberships of the imported group that do not already exist for the target group are added to the target group.
  • A union is made of all group roles between the existing user and the imported user. That is, any group roles of the imported group that do not already exist for the target group are added to the target group.
Parent topic: Import command for security assets