Limitations in the Card Synchronization plugin 3.0 - Card Synchronization 3.0

Card Synchronization Plugin Guide 3.0

series
Card Synchronization 3.0
revised_modified
2018-08-29

Limitations are software or hardware issues that cannot be fixed. For certain limitations, workarounds are documented.

The Card Synchronization plugin 3.0 includes the following known limitations:
Issue Description
1898460 You cannot import Azure AD pictures from an Azure AD data source.
Workaround: From Azure AD, assign the picture you want to import to the user as an Office 365 picture instead of an Azure AD picture.
1714451 If you delete an imported cardholder with a picture, and then reimport it, the cardholder's picture is not reimported.
Workaround: Restart the plugin.
1682319 If you change the global keys of a data source after entities are imported, strange behaviors occur when entities are merged.
Workaround: Before importing from a data source, make sure the global keys are set correctly. On the Properties page of the plugin, you can set the option Manual synchronization only to ON, so that you do not accidentally synchronize the wrong global key configuration.
1674832 When importing entities from a file, if your data source configuration is not up to date or if your data source does not respect the schema, validation for CardholderGroupMember and Credential fails.
1666830 When adding an ODBC data source for a Microsoft Access database, your ODBC drivers must use the same architecture (32-bit or 64-bit) as GenetecPlugin.exe. Otherwise, you receive a validation error.
1475199 If a cardholder was added to imported cardholder groups in Security Center, and the cardholder is not a member of the groups in the external system, the cardholder is removed from the groups during synchronization.
Workaround: Create a parent group, make the imported group a child of the parent group, and then add the cardholder to the parent group. You can use the parent group in access rules.
1137316 Activation and expiration dates in data sources must be configured in the ISO 8601 format. For example, 2018-06-28T22:15:00Z.

Custom fields in Security Center using the Date data type must also be configured in the ISO 8601 format.

1059707 Entities imported through Federation™ or the Active Directory cannot be modified by the plugin. Only custom fields linked to those entities can be synchronized.
1046123 If you import a credential that has the same type and same value in Security Center, you receive a warning, and the import fails.
NOTE: This limitation does not apply to PIN credentials. Duplicate PIN credentials can be imported.
Workaround: Use the Security Center data source to merge the entities.
1046122 If you import a cardholder that shares the same first and last name as an existing cardholder in Security Center, a duplicate cardholder is created.
Workaround: Use the Security Center data source to merge the entities.
1042106 When you delete the Card Synchronization plugin role, imported entities are not deleted from Security Center.
1041937 If you remove parts from your Security Center license, and can no longer support the number of data sources already added to the Card Synchronization plugin, the plugin turns red and is disabled.
Workaround: From Server Admin, restart the Directory to re-enable the plugin so that you can delete the additional data sources.
1019108 When you update a value to be NULL in a data source, the value in Security Center is not removed.
Workaround: Delete the entity from Security Center, and then start a synchronization to reimport it.