Database data source - Card Synchronization 3.4.2

Card Synchronization Plugin Guide 3.4.2

Applies to
Card Synchronization 3.4.2
Last updated
2023-01-27
Content type
Guides > Plugin and extension guides
Language
English
Product
Card Synchronization
Version
3.4

To import entities into Security Center from a database, the views in the database must follow the Card Synchronization schema.

A database must include one view for each of the entity types you want to import. A view for each of the following can be included in your database:
  • Cardholders
  • Cardholder groups
  • Cardholder group members
  • Credentials

Custom fields can be configured and mapped to add additional data to cardholders, cardholder groups, and credentials. This is not applicable if you are using the legacy database data source from Card Synchronization plugin 3.0.

Each view has mandatory and optional columns, depending on what information is contained in the database view.

  • All columns must be included in the database view.
  • Mandatory columns must be filled.
  • Column names and values are case sensitive.
  • For credentials using custom card formats, you must create corresponding custom card formats in Security Center.
  • For each custom field you add, you must create a corresponding custom field in Security Center.
Best Practice: To minimise the chance of accidental modification of data, configure your database data source from a user with read-only privileges on the database.