Skip to main content

1.3.1.1C

Participant onboarding: Certification - Identity and credentials issuance

Test: Prove that the stack uses a credential framework that is compatible with this initiative: EBSI

note

The description of Test 1.3.1.1C 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? No

  • Related KPIs:

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

  • Evaluation Criteria:

N/A

Results​

note

The results for Test 1.3.1.1C 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: EBSI

Expected output​

Compatibility specifications regarding EBSI.

Results​

Assessment​

The FIWARE documentation assess that the connector can effectively interface with trust services aligned with EBSI specifications by integrating decentralized identifiers, verifiable credentials, and EBSI-compliant trust services.

Measured results​

The criteria used to measure the results was the one specified by the Data Product Publication ISO25010 Quality file regarding Functional Suitability.

CriterionDescriptionScore (0-4)Explanation
Functional CompletenessTechnical requirements cover all the specified tasks and user objectives.4The Fiware connector fully supports all necessary functions for identity and credential issuance, ensuring compatibility with EBSI standards, including decentralized identifiers and verifiable credentials. This ensures the platform can handle all tasks required by EBSI.
Functional CorrectnessTechnical requirements meet results with the needed degree of precision.4The implementation of EBSI-compatible services is precise and reliable, correctly issuing credentials and managing identities as per the specifications. The integration is robust, with accurate handling of the trust services.
Functional AppropriatenessTechnical requirements facilitate the accomplishment of specified tasks and objectives.4The platform’s design and functionality are well-suited to the requirements of EBSI, enabling efficient and effective credential issuance and identity management. It supports the necessary processes without unnecessary complexity, facilitating smooth operations.

Overall calculation: (4 + 4 + 4)/3 = 4

Functional Suitability Quality Metric Score: 4

Notes​

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