1. Introduction
1.1 Gaia-X Technical Workshop for Compliance on Tagus and Loire¶
In this repository, you may a find quick overview and step-by-step guide to get the Gaia-X Compliance on Loire and Tagus versions. This will also allow to fulfill all the required steps to complete the Technical Advisor Certificate on the Gaia-X Academy.
This workshop includes very basic explanations on the prerequisite concepts such as Decentralized Identity or Verifiable Credentials, a more in depth look into these subjects is very recommended. Several tools (local or online) are required to complete all the steps, however other methods are available and custom method are possible as everything is based on open standards.
Disclaimer: The steps explained here, are for educational and testing purposes only, we highly
recommend to follow proper procedures and considerations for any production use.
1.2 Practical work: Get your own keypair, x509 certificate & create your own DID¶
The first guide of the Gaia-X journey starts with either creating (locally), delegating to third party or requesting from a Trust Service Provider, cryptographic material, certificates and Decentralized Identifiers to start issuing verifiable credentials.
This guide is dedicated to only preparing these prerequisites locally, as this is for educational purposes only, a proper use of these resources is highly recommended for any production use, such as wallet use, secure authentication and storage and requesting a certificate from a trusted certificate authority.
1.3 Practical work: Tagus Compliance¶
In this guide we will mainly focus on how to use the cryptographic material and did to sign a Verifiable Credential.
Using a JWS2020 signature and fulfilling the requirements for minimum compliance on the Tagus release.
Several tools (online and offline) are available, in this guide we will use the Gaia-X wizard, a UI tools that provides
step-by-step guide and forms to create and sign Verifiable Credential from the Gaia-X ontology.
Other tools are also available, but won’t be covered in this guide.
1.4 Practical work: Loire Compliance¶
In this last part, the goal will remain the same as last time, only this time for the Loire or v2 Compliance.
There are many changes between Loire and Tagus, we will focus mainly on the signature format VC-JWT, the new ontology,
and the requirements in the new 24.11 Compliance Document. Again, there are multiple ways of going through this, but we will
try this time to use the Credential Helper, a tool compatible with any ontology, to take an example or create a new object.
Then we will install a signer tool to sign our Verifiable Credential into VC-JWT format.