Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Changed Identity Manager operator UI to Identity Manager Operator

When using Card SDK (via Identity Manager operator UIOperator) the encoding device needs to be set up in Card SDK Configuration Manager.

Prerequisites

Expand
titlePrerequisites

-

Step-by-step instructions

Expand
titleAdd encoding device
  1. In Card SDK Configuration Manager, open the Contact Chip Encoding property. The Chip: Device Setup dialog box opens.
  2. Click New... to add and configure a new device. The Chip: Select Device dialog box opens.
  3. Select the appropriate encoder or reader, in case of an integrated encoder, select the printer. Click OK.
  4. Select the JPKIEncoder and click OK.
  5. In the Encoding Device Setup dialog box, select the corresponding PC/SC Reader device.

    Note

    Nexus recommends to install the original driver software for the PC/SC Reader provided by the manufacturer.


Integrated chip encoding

For integrated chip encoding in a card printer, and depending on the printer model in use, it may be necessary/possible to choose the correct position of the integrated encoder.

  1. Select the newly created device in the Encoding Device Setup dialog box. As the chosen printer supports the Printer Encoding Position selection, the device-dependent button gets visible.
  2. Click the device-dependent button in the dialog to select the Printer Encoding Position for this device (RFID Chip or Contact Chip Position).


Expand
titleRestart service
  1. After the encoding device is configured, open the IDProductionService property in Configuration Manager and click Restart Service. For more information regarding  IDProductionService, see Initial setup of Configuration Manager.


Expand
titleJava Client Installation

On the local client, Smart ID Identity Manager connects via Java JRE to the Pkcs#11 Middleware Library. Therefore the Java JRE must be the same platform architecture (32 or 64 bit) like the Middleware library. In doubt, it should be safe to choose 32-Bit JRE.