- Created by Ann Base, last modified on Jul 07, 2020
This article includes any limitations for the different releases of Smart ID Identity Manager.
Limitations for PRIME 3.12.4
Release date: 2020-06-17
Release note: Release note Nexus PRIME 3.12.4
Server-side card operations and self-service card encoding processes can fail
Server-side card operations and self-service card encoding processes can fail with a null-pointer exception in the PRIME log, especially on a fresh installation.
You must remove the bean definition that you add in this workaround once you upgrade to a PRIME version that includes a correction.
Add the following bean definition to WEB-INF\classes\spring\custom-beans.xml of PRIME Explorer.
Add this bean definition Expand source<bean id="tunnelServerContext" class="de.vps.act.frontend.admin.systemproperty.ContextVO" scope="prototype"> <property name="contextVOName" value="tunnelServerContext"></property> <property name="name" value="serverContext"></property> <property name="propertyVOs"> <list> <bean name="primeUriProperty" class="de.vps.act.frontend.admin.systemproperty.PropertyVO" scope="prototype"> <property name="name" value="primeUri" /> <property name="text" value="property.prime.server.url" /> <property name="formatMask" value="#" /> <property name="type"><util:constant static-field="de.vps.act.kernel.datatype.DataType.STRING" /></property> <property name="defaultValue" value="http://localhost:8080/prime_explorer"></property> </bean> </list> </property> </bean> <bean id="systemPropertyBuilder" class="de.vps.act.frontend.admin.systemproperty.SystemPropertyBuilder" scope="prototype"> <property name="systemProperties"> <list> <ref bean="smtpContext" /> <ref bean="licenseContext" /> <ref bean="hagXPIContext"/> <ref bean="coreTemplateContext" /> <ref bean="mdmContext" /> <ref bean="processTimeoutContext" /> <ref bean="hideOpenTasksContext" /> <ref bean="tunnelServerContext" /> </list> </property> </bean>- Restart Tomcat
- Log in to PRIME Explorer as admin user.
- Select the Admin tab.
- Select Configure system properties.
- Select serverContext.
- Enter the correct URL of PRIME Explorer.
- Click Save.
Limitations for PRIME 3.12
Release date: 2020-04-15
Release note: Release note Nexus PRIME 3.12
No known limitations so far.
Limitations for PRIME 3.11
Release date: 2019-11-07
Release note: Release note Nexus PRIME 3.11
No known limitations so far.
Limitations for PRIME 3.10
Release date: 2019-05-24
Release note: Release note Nexus PRIME 3.10
No known limitations so far.
Limitations for PRIME 3.9
Release date: 2018-12-14
Release note: Release note Nexus PRIME 3.9
db_update requires Java 8
From PRIME 3.9, Java 11 is supported on the server side, meaning that Java 11 can be used when installing PRIME. However, the tool for initializing the database, called db_update based on liquibase, does not support Java 11.
To solve this, do any of the following:
- Before you install Tomcat and PRIME, install Java 8 and run db_update
or
- Run db_update from another computer with Java 8 and access to the database
or
- Run Java 8 only
Card SDK requires Java 8
Card SDK for PKI encoding does not support Java 11. Clients used for PKI encoding via Card SDK must run on Java 8.