You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Walt-ID seems to be not sync with Gaia-X GXDCH
I was trying happily Walt.ID CLI tools again and noticed that there is maybe could be a chance that Walt-ID is able to generate VC SD JWT for me which are accepted (compliant) by the Gaia-X GXDCH.
First of all - the converting feature of the CLI is pretty handy and useful. thanks for that. We could e.g. convert a private key in PEM format into jwk format.
The process of sign and all works fine seems - so far so good. but the compliance apis does not accept it because they expect header have more informations like issuer. the example payload have headers of the form
{
"alg": "ES256",
"typ": "vc+ld+json+jwt",
"cty": "vc+ld+json",
"iss": "did:web:gaia-x.unicorn-home.com",
"kid": "did:web:gaia-x.unicorn-home.com#X509-JWK2020"
}
So there are several questions related to the relationship between Gaia-X, Aster-X and Walt-ID :
is there a sync between Gaia-x / aster-X and Walt-ID? since i know for Demos Walt-ID is their prefered solution in past
if there is no sync : do you care Gaia-X compliance in general? I mean at least it's at least a EU try to shape the future of identity so ....
is it possible to add fields in the header of jwt or is the header truly fixed? i saw that the issuer is written in the payload of the Walt-ID jwt
will the Rest-APIs and SDKs result in the same format of jwt?
Thanks for your time and great work until now but i am wondering if there will be some cooperation with Gaia-x ...
The text was updated successfully, but these errors were encountered:
Currently Walt-ID seems to be not sync with Gaia-X GXDCH
I was trying happily Walt.ID CLI tools again and noticed that there is maybe could be a chance that Walt-ID is able to generate VC SD JWT for me which are accepted (compliant) by the Gaia-X GXDCH.
First of all - the converting feature of the CLI is pretty handy and useful. thanks for that. We could e.g. convert a private key in PEM format into jwk format.
next we wanted to take the payload of example from https://compliance.lab.gaia-x.eu/development/docs/#/conformity/CredentialOfferController_verifyBasicConformityLevel (if convert jwt into human readable form - be careful the " at end and begin does not belong to the jwt) and then sign it with Walt-ID CLI.
The process of sign and all works fine seems - so far so good. but the compliance apis does not accept it because they expect header have more informations like issuer. the example payload have headers of the form
{
"alg": "ES256",
"typ": "vc+ld+json+jwt",
"cty": "vc+ld+json",
"iss": "did:web:gaia-x.unicorn-home.com",
"kid": "did:web:gaia-x.unicorn-home.com#X509-JWK2020"
}
So there are several questions related to the relationship between Gaia-X, Aster-X and Walt-ID :
Thanks for your time and great work until now but i am wondering if there will be some cooperation with Gaia-x ...
The text was updated successfully, but these errors were encountered: