IDM (PRIME) 3.10 - Requirements and interoperability

This article provides installation requirements and interoperability data for PRIME. 

Requirements

PRIME application server

Hardware

	Minimum	Recommended
Hard disk storage	5 GB The application generates log files, which consumes additional hard disk space.
CPU	2 GHz	> 2 GHz
RAM	8 GB	16 GB

The sizing requirements listed above are only recommendations for a default setup. The sizing may differ, for example depending on the following things:

• Number of concurrent users in the PRIME applications.

• System architecture: for example high availability setup, combined or distributed setup of the PRIME applications.

• OS footprint: different operating systems consume different RAM/CPU loads.

It is recommended to host the application server and the database server in the same data center (but on separated servers). Connecting a PRIME application server to a database server via a WAN connection would mean higher latencies and would affect the performance of the system.

Operating systems

The following operating systems are supported:

• Windows 10 (Client OS not recommended for production environment) 

• Windows Server 2012

• Windows Server 2012 R2

• Windows Server 2016

• Windows Server 2019

• Linux and others on request

Software

The following software is supported:

• Oracle Java JDK/JRE:

  • Version 8.0 (32-bit and 64-bit) , Update 191 or higher

• OpenJDK

  • Version 11 (64-bit), Tested on OpenJDK 11.0.1

• Application Server:

  • Apache Tomcat 8.5 and 9.0

  • IBM Websphere 8.5.5.11 (we expect Websphere expertise at the customer, Nexus does not offer integration services for deployment Websphere)

Required ports for Tomcat

On the Apache Tomcat at least two ports are required, one for HTTP and one for HTTPS. Tomcat default ports are 8080 (HTTP) and 8443 (HTTPS). To avoid port collisions, the PRIME distribution package is preconfigured with 18080/18443. The port numbers can be configured in the configuration file server.xml. Technically, it is not necessary to use HTTPS, but it is highly recommended.

PRIME database server

Hardware

It is recommended to host the application server and the database server in the same data center (but on separated servers). Connecting a PRIME application server to a database server via a WAN connection would mean higher latencies and would affect the performance of the system.

Databases

The following databases are supported:

• SQL Server 2012 and 2012 R2

• SQL Server 2014 and 2014 R2

• SQL Server 2016

• SQL Server 2017

• SQL Server 2019

• Azure SQL

• Oracle Database 11g

• Oracle Database 12c

• PostgreSQL 9.2 – 9.6

• IBM DB2 10.5

Operating systems

All operating systems that can host the above databases are supported.

PRIME client workstation

Web browsers

All PRIME applications (Designer, Explorer, Tenant and Self-Service) are executed in up-to-date HTML5 web browsers such as:

• Mozilla Firefox

• Google Chrome

• Internet Explorer 11

• Safari

• Microsoft Edge (Edge HTML engine)

PRIME releases are always tested with the latest browser versions.

Hardware

Operating systems

The following operating systems are supported:

• Windows 10

• Linux (for clients without image capture, printing and encoding)
  

Mobile device platforms

Platforms of mobile devices, for example iOS, Android, and Windows RT, are only supported by certain functions of the browser-based Nexus PRIME Self-Service, but cannot be used with Nexus PRIME Designer and Nexus PRIME Explorer.

JasperReports

The following version of JasperReports is supported:

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

Capture or production client: Software

If a workstation is used as a capture client or production client, the Nexus Card SDK application must be installed and licensed.

This requires a Windows-based workstation (PC). For complete installation requirements for Card SDK, see the Nexus Card SDK documentation.

The following version is required:

• Nexus Card SDK Version >= 5.4.0.22 

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

• Oracle Java JDK/JRE or OpenJDK

  • Version: 8 or 11, Tested on JRE 8 Update 191 and OpenJDK 11.0.2

  • 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 PRIME Explorer's encoding component connectors from the client-side Java to the middleware.

Identity Manager Self-Service client: PKI cryptochip encoding

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

• A PKCS#11 compliant smart card middleware.

  • For a list of supported smartcard middleware, see Smartcards and smartcard middleware.

• Smart ID Desktop App version 1.2.

Interoperability

Data connectors

PRIME 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

PRIME 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

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

The following databases are supported:

• QL Server 2012 and 2012 R2

• SQL Server 2014 and 2014 R2

• SQL Server 2016

• SQL Server 2017

• SQL Server 2019

• Azure SQL

• Oracle Database 11g

• Oracle Database 12c

• PostgreSQL 9.2 – 9.6

• IBM DB2 10.5

• H2

Certificate authorities

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

• Smart ID Certificate Manager 7.18.

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

• D-Trust Managed PKI

• IDNomic version 4.8.1

• EJBCA Version 6.3 (without Key Backup / Key Recovery) 

• DFN Managed PKI

• QuoVadis PKI

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

Other CAs can be integrated on demand.

Physical access control systems (PACS)

These are the different levels of PACS integration in PRIME:

Basic PACS integration

• Integration via standard data connectors, such as CSV files, JDBC, LDAP, and SCIM

• Export of card data to PACS at card activation and deactivation

All PACS systems that can use any of the standard data connectors are supported.

Full entitlement PACS integration

Full entitlement PACS integration is included as part of the Physical Entitlement Management module in PRIME:

• Integration via standard connectors in PACS backend

• Online sync of card data and access profiles

• Virtual access profile groups on top of PACS access profiles

• Updates of access profiles can be separated from card issuing

The following PACS systems are supported:

For some PACS systems you need an additional license to do this integration. Contact your PACS vendor for more information.

Set up integrations

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

Missing your PACS system on the list?

Provide the details of your PACS system in this form and we will contact you.

Mobile device management (MDM)

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

• MobileIron 9.1

Other MDM systems can be integrated on demand.

Digital identities

Smart cards and middleware

Supported smart cards depend on the smart card middleware. Smart card middleware is not part of the Nexus PRIME product.

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

CardOS 4.4 and CardOS 5.0 are our 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.2.2 is the minimum compatible version, we recommend 1.8.2.4 or later

Virtual smartcards

The following virtual smartcard is supported:

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