2.1 Minimum Requirements

NESCM has the following minimum requirements:

2.1.1 eDirectory Server

eDirectory 8.8 SP1 or later on one of the following platforms:

  • NetWare 6.5 SP6 or later

  • Windows Server 2003 SP1 or later and Windows 2008 32-bit

  • SUSE Linux Enterprise Server (SLES) 10 32‑bit or 64‑bit

  • SUSE Linux Enterprise Server (SLES) 11 32‑bit or 64‑bit

  • Red Hat AS 4.0 Server 32‑bit or 64‑bit

  • Red Hat Enterprise Linux (RHEL) 5 32‑bit or 64‑bit

  • Solaris 10 on Sun SPARC 32-bit

2.1.2 Client Workstations

  • Novell Client 4.9.1 SP5 IR1 or later installed on Windows XP SP2 or later

  • Novell Client 2 SP2 (IR2a) for Windows Vista or later installed on Windows Vista (32-bit and 64-bit)

  • Novell Client 2 SP2 (IR2a) for Windows 7 or later installed on Windows 7 (32-bit and 64-bit)

  • Novell Client 2 SP2 (IR2a) for Windows Server 2008 (32-bit and 64-bit) and Windows Server 2008 R2 (64-bit)

  • iManager version 2.7 SP3 with NMAS plug-in version 3.200.20090408

The NESCM iManager plug‑in has the ability to query certificate information directly from smart cards. This functionality is supported on Windows with the following browsers:

  • Internet Explorer* 6.0 SP2 or later

  • Mozilla Firefox* 3.6.x / 4.x.x / 5.x.x /6.x.x /7.x.x/8.x.x

    Firefox 4.0 and later accepts SSL certificates signed by CAs that are natively trusted by Firefox for plug-in installation. To install the NESCM plug-in over an SSL connection, set the extensions.install.requireBuiltInCerts to false in the Firefox configuration.

    • Launch Firefox, then type about:config in the address bar of the browser window.

    • On the configuration page that displays, right-click to open the Modify Menu.

    • Select New > Boolean, then specify the new preference name as extensions.install.requireBuiltInCerts in the dialog box and set this option to false.

    • Install the NESCM card reader plug-in for Firefox.

A smart card reader and appropriate smart card middleware must be installed and properly configured on the workstation. The method should work with most Windows compliant PC/SC middleware. It has been tested with the following:

Table 2-1 Middleware, Smart Card Readers, and Smart Cards


Tested Applications


  • Netsign* CAC version

  • Gemplus* version 3.2.2 and 4.2

  • GemSAFE libraries 4.2

  • Gemalto PKCS11 For .NET V2+

  • GemCCID (PC USB PC/SC drivers)

  • ActivCard* Gold for CAC 3.0.1

  • ActivClient* 6.0 PKI Only or later

  • Cryptovision cv act sc/interface 3.2.1

  • eToken* Run Time Environment 3.60

  • CIP 4.07

  • FNMT Cryptographic Card Interface (Infineon, ST, ST-WG10). RSA keys up to 2048

Smart Card Readers

  • SCM Microsystems* SCR241 PCMCIA

  • SCM Microsystems SCR 131 Serial (RS232)

  • Cherry G83-6759LPAUS-2 USB Keyboard

  • Gemplus GemPC433-SL USB

  • Schlumberger Reflex 72v2

  • Schlumberger Reflex USB

  • SCM Microsystems SCR531-USB

  • Precise Biometrics 250 MC

  • ActivIdentity* USB Reader 2.0 and 3.0

  • ActivCard ActivCard USB Reader V3.0

  • C3P0 LTC3X USB Smart Card Reader v1.30

Smart Cards

  • Axalto Access 64K CAC

  • Gemplus GemXpresso* CAC

  • Gemalto .NET V2+

  • Oberthur CosmopolIC V4 CAC

  • Schlumberger Access 32K V2 CAC

  • Gemplus GemSAFE* SDK GPK16000

  • Cryptovision - CardOS M4.01a

  • Aladdin* - eToken PRO 64K

  • Oberthur CosmpolIC 64K V5.2 Fast ATR (PIV)

  • FNMT-RCM_ST_v2.0 (Ceres Card)