DigiDoc4j is a Java library for digitally signing documents and creating digital signature containers of signed documents.
- Creating BDOC, ASiC-E and DDOC containers
- Digitally signing containers in XAdES format
- Validating BDOC, ASiC-E and DDOC containers
How to use it
- Take a look at the examples
- See the full DigiDoc4j API description
- Explore the Wiki section
- Download the latest release
- See the library development guide. Your contribution and pull requests are more than welcome
BDOC (ASiC-E) container format
- Has .bdoc or .asice extension
- BDOC is a new digital signature format developed in 2014 to replace the old, DDOC (DigiDoc) digital signature format.
- The benefits of the new format include the higher security level, the long-term integrity of the signed documents, as well as the better compliance with international standards.
- BDOC container is based on ASiC-E standard.
- Signatures are stored in XAdES format.
- Supports two signature formats: BDOC-TM and BDOC-TS
- BDOC-TM signature format has time-mark ensuring long-term provability of the authenticity of the signature.
- This format has been used as a default digital signature format in Estonia since 2015.
- It is based on XAdES baseline LT signature format.
- Recommended extension is .bdoc
- BDOC-TS signature format has time-stamp.
- In contrast to the BDOC-TM format, long-term provability of the authenticity of the signature is ensured by time-stamps.
- It is based on XAdES baseline LT signature format and uses RFC3161 based time-stamps which makes it highly compliant in international context.
- To ensure better compliance with international standards, it's recommended to sign documents with the BDOC-TS time-stamp signature profile.
- Recommended extension is .asice
- .bdoc or .asice file is in fact a ZIP container with the signed files, the signatures and the protocol control information and can basically be opened by any program that recognizes the ZIP format.
DDOC container format
- Has .ddoc extension
- An old DigiDoc digital signature format
- Since year 2015 it's recommended not to sign documents in the DDOC format
- It is based on XML Advanced Electronic Signatures (XAdES) format, corresponding to profile XAdES-X-L
- The DigiDoc container includes the source files (the files that were signed) as well as the signatures that are related to the signed file(s)
- Every signature contains the certificate, validity confirmation and the validity confirmation service certificate.
- DigiDoc4j API
- Pivotal Tracker contains user stories and issues
- Architecture of ID-software
- Digital signature formats
- BDOC 2.1.2 specification
- DDOC specification
- Java 1.7
- Internet access to external verification services
- OCSP (Online Certificate Status Protocol) - http://ocsp.sk.ee
- EU TSL (European Commission's Trusted Status List) - https://ec.europa.eu/information_society/policy/esignature/trusted-list/tl-mp.xml
- All the EU member states' TL servers referred in the EU TSL. Note that this list may change. (e.g. https://sr.riik.ee/tsl/estonian-tsl.xml, https://sede.minetur.gob.es/Prestadores/TSL/TSL.xml, https://www.viestintavirasto.fi/attachments/TSL-Ficora.xml etc.)
- TSA (Time Stamping Authority) - http://tsa.sk.ee
You can use the library as a Maven dependency from the Maven Central (http://mvnrepository.com/artifact/org.digidoc4j/digidoc4j)
<dependency> <groupId>org.digidoc4j</groupId> <artifactId>digidoc4j</artifactId> <version>1.x.x</version> </dependency>
The list of user stories and issues are tracked in Pivotal Tracker
- LGPL (GNU Library General Public License, see LICENSE.LGPL)
- © Estonian Information System Authority
Source code is provided on "as is" terms with no warranty (see license for more information). Do not file Github issues with generic support requests.