Aare Nurm

We have removed the support of B_EPES and LT_TM profile in Digidoc4j version 5.2.0. However the same behavior is still present for B_BES profile. I have modified the heading.

This has been added to backlog for analysis.

> ### Feature request > Add a method to check if a certificate is an e-Seal. We have some questions regarding the purpose of this functionality. What is your use...

In essence it is already possible to determine whether the signature is given by e-seal after validation. getSignatureQualification(); method returns signature qualification object. In case of detection of e-seal, the...

Could you provide us the test file you see the problem with? With the file we are using all seems to be okay.

Sorry for late reply. We are aware of problems in handling + character encoding. The final solution is not yet decided but next version will introduce changes regarding this.

We have released Digidoc4j 5.0.0 where + character is not encoded/decoded as space.

I will close the issue as the 5.0.0 has been released for a year and no additional feedback has been given.

This is still present in SIVA 3.2.0

This is still present in SIVA 3.2.0 although it is claimed to be solved in Digidoc4j.