jccruellas
commented
2 years ago Good afternoon, I have taken a look to the JAdESCC, and indeed the results that you have pointed out were not correct.
- The CC understood that the desc member was empty when it actually was not present.
- The CC tried to base64 decode the digVal member, when it should base64url decode it according to our agreement in the slack. As I said, both issues are now fixed in my local copy. I will between today and tomorrow take a look to the other two pending issues. If I consider that they are not difficult to solve, I will try to fix them and upload a new version with the three issues solved. If not, I will upload a new version fixing just this one
Regards and thanks for using the JAdESCC Juan Carlos
I have a problem checking the signature for the JAdES Plugtests Test Scenario JAdES-B-B.SCOK/Signature-J-B-B-13.json. Two things yield an incorrect message. First of all, as discussed in our slack forum, the encoding of the digVal member shall be in Base64Url Encoding. Nevertheless, if I upload a signature where the digVal member is Base64Url encoded, I get one of the attached errors. If I encode it with "standard" Base64, it succeeds.
Also, for both signatures that participants created at the time of writing, the CC yields an error saying, "The component should have a non-empty content. The 'desc' member is present, but its value is empty", but for both signatures, the desc member in the OID object is not present Attached are the signatures and a screenshot of the error message
error.zip .