Skip to main content

1.3.1.1A

Participant onboarding: Certification - Identity and credentials issuance

Test: Prove that the stack uses a credential framework that is compatible with this initiative: Gaia-X

note

The description of Test 1.3.1.1A was extracted from this page in the GitHub repository.
This file was last modified at 2026-06-24 15:37:50 UTC.

Information​

  • Phase 1

  • Minimal? Yes

  • Related KPIs:

    • Functional suitability: [Completeness] The credential framework supports attestations and (multiple?) trust anchors.

  • Evaluation Criteria:

The test assigns a numeric score based on the assessment, using the Functional Suitability metric from iso27001_kpis_subkpis.xlsx.

CriteriaScoring
No Coverage: The solution fails to meet any of the specified technical requirements. This indicates a complete lack of implementation concerning the requirements. The solution does not support using, issuing or validating verifiable credentials.0
Minimal Coverage: The solution meets up to 25% of the technical requirements. The solution has minimal support for verifiable credentials. For example, a credential will be accepted and its signature checked. However, significant gaps exist, such as lack of compatibility with different credential types, no support for SD classes or integration with external trust intermediaries.1
Partial Coverage: The solution satisfies approximately 50% of the technical requirements. The solution supports self-issued credentials with support for SD classes. The solution supports a GAIA-X compatible DID method but without any compliance or claim verification.2
Significant Coverage: The solution covers about 80% of the technical requirements. Most key functionalities are implemented effectively. The solution supports and uses GAIA-X trust anchors. The stack has a service that verifies credential compliance and a connector has policies to ensure a participant has compliant GAIA-X descriptors.3
Full Coverage: The solution fully meets all technical requirements, the stack implements policies that can use SD classes to interpret claims and use a GXDCH clearing house for business purposes.4

Results​

note

The results for Test 1.3.1.1A for Fiware were extracted from this page in the GitHub repository.
This file was last modified at 2026-06-24 15:37:50 UTC.

Environment​

The test is conducted in the IONOS FIWARE_cluster cluster using node pool IP 85.215.161.198.

Tested quality metric and method​

The test quality is based on the metric defined in iso27001_kpis_subkpis.xlsx. For the current phase (phase 1), the test focuses on the Functional Suitability quality metric.

Comparative criteria (checklists, ...)​

Asses that the stack uses a credential framework that is compatible with this initiative: Gaia-X

Expected output​

Compatibility specifications regarding Gaia-X.

Results​

Assessment​

The documentation states in the onboarding steps that the organization validates that the VC containing its description as organization is compliant with Gaia-X specifications using the services of a Gaia-X Digital Clearing House. Therefore it is compatible with Gaia-X framework.

Measured results​

The FIWARE Connector provides partial coverage as it supports self-issued credentials, including GAIA-X compatible DID methods. However, it lacks comprehensive compliance or claim verification capabilities. While it supports key functionalities like ABAC and OPA integration, it does not fully implement policies for interpreting claims using SD classes or leveraging a GXDCH clearing house for business purposes.

Score: 2 (Partial Coverage)

Functional Suitability Quality Metric Score: 2

Notes​

More information about it: https://github.com/FIWARE/data-space-connector