Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CompleteCertificateRefsV2 is not correctly supported #6

Open
bsanchezb opened this issue Feb 24, 2021 · 3 comments
Open

CompleteCertificateRefsV2 is not correctly supported #6

bsanchezb opened this issue Feb 24, 2021 · 3 comments

Comments

@bsanchezb
Copy link

bsanchezb commented Feb 24, 2021

Hello,

According to the EN 319 132-1 and the schema, the element CompleteCertificateRefsV2 shall contain the element CertRefs inside:

<xsd:element name="CompleteCertificateRefsV2" type="CompleteCertificateRefsTypeV2"/>
<xsd:complexType name="CompleteCertificateRefsTypeV2">
    <xsd:sequence>
        <xsd:element name="CertRefs" type="xades:CertIDListV2Type"/>
    </xsd:sequence>
    <xsd:attribute name="Id" type="xsd:ID" use="optional"/>
</xsd:complexType> 

However, when I validate a file with the elements, the XAdES Conformance Checked reports me the error:

Location-{CodeTest}:UnsignedSignatureProperties/CompleteCertificateRefsV2[2]-{CheckSchemaForChildren}
--
Children order and number DO NOT MATCH specification 
Specification: xadesv132:Cert+
Elements found: xadesv141:CertRefs
Error indication (^ appears at the end of the last correct child): ^xadesv141:CertRefs

It seems like the element 'xadesv141:CertRefs' is skipped in the checker. Could you check it, please?

The test file is in the attachment (archived, because GitHub does not support XML attachments).

Best regards,
Aleksandr.


Edited: updated the attachment

sample-signed-xades-x.zip

@jccruellas
Copy link
Collaborator

Dear Alexander,
Sorry for the delay in reacting. I have experienced problems during some time as the notifications did not arrive to may email and also heavy work in the university.
Indeed the behaviour is not correct. I will check and modify XAdESCC accordingly

I will keep you posted
Best regards
Juan Carlos.

@jccruellas
Copy link
Collaborator

Hi again Alexander,
I have fixed this issue in my local copy of XAdESCC.
I attach a screenshot of my screen where you will be able to see that this version now works fine
20210414_XAdESCCScreenShot

@jccruellas
Copy link
Collaborator

I plan to update the deployed XAdESCC at the ETSI portal during this week
Regards
Juan Carlos.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants