Skip to content
Risto Seene edited this page May 31, 2022 · 3 revisions

The 4.x.x branch

It is recommended to migrate your systems over to DigiDoc4j 5.x.x.

The 3.x.x branch

The 3.x.x branch of DigiDoc4j is intended for legacy systems. It is recommended to migrate your systems over to DigiDoc4j 4.x.x.

Support for 3.x.x has ended by the end of 2020 and no further updates are planned.

Downgraded dependencies (since version 3.3.1)

In order to make DigiDoc4j compatible with Java 7, some of its dependencies have been downgraded or just not updated anymore.

In case of using DigiDoc4j 3.3.1 with Java versions 8 and up, it is advisable to override the versions of some of the DigiDoc4j dependencies in order to get the latest security updates. The most critical is org.apache.santuario:xmlsec, which should be updated to at least version 2.1.4 (CVE-2019-12400).

By default DigiDoc4j 3.3.1 uses BouncyCastle version 1.60 (org.bouncycastle:bcpkix-jdk15on and org.bouncycastle:bcprov-jdk15on). In case of using Java versions greater than 7, it may be a good idea to increase that number (more about which exact version to choose can be read here). For Java 7, using alternative libraries bcpkix-jdk15to18 and bcprov-jdk15to18 may result in being able to use grater versions of Bouncy Castle, if required.

TLS v1.2 on Java 7

Some of the external resources accessed by DigiDoc4j (downloading LOTL and national trust lists, etc...) may require the usage of TLS version 1.2. In order to enable TLS v1.2 for DigiDoc4j 3.3.1 on Java 7, at least JDK 7u131 is required which enables TLS v1.2 by default on the TLS client end-points.