12
9
Page 91
12
Sebastian ElforsAug 9, 2022
According to CEN 419 241-2: "The SAD binds together three elem...
9
Michal TaborJul 11, 2022
Does it cover 2 scenarios with wallet? 1. Walet holds attribut...
Page 66
11
Sebastian ElforsAug 3, 2022
This section could be rephrased to more clearly distinguish th...
Page 58
10
Michal TaborJul 26, 2022
hashes
Page 22
8
Michal TaborJul 11, 2022
Note that this method may be used as part of Wallet authentica...
Page 6
6
Michal TaborJul 11, 2022
Current works on the EU Digital Wallet and more common SSI mod...
Page 40
5
François ChungApr 26, 2022
What is the new version? Isn't the 2.0 already? Or a version a...
Page 16
4
François ChungApr 25, 2022
application
Page 15
3
François ChungApr 25, 2022
Union
Page 54
2
evrenApr 7, 2022
Default value of credentialInfo is false and request body has ...
Page 28
1
Kostas JakeliunasApr 6, 2022
It appears that CSC v2 still expects hashes to be supplied via...
11 of 11
12
Sebastian ElforsAug 9, 2022According to CEN 419 241-2: "The SAD binds together three elements: signer authentication with the signing key and the data to be signed (DTBS/R(s))."
In this specification, the SAD is only the Oauth2 access token, so the CredentialID (signing key id) and the hash of DTBS are sent separately to the RSSP.
A potential enhancement to CSC API v2.x could be to use OIDC instead of Oauth2, which allows for id tokens with custom claims. Then the SAD could be a signed OIDC id token that combines the signer authentication, CredentialID (signing key id) and the hash of DTBS.
Status
This canvas is inactive and currently has commenting disabled.