Table of contents

  1. Introduction

  2. Types of tests

  3. Versions of XAdES tested

  4. Before starting the Plugtests

  5. Conducting generation and cross-verification tests

  6. Conducting augmentation and arbitration tests

  7. Conducting only-verification tests

1. Introduction

This page provides generic information on the Plugtests, namely: the types of interoperability tests that the participants will be able to conduct, and a high-level description of how they may conduct tests using the XAdES Plugtests portal.

2. Types of tests

This Plugtests event allows to conduct three types of tests:

1. Generation and cross-verification (a.k.a. Positive) tests.
   Each participant is invited to generate a certain set of valid XAdES signatures with certain characteristics (generation). The rest of participants are invited afterwards to verify these signatures (cross-verification). The Plugtests portal automatically generates an updated set of interoperability matrixes that all the participants may access.
2. Signatures augmentation and arbitration (a.k.a. Positive) tests.
   In this type of tests ETSI will provide a restricted set of valid XAdES signatures of different levels. A certain participant A (acting as verifier/archival system) will verify the aforementioned signature and will augment ate it to a higher level. Finally, another participant B (acting now as if she was an arbitrator) will take the augmented signature and will verify it as an arbitrator would do.

3. Only-verification (a.k.a. Negative) tests.
   ETSI has generated a number of invalid XAdES signatures (the so-called "negative testcases") by different reasons. Each participant may, at her own discretion, try to verify these signatures, checking in this way that the corresponding tool actually detects that the signature is not valid.
4. Conformance checking.
   

   At the start of the Plugtests event, the XAdES Conformance Checker:

   1. Will conduct a complete set of tests for checking conformance against ETSI TS 103 171v.2.2.1 (XAdES Baseline Profile)
   2. Will conduct a complete set of tests for checking conformance against ETSI TS 101 903v1.4.2 (XAdES core specification)

It is the intention of the organizers to also incorporate to the XAdES Conformance Checker:

1. partial tests for checking conformance against ETSI pre EN 319 132-1 v1.0.0 (XAdES baseline signatures -correspond to former XAdES Baseline Profile).
2. partial tests for checking conformance against ETSI pre EN 319 132-2 v1.0.0 (XAdES extended signatures -correspond to former XAdES core).

Participants will be reported on the progress of these features during the event.

3. Versions of XAdES tested

Below follows the XAdES related specifications that will be addressed:

1. ETSI pre EN 319 132 v1.0.0. The test suite defined in Test Cases includes test cases for:
   1. Part 1. XAdES Baseline signatures XAdES-B-B, XAdES-B-T, XAdES-B-LT, and XAdES-B-LTA levels.
   2. Part 2. XAdES Extended signatures XAdES-E-BES, XAdES-E-C, XAdES-E-X, XAdES-E-XL, and XAdES-E-A.
2. XAdES ETSI TS 103 171v2.2.1. The test suite defined in Test Cases includes test cases for the four conformance levels, identified within this document as XAdES-B conformance level, XAdES-T conformance level, XAdES-LT conformance level, and XAdES-LTA conformance level.
3. XAdES ETSI TS 101 903v1.4.2. The test suite defined in Test Cases includes test cases for XAdES-BES, XAdES-C, XAdES-X, XAdES-XL, and XAdES-A.

Conceptually speaking, this event is going to use two test suites (you can find them in Test Cases). They aim at providing a good coverage of the different XAdES specifications existing today:

1. The pair formed by the existing ETSI TSs, namely ETSI TS 101 903v1.42, ETSI TS 103 731v2.1.1. The test cases defined in this test suite lead to XAdES signatures that, in most of the cases, are compliant at the same time with both ETSI TS 101 903v1.42, ETSI TS 103 731v2.1.1.
2. The new ETSI pre EN 319 132 v1.0.0 parts 1 and 2. The test cases defined in this test suite lead to XAdES signatures that, in most of the cases, are compliant at the same time with both ETSI TS 101 903v1.42, ETSI pre EN 319 132-1 v1.0.0 and ETSI pre EN 319 132-2 v1.0.0.

4. Before starting the Plugtests

Before starting the Plugtests, the participants should:

1. Request a certificate (and optionally the generation of the key pair) to the Certification Authority server.
2. Read the documentation present in the portal describing the environment, namely:
1. This page, and the 5 additional pages providing detailed information on how to conduct the interoperability tests, namely:
   1. Conducting Plugtests: Interactions with portal, which provides a high level view of how the participants may interact with the portal depending on the type of tests they are conducting.
   2. Conducting Plugtests: Downloading material, which provides information on how to proceed to download the initial package and the successively updated download package, as well as details of its inner structure, and how this relates to the tests conducted.
   3. Conducting Plugtests: Generation & cross-verif.,which provides details on how to conduct the generation and cross-verification test cases.
   4. Conducting Plugtests: Only verification,which provides details on how to conduct the only-verification test cases

2. The pages on trust framework and cryptographic material.
3. The page providing details on how to use the On-line PKI-related services offered by the portal.

5. Conducting generation and cross-verification tests

Participants are kindly requested to read Conducting Plugtests: Generation & cross-verif. page, which provides all the required details on how to conduct the generation and cross-verification test cases.

6. Conducting augmentation and arbitration tests

Participants are kindly requested to read Conducting Plugtests: augmentation & arbitration,which provides details on how to conduct the augmentation and arbitration test cases.

7. Conducting only-verification tests

Participants are kindly requested to read Conducting Plugtests: Only verification,which provides details on how to conduct the only-verification test cases.