October 2019

Author: Juan Carlos Cruellas, UPC cruellas@ac.upc.edu


Downloading material

The figure below shows two participants interacting with the portal for downloading the material present in the portal and locally performing the plugtests.

Each participant:

downloads the initial package containing the AdES signatures and ASiC containers already delivered by the participants, and generated by organization team.

Validates those AdES signatures and/or ASiC packages considers worth, and/or generates new AdES signatures and/or ASiC containers.

uploads the new AdES signatures and/or ASiC packages generated, and/or the validation reports.


The figure below shows the structure of the initial package.





As mentioned in the former figure, each folder shall have one IT_ETS sub-folder, enclosing pre-generated signatures. The validation of some of them should result in total-failed; the validation of other should result in indeterminate. See Conducting negative tests page for more details on these pre-generated signatures.

When the plugtest participants extract the contents of the initial package, they will find in their local computers the folders structure represented in the figure above.

The initial package contains the folders ESIG-A, ESIG-C, ESIG-P, and ESIG-X. Their names follow the pattern ESIG-[SignatureTypeOrContainer] where [SignatureTypeOrContainer] stands for the specific type of AdES signature ("C" for CAdES, "P" for PAdES, and "X" for XAdES) or ASiC container (indicated with an "A").

All the ESIG-[SignatureTypeOrContainer] folders have the same inner structure, namely: one sub-folder per each participant. The participants' subfolders names follow the pattern [CC]-[ParticipantID], where [CC] is the two-characters participant's country code, and [ParticipantID] is an identifier assigned to the participant if there are several entities participating in the plugtest for the country identified by CC.

Within each of the aforementioned subfolders, participants will find all the AdES signatures/ASiC containers generated by the owner of the folder. See Generation and cross verification page for details on the files naming strategy.

Once the participants have extracted all the information present in the package in their computers, they may start conducting the plugtest. Typically, participants will go through some or all the steps detailed below:

  1. Validate AdES signatures/ASiC containers present in the downloaded package and upload the corresponding validation reports to the portal.

  2. Generate AdES signatures/ASiC containers for generation and cross-validation test cases, and upload them so that other participants may in turn verify for checking interoperability between tools.

  3. Download and verify AdES signatures/ASiC generated by other participants and upload validation reports to the portal.

Next sections provide details on how this will be accomplished.