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

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

The following databases are supported:

• SQL Server 2016
• SQL Server 2017
• SQL Server 2019
• Azure SQL
• Oracle Database 12c
• Oracle Database 19c
• PostgreSQL 11
• PostgreSQL 12

• PostgreSQL 14

• PostgreSQL 15

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

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.

The following version of JasperReports is supported:

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

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 "Smartcards and smartcard middleware".
• 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.

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 here for 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 "Smartcards and smartcard middleware".

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

• Tomcat 8/9
• Java 11

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.

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

The databases are the same as under heading Requirements > Databases in Identity Manager requirements and interoperability.

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

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

• Smart ID Certificate Manager, see Smart ID 23.04 - Compatibility for more information.
• Microsoft Active Directory Certificate Services (ADCS) 2012 / 2012 R2 / 2016 / 2019
• D-Trust Managed PKI
• IDNomic version 4.8.1
• EJBCA version 6.15
• DFN Managed PKI
• QuoVadis PKI

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

Other CAs can be integrated on demand.

The following physical access systems (PACS) are supported by Identity Manager:

Set up integrations

For more information, see Integrate Identity Manager with physical access control system (PACS). 

There is also a PACS demo service included in the Physical Access component that can be used to simulate PACS integration. 

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.

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: 

⁽¹⁾ 5.4W14 or later is required for certain features

⁽²⁾ 1.8.3.1 is the minimum compatible version. Nexus recommends 1.8.3.2 or Deutsche Telekom TCOS NetKey 1.10.9.0, 1.12.4.0, or 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

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

Fido2 tokens on Yubikey are not supported. 

The following virtual smartcard is supported:

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

The following languages are supported: 

• English
• French
• German
• Swedish