IDM 6.1.0 - Requirements and interoperability

This article provides installation requirements and interoperability data for Smart ID Identity Manager. 

Recommendations

Deployment and sizing considerations

Read the information under header "Deployment and sizing considerations" in Smart ID deployment recommendations.

Database recommendations

Read the information under header "Database recommendations" in Smart ID deployment recommendations.

Requirements

Databases

The following databases are supported:

• SQL Server 2017

• SQL Server 2019

• SQL Server 2022

• SQL Server 2025

• Azure SQL

• Oracle Database 19c

• Oracle Database 23ai

• PostgreSQL 15

• PostgreSQL 16

• PostgreSQL 17

For SQL Server and Azure SQL see also the transaction isolation level requirements here: Set transaction isolation level for MS SQL when used with Identity Manager

Client: Web browsers

All Identity Manager clients are executed in up-to-date HTML5 web browsers such as:

• Mozilla Firefox

• Google Chrome

• Safari

• Microsoft Edge (Chromium)

Identity Manager releases are always tested with the latest browser versions.

JasperReports

The following version of JasperReports is supported:

• Templates in JasperReports format (.jrxml) version 6.5.1 are supported

Capture or production client: Software

The following requirements apply for a workstation that is to be used as a capture client or production client: 

• Nexus Card SDK of the latest version is supported and must be installed. See here for information about the latest Card SDK version.

• Windows-based workstation (PC). For more information, see Card SDK requirements and interoperability.

For PKI cryptochip encoding the following is also required:

• A PKCS#11 compliant smart card middleware.

  • For a list of supported smart card middleware, see heading "Supported smart cards and middleware in Identity Manager".

• OpenJDK or Oracle Java

  • Version 11 (64-bit), tested on OpenJDK 11.0.6+10

  • Architecture: 32-bit (for any smart card middleware) or 64-bit (for any smart card middleware except Nexus Personal)

• The smart card middleware and client-side Java must have the same OS architecture, either 32-bit or 64-bit, since Identity Manager's encoding component connects from the client-side Java to the middleware.

PKI encoding via Self-Service: Software

The following requirements apply for the use of PKI cryptochip encoding features on Identity Manager Self-Service clients:

• Smart ID Desktop App of the latest version is supported and must be installed. See Smart ID Desktop App newsfor information about the latest Smart ID Desktop App version. For more information, see Smart ID Desktop App requirements and interoperability. 

• A PKCS#11 compliant smart card middleware must be installed.

  • For a list of supported smartcard middleware, see heading "Supported smart cards and middleware in Identity Manager".

Identity Manager war files deployment installation

The following requirements apply for Identity Manager war files deployment installations:

• Tomcat 11

• Java 21

Interoperability

Data connectors

Identity Manager allows synchronization of data with external systems for many different use cases, for example card data, employee data from corporate directories, and entitlements from physical access control systems. Import and export of data can be done for various formats, for example LDAP, JDBC, CSV and SCIM. 

Corporate directories

Identity Manager supports connection to directories compliant with the following standard: 

• LDAP v3

Microsoft Active Directory is a typical example of a supported directory.

For more information, see Integrate Identity Manager with Microsoft services.

JDBC databases

Identity Manager supports connection to databases based on Java database connectivity (JDBC).

The databases are the same as under heading Requirements > Databases.

The SQL Server and Azure SQL databases only support case insensitive queries (which is the default option).

Certificate authorities

The following certificate authority (CA) products and services are supported:

• Smart ID Certificate Manager

• Microsoft Active Directory Certificate Services (ADCS) 2012 / 2012 R2 / 2016 / 2019

• D-Trust Managed PKI

• DFN Managed PKI

• QuoVadis PKI

• Sectigo (User certificates only)

For more information, see Integrate Identity Manager with certificate authority (CA). 

Other CAs can be integrated on demand.

Physical access control systems (PACS)

See Supported PACS connectors for details about supported PACS connectors.

Mobile device management (MDM)

The following mobile device management (MDM) product is supported in Identity Manager:

• MobileIron 10.4 - 10.7

Other MDM systems can be integrated on demand.

Digital identities

Smart cards and middleware in Identity Manager

Supported smart cards depend on the smart card middleware. Smart card middleware is not part of Identity Manager.

Identity Manager connects to a smart card via the PKCS#11 library provided by the middleware. For a list of supported cryptochips and smart cards, see the corresponding technical specification of the middleware.

CardOS 4.4 and CardOS 5.0 are Nexus' reference cards for testing. Other cards listed in the middleware specification also normally work, but must be tested individually for the specific requirement.

The following smart card middleware products are supported: 

⁽¹⁾ 32 bit JVM no longer needed for PKI Card production through Card SDK.

⁽²⁾ 5.4W14 or later is required for certain features.

^(2b) Versions before 5.5.1 have known issues with elliptic curve support.

⁽³⁾ Supersedes Gemalto IDGo800 (contains IDPrimePKCS11.dll as optionally installable component in addition to eToken.dll).

⁽⁴⁾ Signature slot support on MD940 requires use of IDPrimePKCS11.dll (optionally installable component) instead of eToken.dll.

⁽⁵⁾ 1.8.3.1 is the minimum compatible version. Nexus recommends 1.8.3.2 or Deutsche Telekom TCOS NetKey 1.12.4.0 / 1.13.5.0.

⁽⁶⁾ Requires Identity Manager 22.10 and above, supersedes T-Systems TCOS3 NetKey. Nexus recommends 1.12.4.0 or 1.13.5.0. DLL names may vary between versions.

⁽⁷⁾ May use different branding (for example "IN Groupe").

⁽⁸⁾ Earlier versions of the client-side middleware have known issues.

⁽⁹⁾ JCOP 4.5 cards with Chipdoc applet versions before 4.1.1 are not supported on some PIN pad readers (e.g. Xiring/Ingenico Leo) due to missing support for chained APDUs in the card firmware.

Yubico Yubikeys

Identity Manager supports certificate enrollment to Yubico YubiKey 5 PIV tokens via Smart ID Desktop App. 

Identity Manager supports enrollment of Fido passkeys on behalf of another user with Microsoft Entra on Yubikey 5 via Smart ID Desktop App.

Fido devices

Identity Manager supports enrollment of Fido passkeys on behalf of another user with Microsoft Entra with all Fido devices supporting CTAP 2.1. Microsoft Entra requires Fido devices to be certified with the Fido alliance.

Virtual smart cards

Virtual smart cards are supported with Smart ID Desktop App.

For more information, see Set up virtual smart card management in Identity Manager. 

Language support

The following languages are supported: 

• English

• French

• German

• Swedish

Additional information

• Card SDK requirements and interoperability

• Identity Manager installation and upgrade

Last updated: October 13, 2026