Closed bsanchezb closed 2 years ago
Hm, maybe the problem is not related to all custom 'CommitmentTypeQualifier's, but it is the content of this particular CommitmentTypeQualifier that causes the issue. But still the problem persist.
Good afternoon, I will take a look asap and will come to you. Regards Juan Carlos
Good afternoon,
I think that I have found the reason for the failure and fixed It.
Actually it was a failure in the process of registering the nodes with attribute 'Id' or 'ID' or 'id' which are defined in a non-XML namespace. In particular, it was the element
I will deploy this version of XAdESCC hopefully this afternoon. Regards and thanks for reporting this issue sample-signed-xades-baseline-b.zip
Juan Carlos.
Hi again, I have deployed XAdESCC version 1.4 which, as far as I am aware, fixes the problems that you experienced with the signature that you passed to me.
Could you please confirm whether I can close this issue? Regards
Hello Juan Carlos,
It seems to be working perfectly now!
Thank you for the quick resolution. I will close the issue.
KR, Aleksandr.
Dear @jccruellas ,
According to the specification, CommitmentTypeQualifier element is a type of AnyType, therefore it may contain text information or an embedded XML:
However, while XAdESCC is able to verify a signature containing a text type CommitmentTypeQualifier, it fails to verify a signature with XML content enveloped into CommitmentTypeQualifier element.
The returned error is NOT_FOUND_ERR.
Could you please take a look on the issue? The sample document is in the attachment.
Best regards, Aleksandr.
sample.zip