Before you can import entities from an external system, you must set up your data sources, and configure Security Center so that the entities you want to import can be mapped properly.
What you should know
- For more information on creating custom fields, creating custom card formats, and backing up the Directory database, refer to the Security Center Administrator Guide.
- When importing entities from a file, validation for CardholderGroupMember and Credential fails if your data source configuration is not up to date, credentials are not unique, or if your data source does not respect the schema.
-
A cardholder can be removed from the groups during synchronization between data sources if that cardholder was added to imported cardholder groups in Security Center, but the cardholder is not a member of the groups in the external system.
To keep the cardholder, 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.
- When you import a credential and the related cardholder is missing from the data source, the import succeeds. You are not notified that the credential is not linked.
Procedure
- Make sure that your Security Center license supports a sufficient number of data sources.
- (For non-Azure AD data sources) Create a database view or delimited text files that follow the Card Synchronization schema.
-
If you have custom fields to import:
-
Click Save.
CAUTION:Do not delete the custom field after it is created by the plugin. Deleting the associated custom field causes the synchronization to fail.
-
Click Save.
- If the credentials you want to import use custom card formats, create corresponding custom card formats in Security Center.
- Implement the best practices for importing entities.
- Back up the Directory database, so that you can restore the database if you accidentally merge or duplicate entities during import.