Architecture

Until ActivID CMS 5.10, we provided a Java and C SDK including a SOAP client for the CCM Card and Credential Management API. The typical integration involves a Java or C application linking to the ActivID CMS SDK to both interact with the ActivID CMS server and the device plugged in. These SDKs are still available.

With the extension of the REST API for device issuance in ActivID CMS 5.10, we move to a new integration scheme where the application is a Single-Page Application (SPA) running in a Chrome™-based browser.

It is assumed that the SPA has a back end with customer services. The back end sends requests to the ActivID CMS server after being authenticated.

The SPA interacts with the device plugged in the machine through the ActivID CMS Chrome Extension and the ActivID CMS Client. If written in Angular, the SPA can also benefit from the CMS Angular Service that facilitates this integration.

ActivID CMS Client

The ActivID CMS Client is a native executable program used by the browser to exchange data between a device and the ActivID CMS server during a Synchronization.

The Operator Portal and the User Portal automatically propose to download and install the ActivID CMS Client if it is missing. The .msi installation file can be downloaded from the ActivID CMS server.

ActivID CMS Extension

The ActivID CMS extension is a Chrome component that facilitates communication between the web front end (for example, the Operator Portal) and the ActivID CMS Client.

The extension works for both the Google Chrome and the Chrome-based Microsoft Edge browsers.

The Operator Portal and the User Portal automatically propose to download and install the ActivID CMS extension if it is missing. It is available in the Chrome store: https://chrome.google.com/webstore/detail/activid-cms-extension/ddfoinleihmgpkhfmemkncgffilfahnm