SDK Overview

This section serves as an introduction to the process of developing custom components and extensions to ActivID CMS, and it provides descriptions and examples that explain the following topics:

• Using the ActivID CMS SDK and its components

• Choosing an SPI Fast Identity Online/API In the context of ActivID CMS, an Application Programming Interface (API) is an external interface (for example, the CCM API) that makes it possible for applications not supported by HID Global to incorporate ActivID functionality. and enabling plug-in debug logs

• Integrating ActivID CMS functions into custom applications with use case examples that describe:

• Managing and synchronizing devices using a custom application

• Supporting a third-party certificate authorities (CAs) using Credential Provider Service Provider Interface (SPI)

• Getting notification of ActivID CMS events using the Event Notification plug-in

• Customizing ActivID CMS device issuance to enroll or verify user attributes using the Generic plug-in SPI

• Fetching cardholder attributes from non-LDAP directories using the Generic plug-in SPI

• Storing additional static data Cardholder-related information including things such as health benefits, biometrics, unique organizational identifiers, or unique personal identifiers that rarely change. on devices using the Static Data Collection plug-in SPI

For additional information about the ActivID Credential Management System, refer to:

• About the CCM API

• About the Credential Provider Service Provider Interface (SPI)

• About the Event Notification Plug-in SPI

• About the Generic Plug-In SPI

• About the Static Data Collection Plug-In SPI

Topics in this section: