-
Notifications
You must be signed in to change notification settings - Fork 1
/
issuerResolution.html
586 lines (535 loc) · 20 KB
/
issuerResolution.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove" defer></script>
<script src="./common.js"></script>
<script class="remove">
// All config options at https://respec.org/docs/
var respecConfig = {
specStatus: "unofficial",
editors: [
{
name: "José San Juan",
mailto: "[email protected]"
},
],
github: "decentralized-identity/vui",
shortName: "vui-issuer-resolution",
xref: "web-platform",
group: "Verifier Universal Interfaces",
localBiblio: ccg.localBiblio,
logos: [
{
src: "https://cdn2.hubspot.net/hubfs/4728390/GATACA_ISOTYPE_GRADIENT.png",
url: "https://gataca.io",
alt: "GATACA",
width: 100,
height: 100,
id: "gataca-logo",
},
],
};
</script>
<style>
.oplist {
list-style-type: none;
margin: 0;
padding: 0;
}
.oplist:first-of-type {
counter-reset: item;
}
.start2 {
counter-set: item 1;
}
.start4 {
counter-set: item 3;
}
.oplist>li {
display: table;
counter-increment: item;
margin-bottom: 0.6em;
}
.oplist>li:before {
content: counters(item, ".") ". ";
display: table-cell;
padding-right: 0.6em;
}
li .oplist>li {
margin: 0;
}
li .oplist>li:before {
content: counters(item, ".") " ";
}
table {
border-collapse: collapse;
border-width: 1px;
}
table td,
table th {
border: 1px solid #ddd;
padding: 8px;
}
table tr:nth-child(even) {
background-color: #f2f2f2;
}
table tr:hover {
background-color: #ddd;
}
</style>
</head>
<body>
<h1 id="title">Issuer Resolution</h1>
<h2 id="subtitle">Definition of the standards under the <a>Verifier Universal Interface</a> protocol, to define a
common format for any governance platform possessing a trusted issuers registry.
</h2>
<section id="abstract">
<p>
One of the major challenges on the Decentralized Identity model is how to trust the issuers of credentials, and
how to make sure that all legal requirements regarding the identity validation have been correctly
fulfilled.
</p>
<p>
In the Decentralized Identity world, multiple "governance" platforms differentiated by
technology, geographical, economical or legal frameworks will coexist.
</p>
<p>
If we wish to ensure interoperability between technology providers, and more precisely verifiers, it is
necessary to establish a common standard interface that is agnostic of the governance platform to allow external
actors to retrieve a list of trusted issuers for a specific credential.
</p>
<dd>
This document proposes a generic Data Model and API, agnostic of any current framework, to expose a trusted
issuers registry to any external actor.
</dd>
<p class="ednote">
Despite its format, this document doesn't aim to be published on the W3C as a standard normative, rather it aims to
offer a new protocol that is applicable to known SSI governance frameworks.
</p>
</section>
<section id="sotd">
<p> </p>
</section>
<section data-dfn-for="Context">
<h1>Context</h1>
<p>
Many technology providers have offered different solutions to solve the problem of "who should be trusted as
an issuer". Some known solutions could be hardcoded lists in configuration files, API services, Domain name
consultations, or Blockchain/DLT registries.
</p>
<p>
In the SSI world however, it's the Verifier who must have the final decision on who he can trust. That
means that a verifier should be allowed to query different governance platforms to retrieve their issuers
and assign different levels of trust to each one of them. The verifier could even have a private registry of
issuers that is not publicly available.
</p>
<p>
Only in the context of the Essiflab project, there are multiple solutions trying to offer partial solutions
to this problem:
<ul>
<li>
<a href="https://essif-lab.eu/essif-train-by-fraunhofer-gesellschaft/">Fraunhofer SIT: TRAIN</a>
</li>
<li>
<a href="https://github.com/UBICUA-JSSI/ssiddi/">UBICUA: Self-Sovereign Identity Description, Discovery
and Interoperability</a>
</li>
<li>
<a href="https://github.com/tno-ssi-lab/credential-catalog">TNO: Credential Catalog</a>
</li>
</ul>
</p>
<p>
In the context of EBSI Essif, a trusted issuer registry has been designed with a complex governance protocol
to determine who can issue which credentials and who can vouch for those issuers. A generic, agnostic
approach to that kind of behaviour, portable to any governance platform, could be the solution
required by verifiers.
</p>
<p>
This document will try to offer a generic adaptation compatible with EBSI Essif trusted registries that
can be a solution for any governance framework.
The verifier will only need to build a generic query interface, similar to the Universal DID Resolver, to
retrieve the issuers from any platform, and manage them as he pleases.
</p>
<section id="conformance">
</section>
<section id="terminology">
<h2>Terminology</h2>
<dl>
<dt><dfn data-lt="DID|<a>DIDs</a>|decentralized identifiers">Decentralized Identifier</dfn>
(DID)</dt>
<dd>As defined in [[DID-CORE]].</dd>
<dt><dfn data-lt="">DID document</dfn></dt>
<dd>As defined in [[DID-CORE]].</dd>
<dt><dfn data-lt="">DID resolution</dt>
<dd>As defined in [[DID-RESOLUTION]].</dd>
<dt><dfn data-lt="DID resolver's">DID resolver</dt>
<dd>As defined in [[DID-RESOLUTION]].</dd>
<dt><dfn data-lt="VC|Verifiable Credential">Verifiable Credential</dfn> (VC)</dt>
<dd>As defined in [[VC-DATA-MODEL]].</dd>
<dt><dfn data-lt="VP|Verifiable Presentation">Verifiable Presentation</dfn> (VP)</dt>
<dd>As defined in [[VC-DATA-MODEL]].</dd>
<dt><dfn data-lt="LD PROOFS|Proofs|Linked Data Proofs">Linked Data Proofs</dfn></dt>
<dd>As defined in [[LD-PROOFS]].</dd>
<dt><dfn data-lt="JSON-LD">JSON-LD</dfn></dt>
<dd>As defined in [[JSON-LD]]</dd>
<dt><dfn data-lt="VUI|Verifier Universal Interface">Verifier Universal Interface</dfn>(VUI)</dt>
<dd>As defined in [[VUI]]</dd>
</dl>
</section>
</section>
<section data-dfn-for="Data Model">
<h1>Data Model</h1>
<p>
The data model marks the representation of a Trusted Issuer
</p>
<p>
A Trusted Issuer is a signed document that presentsa credential issuer's information along with the
accreditations backing the identity validation process performed.
</p>
<h3>Properties</h3>
<dl>
<dt>
Id
</dt>
<dd>
Unique id to reference this issuer in the governance platform
</dd>
<dt>
Dids
</dt>
<dd>
List of DIDs that can be used from this organization to issue credentials
</dd>
<dt>
Domain
</dt>
<dd>
Economic/industry domain to which this organization belongs
</dd>
<dt>
Service Endpoints
</dt>
<dd>
OPTIONAL Description of the multiple service endpoints that the organization may provide to issue
credentials
<dl>
<dt>
Id
</dt>
<dd>
DID associated to the service
</dd>
<dt>
Service Endpoint
</dt>
<dd>
URL endpoint of the issuance service
</dd>
<dt>
Type
</dt>
<dd>
Description of the service
</dd>
</dl>
</dd>
<dt>
eIDAS Certificates
</dt>
<dd>
OPTIONAL Include information about eIDAS Certificates that may be linked to the issuer and used by him.
<dl>
<dt>
Certificate Issuer Number
</dt>
<dd>
Identification of the cerfificate issuer
</dd>
<dt>
Certificate PEM
</dt>
<dd>
PEM of the eIDAS Certificate
</dd>
<dt>
Certificate Serial Number
</dt>
<dd>
Serial number of the eIDAS Certificate
</dd>
</dl>
</dd>
</dl>
<section data-dfn-for="JSON-LD Context">
<h2>
JSON-LD Context
</h2>
<p>
JSON-LD is a JSON-based format used to serialize Linked Data.
</p>
<p>
The JSON-LD representation defines the following representation-specific entries:
</p>
<dl>
<dt>
@context
</dt>
<dd>
The JSON-LD Context is either a string or a list containing any combination of strings and/or
ordered
maps.
</dd>
</dl>
</section>
<section data-dfn-for="Organization Info">
<h2>
Organization Info
</h2>
<p>
The trusted issuer registry contains all the information about organization issuing the credentials.
That implies both legal information and information to present the issuer to the users.
</p>
The MANDATORY properties about the organization info are:
<dl>
<dt>
Legal Name
</dt>
<dt>
Domain Name
</dt>
<dd>
Company base domain
</dd>
</dl>
Other OPTIONAL properties that CAN be listed about a Trusted Issuer providing legal information about him:
<ul>
<li>areaGroup</li>
<li>EORI</li>
<li>discoveryURL</li>
<li>identifierBag</li>
<li>legalAddress</li>
<li>legalPersonalIdentifier</li>
<li>LEI</li>
<li>SEED</li>
<li>SIC</li>
<li>taxReference</li>
<li>VATRegistration</li>
</ul>
<section data-dfn-for="Preferred Display">
<h2>
Preferred Display
</h2>
The organization info CAN also contain information about how the data MUST be presented, under the
<b>Preferred Display</b> property:
<dl>
<dt>
preferredDisplay
</dt>
<dd>
<dl>
<dt>
Preferred Name
</dt>
<dd>
Name used to display the issuer.
</dd>
<dt>
Logo
</dt>
<dd>
OPTIONAL Logo to represent the issuer.
</dd>
<dt>
Style
</dt>
<dd>
OPTIONAL Color and font family employed RECOMMENDED to display the issuer.
</dd>
<dt>
Background
</dt>
<dd>
OPTIONAL Color or image uri background RECOMMENDED to display the issuer.
</dd>
</dl>
</dd>
</dl>
</section>
</section>
<section data-dfn-for="Accreditations">
<h2>
Accreditations
</h2>
<p>
The accreditations are issued by trusted members in charge of the platform management.
</p>
<p>
The accreditations indicate which credential schemas can be issued by the issuer and give
information
about the validation process executed to issue those credentials.
</p>
<dl>
<dt>
Accreditor
</dt>
<dd>
<a>DID</a> of the trusted manager auditing the issuance process
</dd>
<dt>
CreatedAt
</dt>
<dd>
Time of issuance of the accreditation
</dd>
<dt>
Expiration Date
</dt>
<dd>
Time until which the accreditation is valid
</dd>
<dt>
Credential Schema
</dt>
<dd>
Schema of the credential allowed to issue by this accreditation
</dd>
<dt>
Level of Trust
</dt>
<dd>
Designated level of trust of the validation process, following eIDAS directives
</dd>
<dt>
Evidence
</dt>
<dd>
Description of the identity validations performed during the issuance process
</dd>
<dt>
Proof
</dt>
<dd>
<a>Linked Data Proof</a> issued by the Trusted manager to validate the accreditation.
</dd>
</dl>
</section>
<section data-dfn-for="Proof">
<h2>
Proof
</h2>
<p>
<a>Data Proof</a> asserting the event and the current resulting state of the <a></a>Data
Agreement</a>, as described in <a href="https://www.w3.org/TR/vc-data-model/#proofs-signatures">VC
Data
Model</a>. This can be one or
more cryptographic proofs that can be used to detect tampering and
verify the
authorship of a modification or acceptance event.
</p>
<p>
The governance service MUST assert the truth of the contents of an Issuer record by signing them with
a
platform <a>DID</a>.
</p>
</section>
<pre class="example" title="Data Agreement Template">
<pre class="json">
{
"@context": "https://gataca.io/schemas/tir/2020/v1",
"accreditations": [{
"accreditor": "did:gatc:2abcd...ABC",
"createdAt": {},
"credentialSchema": "https://gataca.io/tsr/exampleSchema1.json",
"evidence": {
"evidenceDocuments": ["Passport"],
"documentPresence": "Physical",
"id": "https://essif.europa.eu/tsr/evidence/f2aeec97-fc0d-42bf-8ca7-0548192d4231",
"subjectPresence": "Physical",
"type": [ "DocumentVerification"]
},
"expirationDate": {},
"levelOfTrust": 2,
"proof": [{
"created": {},
"jws": "abc...123=",
"proofPurpose": "assertionMethod",
"type": "EidasSeal2021",
"verificationMethod": "did:gatc:2abcd...ABC#123456789"
}],
"validFrom": {}
}],
"eidasCertificates": [{
"eidasCertificateIssuerNumber": "123456",
"eidasCertificatePem": "[...PEM-ENC-CERT...]",
"eidasCertificateSerialNumber": "123456"
}],
"dids": [
"did:gatc:2abcd...ABC#123456789",
"did:ebsi:2abcd...ABC#123456789"
],
"domain": "Education",
"id": "e20993d1-2430-462b-a9d0-2f2ead3345f8",
"organizationInfo": {
"areaGroup": "Education",
"EORI": "AT123456789101",
"discoveryURL": "https://example.organization.com",
"domainName": "https://example.organization.com",
"identifierBag": "ddd1ebce-8305-4edf-b6b6-7588aa021311",
"legalAddress": "Example Street, 38, 3 Izq, Madrid, Spain",
"legalName": "Example Legal Name",
"legalPersonalIdentifier": "123456789",
"LEI": "12341212EXAMPLE34512",
"preferredDisplay": {
"background": {
"color": "#ABCDEF",
"uri": "https://example.org/background.jpg"
},
"logo": "https://example.org/logo.jpg",
"preferredName": "Brand Name",
"style": {
"color": "#ABCDEF",
"fontFamily": "arial"
}
},
"SEED": "AT12345678910",
"SIC": "1234",
"taxReference": "123456789",
"VATRegistration": "ATU12345678"
},
"proof": [{
"created": {},
"jws": "abc...123=",
"proofPurpose": "assertionMethod",
"type": "EidasSeal2021",
"verificationMethod": "did:gatc:2abcd...ABC#123456789"
}],
"serviceEndpoints": [{
"id": "did:gatc:2abcd...ABC#123456789#openid",
"serviceEndpoint": "https://openid.example.com/",
"type": "OpenIdConnectVersion1.0Service"
}]
}
</pre>
</pre>
</section>
<section data-dfn-for="Resolution API">
<h1>Resolution API</h1>
<p>
The resolution API is a very simple query <a>REST API</a>, only with GET Operations
</p>
<p class="ednote">
This document does not aim to standarize operations for platform management, just resolution operations.
</p>
<p>
The governance resoluion API to expose the trusted issuer registry MUST conform with <a
href="https://gataca-io.github.io/vui-core/issuerResolution.html">the Issuer Resolution API defined</a>
on the
corresponding
<a>VUI</a> working package.
</p>
</section>
<section id="tof"></section>
</body>
</html>