Java version

From version 5.2, the BankID Java Server is dependent on Java 8 or higher.

Bouncy Castle library version

The Bouncy Castle library dependency have been updated to version 1.56 in version 5.2.

New configuration parameters

New optional parameters for configuring communication timeouts with internal COI components are introduced in version 5.2. If no configuration is provided, the value of the existing parameter commtimeout is used. Commtimeout is in itself optional with a default timeout value of 10 seconds.

Name of property	Example value of property	Description
sdmcommtimeout	5000 (5 seconds)	Communication timeout value for communication with SDM in MILLISECONDS
mobilecommtimeout	5000 (5 seconds)	Communication timeout value for communication with Mobile Gateway in MILLISECONDS
vacommtimeout	5000 (5 seconds)	Communication timeout value for communication with the VA in MILLISECONDS
servicehostcommtimeout	5000 (5 seconds)	Communication timeout value for communication with the Service Host in MILLISECONDS

Google HTTP Client

Google HTTP Client is introduced with version 5.2. It replaces a custom HTTP communication implementation. The new HTTP Client supports different implementations, and the chosen implementation for BankID Java Server is the standard Java HTTP low-level transport based on the java.net package.

The java.net implementation supports persistent connections. Persistent connections properties, and other networking properties, can be configured through system properties.

More information can be found on the following URL’s:

Java 1.6	http://docs.oracle.com/javase/6/docs/technotes/guides/net/properties.html https://docs.oracle.com/javase/6/docs/technotes/guides/net/http-keepalive.html
Java 1.7	http://docs.oracle.com/javase/7/docs/api/java/net/doc-files/net-properties.html http://docs.oracle.com/javase/7/docs/technotes/guides/net/http-keepalive.html
Java 1.8	https://docs.oracle.com/javase/8/docs/api/java/net/doc-files/net-properties.html https://docs.oracle.com/javase/8/docs/technotes/guides/net/http-keepalive.html

Restrictions on SDO creation

If the new CMS (PKCS#7) and OCSP response formats that is introduced in 5.2 was used during signing, it will not be possible to create a SEID SDO, or add signatures to an existing SEID SDO. Trying to do so will lead to an exception being thrown.

Browser not supported