Transformation (3c. Permission Mapping)

note

Warning: this flow will overwrite the target.principals and target.permissions fields for ACL's!

This flow maps the principals and permissions on ACL objects using an Excel workbook. This is different than the Principal mapping flow. That flow transforms creators and modifiers on the content to be migrated. Because migrating permissions can be quite sensitive, the principals and permissions need to be mapped manually. Two sheets are mandatory: Principal Mapping and Permission Mapping. An example of these mappings is shipped with the accelerator (Permission mapping.xlsx).

The Principal Mapping sheet is used to transform the principals on the ACL object. The columns in this sheet are:

• *Source SystemName: Refers to the source.principals[].systemName of the principal.
• Source DisplayName: Refers to the source.principals[].displayName of the principal.
• Target SystemName: Refers to the system name of the target principal.
• Target DisplayName: Refers to the display name of the target principal.

The Permissions Mapping sheet is used to transform the principals on the ACL object. Only one permission will be set. The columns in this sheet are:

• *Source: Refers to the name of the permission in source.permissions.
• `Target: Refers to the name of the target permission.
• Priority: When there are multiple permissions, the priority determines which one is used. A lower value means higher priority here.

Settings

mongoConnection

The Mongo connection string including the database name to connect to.

permissionMappingPath

The path to the Excel workbook containing the principal and permission mappings. There should be two sheets: Principal Mapping and Permission Mapping.