-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathindex.html
468 lines (434 loc) · 20.3 KB
/
index.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
<!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",
url: "https://gataca.io",
mailto: "it@gataca.io"
},
],
github: "decentralized-identity/vui",
shortName: "vui",
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">Verifier Universal Interface</h1>
<h2 id="subtitle">Definition of the standards and interfaces that might be consumed by any verifier to be
interoperable with any wallet</h2>
<section id="abstract">
<p>
Decentralized digital identity, or "self-sovereign" identity (SSI), is a new paradigm proposed for managing
digital identities. Relying on Decentralized identifiers (DIDs) and Verifiable Credentials (VC), the subject
and his personal credentials are independent from any centralized registry,
identity provider, or certificate authority.
</p>
<p>
On the Decentralized Identity model, the role associated to requesting and verifying credentials is
defined as the Verifier.
</p>
<dd>
The verifier functionality is to support the data collector as it tries to acquire credentials from some
other party for the purpose of negotiating a business transaction. It does so by creating presentation
requests (or Presentation Definition as it is called in the draft DIF specfication for Presentation
Exchange) that ask for such credentials, sending them to a holder component of another party, receiving
a
response to such a request (which we call a 'presentation'), verifying the presentation, i.e. checking
the
signature and other proofs of the veracity of both the construction of the presentation as well as its
contents, thus providing the party with verified data.
</dd>
<p>
This document specifies the interfaces that MAY be consumed by any verifier allowing him to be interoperable
with any wallet fulfilling this interface, regardless of:
<ul>
<li>
The vendor of the technology
</li>
<li>
The technology stack used
</li>
<li>
The SSI governance framework in use
</li>
</ul>
</p>
<p class="ednote">
Despite its format, this document does not aim to be published on the W3C as a standard normative, rather it aims to
propose a universal interfaces for a verifier. However, this format is however extremely adequate to allow work
and contribution
on the protocol definition.
</p>
</section>
<section id="sotd">
<p> </p>
</section>
<section data-dfn-for="Context">
<h1>Context</h1>
<p>
As different technology providers are offering SSI solutions, it becomes increasingly relevant to ensure
interoperability between them. On a not yet stable market, most providers aim to offer the whole
SSI stack: components for holders, verifiers, issuers and did-resolver.
</p>
<p>
In order to avoid vendor lock-ins, the APIs exploited by the Verifiers component can be standarized. This
document aims to offer the necessary capabilities for a Verifier component of a technology provider to
use the technology stack of another SSI provider.
</p>
<p>
This document presents an overview of all the different interfaces covered by the Verifier Universal
Interface working group. It refers to each of their specs and tries to provide (if needed) additional
information on how they relate.
</p>
<section id="conformance">
</section>
<section id="terminology">
<h2>Terminology</h2>
<dl>
<dt>Decentralized Identifier(DID)</dt>
<dd>As defined in [[DID-CORE]].</dd>
<dt>DID document</dfn></dt>
<dd>As defined in [[DID-CORE]].</dd>
<dt>DID resolution</dt>
<dd>As defined in [[DID-RESOLUTION]].</dd>
<dt>DID resolver</dt>
<dd>As defined in [[DID-RESOLUTION]].</dd>
<dt>Verifiable Credential(VC)</dt>
<dd>As defined in [[VC-DATA-MODEL]].</dd>
<dt>Verifiable Presentation(VP)</dt>
<dd>As defined in [[VC-DATA-MODEL]].</dd>
</dl>
</section>
<section data-dfn-for="Operations" class="informative">
<h2>Verifier operations</h2>
<p>
Any Verifier MUST perform the following operations:
<ol class="oplist">
<li>
Request and receive specific information to holders in the form of Verifiable Credentials (presented
in a Verifiable Presentation)
</li>
<li>
Verify received VCs. That includes:
<ol>
<li>
Verify the proofs of every credential
</li>
<li>
Verify the proof of the presentation
</li>
<li>
Verify that the information received matches the information requested
</li>
</ol>
</li>
</ol>
Additionally, any Verifier SHALL perform the following operations:
<ol start="2" class="oplist start2">
<li>
While verifying the received VCs:
<ol start="4" class="oplist start4">
<li>
Verify the Issuer of the credential
<ol class="oplist">
<li>
Its authority over the credential
</li>
<li>
Its associated trust level
</li>
</ol>
</li>
<li>
Verify the status of every credential
</li>
<li>
Verify and match the ownership of the Verifiable Credentials and the Verifiable Presentation
</li>
<li>
Verify that all credentials can be linked to the same entity
</li>
<li>
Verify that the credentials requested satisfy some stablished constraints
</li>
</ol>
</li>
<li>
Verify that the credentials have been handled from a secure wallet
</li>
<li>
Authenticate the wallet owner
</li>
<li>
Manage the consent of the usage of the information inside the credentials
</li>
<li>
Ensure user anonimity and non external traceability
</li>
<li>
Manage selective disclosure of the information contained on the credentials
</li>
</ol>
</p>
</section>
</section>
<section data-dfn-for="Interfaces" class="informative">
<h1>Interfaces</h1>
<p>
In order to allow Verifier operation as decribed in <a href="#verifier-operations">the previous section</a>,
this
document proposes a definition for the Interfaces between the Verifier and other components.
</p>
<p>
Those interfaces MUST be independent from any framework or programming language. Interfaces shall be
implemented with standard communication protocols through web services. Usage of REST is recommended.
</p>
Depending on the party to interact and the functionality described to cover, a Verifier SHALL make use of the
following defined interfaces for his operation:
<figure id="api-functional-alignment">
<pre class="json">
+------------------------------------++------------------------------------++-----------------++-----------------+
| Holder || Governance || DID Resolver || Issuer |
+------------------------------------++------------------------------------++-----------------++-----------------+
+------------------------------------------------------------------------------------------------------------------+
|+-----------------++-----------------++-----------------++-----------------++-----------------++-----------------+|
|| || || || || || ||
|| Presentation || Data || Schema || Issuer || DID Resolution || Credential ||
|| Exchange || Agreement || Resolution || Resolution || || Status ||
|| || || || || || Query ||
|| || || || || || ||
|| || || || || || ||
|| API || API || API || API || API || API ||
++-----------------++------------------------------------++-----------------++-----------------++-----------------++
| 1, 2.3, 3, | 2.6, 2.7, | 2.6, 7 | 2.2 | 2.1, 2.2, | 2.3 |
| 4, 6, 7 | 5, 6 | | | 2.4, 4 | |
| |
| Verifier |
| |
+------------------------------------------------------------------------------------------------------------------+
</pre>
<figcaption style="text-align: center;">
Alignment of Interfaces with functionalities to cover
</figcaption>
</figure>
<section data-dfn-for="DID Resolver">
<h1>DID Resolver interfaces</h1>
<section data-dfn-for="DID Resolution">
<h2>DID Resolution</h2>
Standard protocol and considerations for DID Resolution are being defined by a specific working group. <a
href="https://w3c-ccg.github.io/did-resolution/">See [DID-RESOLUTION] </a>.
</section>
</section>
<section data-dfn-for="Issuer">
<h1>Issuer interfaces</h1>
<section data-dfn-for="Credential Status">
<h2>Credential Status</h2>
Standard protocol and considerations for querying the status of the credentials and managing their
revocation are being defined by a specific working group. <a
href="https://w3c-ccg.github.io/vc-status-rl-2020/">See [VC-STATUS-RL-2020] </a>.
</section>
</section>
<section data-dfn-for="Governance">
<h2>Governance interfaces</h2>
<p>
The Identity platform governance should determine what kind of credentials could be issued by the
different
parties, the specific formats and contexts of those credentials, as well as which entities fulfill the
requirements to issue each specific credential.
In order to do that, it might use different registries, that should be queried from any interested
verifier
cooperating with the platform, to allow them to :
<ol>
<li>
Discover the credentials available on the Identity platform
</li>
<li>
Manage the format of every credential
</li>
<li>
Establish the relationship between different credentials, taken as attributes to build more complex
credentials
</li>
<li>
Define and restrict the entities enabled to assert and validate the information from the subjects
</li>
<li>
Assign different levels of trust to the identity validation processes
</li>
</ol>
</p>
<p>
Registries of Issuers and Credential Schemas MAY be separated and managed by different entities.
Multiple registries of Issuers and/or Schemas MAY be queried by a Verifier.
</p>
<p>
Verifiers MAY make use of internal private registries to complement the public registries.
Defining a protocol to merge different registries is outside the scope of this document.
</p>
<p>
Verifiers MAY query and assign different levels of trust to different governance platforms, but all the
platforms should present the same query interface.
</p>
<p>
Registries SHALL be publicly available and auditable. Persisting registries on DLTs is OPTIONAL but
RECOMMENDED as good practice in order to maintain neutrality.
</p>
<p>
Registries MUST offer a web interface. REST protocol SHOULD be employed with HTTP Method GET and
JSON formatting as default.
</p>
<h2>
Discovery
</h2>
<p>
To be defined.
</p>
<p class="ednote">
This section should be filled with discovery of registry endpoints for automatic configuration, as
well as protocols to discover other registries.
</p>
<section data-dfn-for="Issuer Resolution">
<h2>Issuer Registry</h2>
The VUI protocol and considerations for querying the issuer registry are being defined by a specific
working
package inside the VUI. <a href="/vui/issuerResolution">See
[WP-VUI-IssuerResolution] </a>.
</section>
<section data-dfn-for="Schema Resolution">
<h2>Schema Registry</h2>
<p>
This interface is not yet defined. There are no active working groups with this effort.
</p>
</section>
</section>
<section data-dfn-for="Holder">
<h1>Holder interfaces</h1>
<section data-dfn-for="Presentation Exchange">
<h2>Presentation Exchange</h2>
<p>
The VUI protocol and considerations for the Presentation Exchange is being defined by a specific
working
package. <a href="/vui/presentationExchange">See
[WP-VUI-PresentationExchange] </a>.
</p>
<p>
The data model builds upon <a href="/vui/presentationExchange">DIF Presentation
Exchange</a>
with some
optional
additions to support additional features and connect to Data Agreements.
</p>
<p>
For the communication protocol, multiple flavors could be eligible, such as:
</p>
<ul>
<li>
<a href="https://identity.foundation/didcomm-messaging/spec/">DID Comm</a>, which is supported
by <a href="https://identity.foundation/waci-presentation-exchange/">WACI</a>
</li>
<li>
<a href="https://w3c-ccg.github.io/credential-handler-api/">CHAPI</a>
</li>
<li>
<a href="https://w3c-ccg.github.io/vc-api/"">VC-HTTP-APIS</a>
</li>
<li>
<a href="
https://openid.net/specs/openid-connect-4-verifiable-presentations-1_0.html">DID
SIOP</a>
</li>
</ul>
<p>
At this point of in the process of definition and implementation, VUI Presentation Exchange is focused on having
support
on the last one <a
href=" https://openid.net/specs/openid-connect-4-verifiable-presentations-1_0.html">DID
SIOP</a>.
</p>
</section>
<section data-dfn-for="Data Agreements">
<h2>Data Agreements</h2>
<p>
Data Agreements includes Data privacy management oriented for the enforcement of DPIA controls in
privacy
frameworks such as GDPR.
</p>
<p>
The VUI protocol to manage and generate data agreements can be found on its own working package. <a
href="/vui/dataAgreements">See
[WP-VUI-DataAgreements] </a>.
</p>
</section>
</section>
</section>
<section id="tof"></section>
</body>
</html>