IdM data export/import agenda export import zip batch

You can export data from the source IdM by using bulk operations over the appropriate agendas.

For example, if you want to export roles, then first select the appropriate roles in the role agenda and then run the Export Roles bulk operation. The result of this operation will be to create a new export batch in the Menu → Settings → Export/Import agenda. This export batch will contain all exported data that can be downloaded in ZIP format.

Import is performed in the target IdM, when in the same agenda Menu → Settings → Export/Import, we upload the batch that we exported in the source IdM (ZIP).

The import batch can then be run in the so-called demo mode. This mode serves to test what the given batch will actually change in the target IdM.

When we are sure that we really want to make the changes that the batch makes, we can proceed to the launch of the import itself.

Dry run is a mode where we first want to check what changes will be made to the target IdM. For example, due to authoritative mode, some objects that are not part of the imported batch may be deleted during import. Starting dry run mode allows us to find out what data will be deleted.

It also allows us to solve some error situations. This means, for example, a situation where the exported system contains provisioning brake provisioning, including the definition of specific recipients of notifications. These recipients can be defined by role or identity. However, these may not exist on the target IdM. In this case, the import would failed with an error because the recipient would not be found. If we run dry run mode in the same situation, we will see error results on the third tab "All modifications", which will indicate that the given recipient was not found. The message will also contain the recipient's code (identity or role) and thus we can create (before the import itself) the missing recipient according to the obtained code.

Each export of a given type of object is implemented as a separate bulk action, which ensures correct data export. The export action must also ensure that the export metadata is correctly created. Export metadata is the file export-batch.json, which is part of each exported batch. This file contains metadata, such as the batch name and a descriptors for each exported object type.

Export descriptors primarily define the order in which data is exported (the same order is used during import). In addition, each descriptor contains additional metadata that defines how the import should handle that type of object. The descriptor metadata also defines:

• Supports authoritative mode - Defines whether authoritative mode is enabled for this object type. If so, then the import removes other / redundant entities from the target IdM (for example, if the role contains additional guarantors that do not exist in the batch, they will be deleted).
• Parent fields - Defines name of parent fields. This contains UUID of entity for which was DTO exported. This is important for authoritative import, because we need to delete others entity from target IdM. Parent fields are uses for find ID of super parents for this batch (system, role, ..).
• Super parent filter property - Defines name of filter for find all DTOs existing under same super parent on target system. Super parent DTO ia typically system or role. This field is mandatory for authoritative mode. This property is uses for find specific setter in Filter POJO. It means setter must exists in filter!
• Advanced paring fields - Defines fields in DTO, where we need to use advanced paring strategy. It means that we need to check if UUID exists in target system. If not, we will use DTO from embedded map and try to find DTO by code.
• Optional - If is true and DTO will cannot be persisted, because some relation was not found, then only warning will be logged, but batch can continue.
• Excluded fields - Defines fields in DTO, which will be excluded during the import. It means this fields will be not changed on target IdM. If entity will not exists, then that fields will set to null. For example, the token in sync definition is excluded.

  Since version 10.6.0 is token field excluded from a import of system sync.

Version 10.2.0 implements export of roles, systems, application configurations, and some related objects (such as form definitions or catalogs …).

Roles are exports with this related objects:

• More information (EAV) (authoritative mode = off)
• Definition of assigned attributes (authoritative mode = on)
• Business roles (authoritative mode = on) * Incompatible roles (authoritative mode = on)
• Role authorizer - defined by role (authoritative mode = on)
• Role authorizer - defined by identity (authoritative mode = on)
• Role catalogue (authoritative mode = on). Besides a role catalog relation, the catalog definition itself is also exported. Only the catalog to which the role is linked is always exported and all catalogs defining the path to the root of the catalog tree. The catalogs themselves are not exported in authoritative mode (authoritative mode = off)
• Permissions (authoritative mode = on)
• Automatic roles - Version 10.2.0 doesn't implement export of automatic roles.
• Systems - Relation between role and system is not exported within role export. This relations are exported within export of systems.

  Systems

Systems are exports with this related objects:

• Connector configuration (authoritative mode = off)
• Connector pooling configuration (authoritative mode = on)
• Provisioning brake (authoritative mode = on) - Relations to a receivers are mandatory. It means a identities or roles using as receivers must exists in target IdM.
• System scheme (authoritative mode = on)
• System scheme attributes (authoritative mode = on)
• Mapping (authoritative mode = on)
• Attributes mapping (authoritative mode = on) - If a particular attribute maps an EAV attribute to an entity (such as identity), then the attribute definition is also added to the export.
• Role assigns account in systems (authoritative mode = on, optional = on) - Relations between system and roles are exports as optional. It means if some of a role isn't found on target IdM, then is that relation skipped (import will be continue). Within exporting of this relations are role-defined attributes also exported (authoritative mode = on, optional = on).
• Sync configuration (authoritative mode = on, optional=on) - Sync contract/slice configuration contains relation on a tree-type and tree-node object. If this objects will be not found (by ID or code), then whole configuration of the sync will be skipped (not updated, not created, not deleted).

  Since 10.6.0: Sync contract/slice configuration contains relation on a organization structure and organization node. If this objects will be not found (by ID or code), then whole configuration of the sync will be skipped (not updated, not created, not deleted)

Application configurations without authoritative mode.

For execute an export action you will need to have:

• Permission to autocomplete and read, update and create export batch: Export/Import (IdmExportImport) | View in select box (autocomplete), Read, Create, Update | BasePermissionEvaluator.
• Permission to see a progress bar: Scheduler (IdmLongRunningTask) | Autocomplete| BasePermissionEvaluator.
• Permission for read exported object. For example: To export a application configurations you need: Configuration (app) (IdmConfiguration) | Read | BasePermissionEvaluator.

For execute an import action in dry-run mode you will need to have:

• Permission to autocomplete and read, update and create export batch: Export/Import (IdmExportImport) | View in select box (autocomplete), Read, Create, Update | BasePermissionEvaluator.
• Permission to see a progress bar: Scheduler (IdmLongRunningTask) | Read | BasePermissionEvaluator.
• Permission to read import log: Export/Import (IdmImportLog) | Read | BasePermissionEvaluator.

For execute an import action you will need to have:

• Permission to admin export batch: Export/Import (IdmExportImport) | Administration (all) | BasePermissionEvaluator.

Performance testing took place with using numbers of Systems (specifically CSVDir system) with assigned several roles, set mapping etc. to increase overall number of entities to export. The goal was to find both particular time of duration and estimation of the export/import complexity.

• Testing was performed on NB (i7, 16GB RAM, SSD).
• Database (MSSQL) was placed on the SSD communicating with IdM via localhost only.
• System wasn’t running out of any resources during testing.

Following table shows number of testing systems and measured times of their export and import. The growth of the operation time is roughly linearly proportional to number of testing systems and by extension overall processed entities.

When importing a virtual system, you must make some further adjustments so the imported system behaves in the same way as the exported system. Especially if you use the "rights" attribute or if you changed or removed some of the default attributes. After you import the system:

• Go to Settings → Form definitions, search for the definition of type VsAccount and name containing the name of your system.
• Go to Form attributes, remove the attributes that are superfluous. For the attribute "rights", switch the checkbox "multivalued".

More info here.