Cardholders schema - Card Synchronization 3.0

Card Synchronization Plugin Guide 3.0

series
Card Synchronization 3.0
revised_modified
2018-08-29

For cardholders to be imported into Security Center, the database view or file for cardholders must follow the Card Synchronization schema.

NOTE:
  • Including pictures increases the amount of time it takes to import.
  • In database views, both mandatory and optional columns must be included.
  • In delimited text files, optional columns can be excluded.
Column Data type Description
Mandatory columns
UniqueId String A unique ID for the cardholder. The unique ID can be an alphanumeric code, an email address, or a Security Center GUID.
FirstName String The first name of the cardholder.
LastName String The last name of the cardholder.
Optional columns
EmailAddress String The email address of the cardholder.
Picture String A picture in the format of a blob, a base64 string, or a path to an image.

The path must be accessible from the server.

State Integer The value that sets the activation state:
  • 0 = Active
  • 1 = Expired
  • 2 = Inactive
NOTE: If there is a conflict between the state implied by the ActivationDateInUtc, the ExpirationDateInUtc, and the State, the state in Security Center will be set to inactive.
ActivationDateInUtc DateTime The date on which the cardholder becomes active. The date must be entered in the ISO 8601 format.
Example: 2018-06-28T22:15:00Z
ExpirationDateInUtc DateTime The date on which the cardholder expires. The date must be entered in the ISO 8601 format.
Example: 2018-06-28T22:15:00Z
AntipassbackExemption Boolean The value that enables or disables the Bypass antipassback rules option:
  • 0 = Disable
  • 1 = Enable
UseExtendedGrantTime Boolean The value that enables or disables the Use extended grant time option:
  • 0 = Disable
  • 1 = Enable
The following image is an example of a cardholders view in a Microsoft SQL Server database.