/
openid-cx.draft-3.html
executable file
·1651 lines (1345 loc) · 67.5 KB
/
openid-cx.draft-3.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
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en"><head><title>Draft: Contract Exchange Extension 1.0 - Draft 3</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="description" content="Contract Exchange Extension 1.0 - Draft 3">
<meta name="generator" content="xml2rfc v1.35 (http://xml.resource.org/)">
<style type='text/css'><!--
body {
font-family: verdana, charcoal, helvetica, arial, sans-serif;
font-size: small; color: #000; background-color: #FFF;
margin: 2em;
}
h1, h2, h3, h4, h5, h6 {
font-family: helvetica, monaco, "MS Sans Serif", arial, sans-serif;
font-weight: bold; font-style: normal;
}
h1 { color: #900; background-color: transparent; text-align: right; }
h3 { color: #333; background-color: transparent; }
td.RFCbug {
font-size: x-small; text-decoration: none;
width: 30px; height: 30px; padding-top: 2px;
text-align: justify; vertical-align: middle;
background-color: #000;
}
td.RFCbug span.RFC {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: bold; color: #666;
}
td.RFCbug span.hotText {
font-family: charcoal, monaco, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: normal; text-align: center; color: #FFF;
}
table.TOCbug { width: 30px; height: 15px; }
td.TOCbug {
text-align: center; width: 30px; height: 15px;
color: #FFF; background-color: #900;
}
td.TOCbug a {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, sans-serif;
font-weight: bold; font-size: x-small; text-decoration: none;
color: #FFF; background-color: transparent;
}
td.header {
font-family: arial, helvetica, sans-serif; font-size: x-small;
vertical-align: top; width: 33%;
color: #FFF; background-color: #666;
}
td.author { font-weight: bold; font-size: x-small; margin-left: 4em; }
td.author-text { font-size: x-small; }
/* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
a.info {
/* This is the key. */
position: relative;
z-index: 24;
text-decoration: none;
}
a.info:hover {
z-index: 25;
color: #FFF; background-color: #900;
}
a.info span { display: none; }
a.info:hover span.info {
/* The span will display just on :hover state. */
display: block;
position: absolute;
font-size: smaller;
top: 2em; left: -5em; width: 15em;
padding: 2px; border: 1px solid #333;
color: #900; background-color: #EEE;
text-align: left;
}
a { font-weight: bold; }
a:link { color: #900; background-color: transparent; }
a:visited { color: #633; background-color: transparent; }
a:active { color: #633; background-color: transparent; }
p { margin-left: 2em; margin-right: 2em; }
p.copyright { font-size: x-small; }
p.toc { font-size: small; font-weight: bold; margin-left: 3em; }
table.toc { margin: 0 0 0 3em; padding: 0; border: 0; vertical-align: text-top; }
td.toc { font-size: small; font-weight: bold; vertical-align: text-top; }
ol.text { margin-left: 2em; margin-right: 2em; }
ul.text { margin-left: 2em; margin-right: 2em; }
li { margin-left: 3em; }
/* RFC-2629 <spanx>s and <artwork>s. */
em { font-style: italic; }
strong { font-weight: bold; }
dfn { font-weight: bold; font-style: normal; }
cite { font-weight: normal; font-style: normal; }
tt { color: #036; }
tt, pre, pre dfn, pre em, pre cite, pre span {
font-family: "Courier New", Courier, monospace; font-size: small;
}
pre {
text-align: left; padding: 4px;
color: #000; background-color: #CCC;
}
pre dfn { color: #900; }
pre em { color: #66F; background-color: #FFC; font-weight: normal; }
pre .key { color: #33C; font-weight: bold; }
pre .id { color: #900; }
pre .str { color: #000; background-color: #CFF; }
pre .val { color: #066; }
pre .rep { color: #909; }
pre .oth { color: #000; background-color: #FCF; }
pre .err { background-color: #FCC; }
/* RFC-2629 <texttable>s. */
table.all, table.full, table.headers, table.none {
font-size: small; text-align: center; border-width: 2px;
vertical-align: top; border-collapse: collapse;
}
table.all, table.full { border-style: solid; border-color: black; }
table.headers, table.none { border-style: none; }
th {
font-weight: bold; border-color: black;
border-width: 2px 2px 3px 2px;
}
table.all th, table.full th { border-style: solid; }
table.headers th { border-style: none none solid none; }
table.none th { border-style: none; }
table.all td {
border-style: solid; border-color: #333;
border-width: 1px 2px;
}
table.full td, table.headers td, table.none td { border-style: none; }
hr { height: 1px; }
hr.insert {
width: 80%; border-style: none; border-width: 0;
color: #CCC; background-color: #CCC;
}
--></style>
</head>
<body>
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<table summary="layout" width="66%" border="0" cellpadding="0" cellspacing="0"><tr><td><table summary="layout" width="100%" border="0" cellpadding="2" cellspacing="1">
<tr><td class="header">Draft</td><td class="header">N. Sakimura</td></tr>
<tr><td class="header"> </td><td class="header">M. Nishitani</td></tr>
<tr><td class="header"> </td><td class="header">NRI</td></tr>
<tr><td class="header"> </td><td class="header">H. Nara</td></tr>
<tr><td class="header"> </td><td class="header">TACT Communications,Inc</td></tr>
<tr><td class="header"> </td><td class="header">November 04, 2010</td></tr>
</table></td></tr></table>
<h1><br />Contract Exchange Extension 1.0 - Draft 3</h1>
<h3>Abstract</h3>
<p> This extension defines 1) an extensible Contract format, 2) protocol to exchange the Contract, 3)protocol to share privacy data based on the Contract and 4)protocol to provide access log.
The Proposer creates a signed Proposal which describes what privacy data is wanted and send it to the Signatory specified the End User.
The Signatory, upon agreeing to it, signs agreements and provides the Contract.
The combination of the Proposal and Contract is the mutually signed and is potentially legally binding.
This Contract needs to be stored by all bound parties for a given length of time, usually spanning over many years depending on jurisdictions.
</p>
<p> As these document size may be large while the user agent capability may be limited (e.g., mobile phones), sending them via direct communication and passing only the small reference called "Artifact" through the user agents are advisable. Therefore, as the protocol, use of Artifact Binding is strongly recommended.
</p><a name="toc"></a><br /><hr />
<h3>Table of Contents</h3>
<p class="toc">
<a href="#anchor1">1.</a>
Terminology<br />
<a href="#anchor2">1.1.</a>
Requirements Notation<br />
<a href="#anchor3">1.2.</a>
Definitions and Conventions<br />
<a href="#anchor4">1.3.</a>
Terms<br />
<a href="#anchor5">2.</a>
Overview<br />
<a href="#anchor6">3.</a>
Files<br />
<a href="#anchor7">3.1.</a>
JSON and Token<br />
<a href="#anchor12">3.2.</a>
Structures<br />
<a href="#anchor19">3.3.</a>
Storage and Timestamping<br />
<a href="#anchor20">4.</a>
Protocal<br />
<a href="#anchor21">4.1.</a>
Sending Proposal<br />
<a href="#anchor25">4.2.</a>
Accepting Proposal<br />
<a href="#anchor32">4.3.</a>
Receiving Contract<br />
<a href="#anchor35">4.4.</a>
Notify Contract Status<br />
<a href="#anchor36">4.5.</a>
Data Request<br />
<a href="#anchor42">5.</a>
Security Considerations<br />
<a href="#anchor43">5.1.</a>
non-repudiation<br />
<a href="#anchor44">5.2.</a>
Man-in-the-middle<br />
<a href="#anchor45">5.3.</a>
Eavesdropping<br />
<a href="#anchor46">5.4.</a>
Malicious Providers<br />
<a href="#anchor47">5.5.</a>
Phishing Attack<br />
<a href="#anchor48">5.6.</a>
Private Key Compromise<br />
<a href="#anchor49">Appendix A.</a>
Acknowledgements<br />
<a href="#rfc.references1">6.</a>
Normative References<br />
<a href="#rfc.authors">§</a>
Authors' Addresses<br />
</p>
<br clear="all" />
<a name="anchor1"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1"></a><h3>1.
Terminology</h3>
<a name="anchor2"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1.1"></a><h3>1.1.
Requirements Notation</h3>
<p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <a class='info' href='#RFC2119'>[RFC2119]<span> (</span><span class='info'>Bradner, B., “Key words for use in RFCs to Indicate Requirement Levels,” 1997.</span><span>)</span></a> .
</p>
<a name="anchor3"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1.2"></a><h3>1.2.
Definitions and Conventions</h3>
<p> All OpenID 2.0 Artifact Binding messages that contain OpenID Contract Exchange (CX) JSON node MUST contain "type" member starts with the following URI.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
http://specs.openid.net/extensions/cx/1.0/
</pre></div>
<p>
</p>
<p> Variety of sub class message contains fragments at the end of the type URI.
</p>
<a name="anchor4"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1.3"></a><h3>1.3.
Terms</h3>
<p>In addition to the terminology used in <a class='info' href='#OPENID_AB'>OpenID Artifact Binding 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “OpenID Artifact Binding 1.0,” September 2010.</span><span>)</span></a> [OPENID_AB], following terms are used.
</p>
<p>
</p>
<ul class="text">
<li> Party
<ul class="text">
<li>Entity which is bound to a contract and one of Client , Server , Proposer and Signatory.
</li>
<li>Party may be a web server or a smart device client.
</li>
</ul>
</li>
<li> End User
<ul class="text">
<li>Person who has privillege of controlling Privacy Data. End User MUST be identified at OpenID Provider and MAY authorize Contract to be signed and valid.
</li>
</ul>
</li>
<li> Privacy Data
<ul class="text">
<li>Data which is own by End User and can be accessed to permitted Party.
</li>
</ul>
</li>
<li> Contract
<ul class="text">
<li>Document to prove that Party can access Privacy Data under stated condition.
</li>
</ul>
</li>
<li> Client
<ul class="text">
<li>Privacy Data user.
</li>
</ul>
</li>
<li> Server
<ul class="text">
<li>Privacy data holder. Exposes the Privacy Data endpoint.
</li>
</ul>
</li>
<li> Proposer
<ul class="text">
<li>Contract process initiator. Orchestrates the process of data access authorization between Clients and Server with the help of Signatory. <a class='info' href='#OPENID_AB'>OpenID Artifact Binding 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “OpenID Artifact Binding 1.0,” September 2010.</span><span>)</span></a> [OPENID_AB]Relying Party.
</li>
</ul>
</li>
<li> Signatory
<ul class="text">
<li>Contract signer in the charge of the End User. <a class='info' href='#OPENID_AB'>OpenID Artifact Binding 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “OpenID Artifact Binding 1.0,” September 2010.</span><span>)</span></a> [OPENID_AB] Provider.
</li>
</ul>
</li>
<li> Request
<ul class="text">
<li>Document to describe what data is wanted by Client
</li>
</ul>
</li>
<li> Proposal
<ul class="text">
<li>Document to hold a couple of Request and delivered to Signatory by Proposer to start the CX process.
</li>
</ul>
</li>
<li> Acceptance
<ul class="text">
<li>Document to describe how the privacy data can be accessed.
</li>
</ul>
</li>
<li> Contract Part
<ul class="text">
<li>Document which compose Contract and hold a couple of Acceptance and securely distributed to specific Party.
</li>
</ul>
</li>
<li> Token
<ul class="text">
<li>Signed JSON object which serialized into a formated string. Format is defined i n<a class='info' href='#JSON_SIMPLE_SIGN_1_0'>JSON Simple Sign 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Sign ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_SIGN_1_0].
</li>
</ul>
</li>
<li> Service
<ul class="text">
<li>Data or experience provided by Proposer to End User. Some Services consist of couple of End User's Privacy Data which are provided by Server and used by Client. Parties MUST fulfill Contract to collaborate to provide Service.
</li>
</ul>
</li>
</ul><p>
</p>
<a name="anchor5"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2"></a><h3>2.
Overview</h3>
<p>The contract exchange extension(CX) is OpenID extension identified by the URI "http://openid.net/srv/cx/1.0/#". The contract is the document to prove that all parties bound to that have rights and obligations on consuming and providing services between each other.
</p>
<p>
</p>
<p>CX protocol is based on <a class='info' href='#OPENID_AB'>OpenID Artifact Binding 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “OpenID Artifact Binding 1.0,” September 2010.</span><span>)</span></a> [OPENID_AB] and some <a class='info' href='#JSON'>JSON(Javascript Object Notation)<span> (</span><span class='info'>, “The application/json Media Type for JavaScript Object Notation (JSON),” .</span><span>)</span></a> [JSON] messages structure used in CX are defined to exchange non-repudiate message. When an End User starts consuming a CX-based service at a RP(Proposer), the RP compose a Proposal JSON which is compiled with OpenID Artifact Binding Request files defined by parties to be bound to the CX service and contract. The RP starts OpenID Artifact Binding session with the Proposal to the OP(Signatory) specified by the End User, the End User is authenticated at the OP and agrees to compose the CX Contract, and finally the OP provides the CX Contract in OpenID Artifact Binding assertion to the RP.
</p>
<p>
</p>
<p>With sharing Contract in advance and presenting Contract identfier at specified endpoints, the RP and other Parties bound to the Contract can be authenticated and request data services.
</p>
<a name="anchor6"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3"></a><h3>3.
Files</h3>
<p>CX exchange Contract JSON by extending <a class='info' href='#OPENID_AB'>OpenID Artifact Binding 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “OpenID Artifact Binding 1.0,” September 2010.</span><span>)</span></a> [OPENID_AB] protocol. <a class='info' href='#JSON'>JSON(Javascript Object Notation)<span> (</span><span class='info'>, “The application/json Media Type for JavaScript Object Notation (JSON),” .</span><span>)</span></a> [JSON] is the default document format, the extended <a class='info' href='#JSON_SIMPLE_SIGN_1_0'>JSON Simple Sign 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Sign ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_SIGN_1_0] is used for digital signature and the extended <a class='info' href='#JSON_SIMPLE_ENC_1_0'>JSON Simple Encryption 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Encryption ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_ENC_1_0] is used for asymmetric encryption with public key infrastructure.
</p>
<a name="anchor7"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.1"></a><h3>3.1.
JSON and Token</h3>
<p>CX uses JSON format which is used in <a class='info' href='#OPENID_AB'>OpenID Artifact Binding 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “OpenID Artifact Binding 1.0,” September 2010.</span><span>)</span></a> [OPENID_AB] Request file and assertion. All file used for CX MUST have "type" member in a JSON object( enclosed in open and close curly braces ) and the value of "type" MUST be URI and start with :
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
http://specs.openid.net/cx/1.0/#
</pre></div>
<p>CX JSON object MAY optionally have "id" member for specifying any particular JSON object. "id" MUST be a URI uniquely allocated by the creating party.
</p>
<p>So, a generic CX JSON object likes like the following
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
{
"type" : "http://specs.openid.net/cx/1.0/#",
"id" : "http://rp.net/432144395df"
}
</pre></div>
<a name="anchor8"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.1.1"></a><h3>3.1.1.
Extending CX JSON</h3>
<p>
Although any CX JSON object MUST have members specified for "type", any other member MAY be used if parties agree the meaning of it. Any CX JSON MAY has any other JSON object as a member in itself. If a member is a JSON object, "type" and "id" SHOULD be checked firstly and this should be done recursively.
</p>
<a name="anchor9"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.1.2"></a><h3>3.1.2.
Signed JSON and Token</h3>
<p>
Some CX JSON object MUST be digitally signed to prove a particular JSON object's composer.
<a class='info' href='#JSON_SIMPLE_SIGN_1_0'>JSON Simple Sign 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Sign ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_SIGN_1_0] is the default format. Some CX JSON is enveloped by <a class='info' href='#JSON_SIMPLE_SIGN_1_0'>JSON Simple Sign 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Sign ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_SIGN_1_0] .
Signed CX JSON is formed in the "Web Token Serialization" defined in <a class='info' href='#JSON_SIMPLE_SIGN_1_0'>JSON Simple Sign 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Sign ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_SIGN_1_0]. Following the sample of signed and tokenized CX JSON.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
6a82841eea9c17677083b2965bc4e51e0e8e22e208121ab69711b3e5918c6677.eyAndGVzdCc6J2RhdGEnfQ==
</pre></div>
<a name="anchor10"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.1.3"></a><h3>3.1.3.
Encrypted JSON</h3>
<p>
Some CX JSON object SHOULD be asymmetrically encrypted to ensure that only the recipient can read the JSON object.
<a class='info' href='#JSON_SIMPLE_ENC_1_0'>JSON Simple Encryption 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Encryption ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_ENC_1_0] is the default format.
</p>
<a name="anchor11"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.1.4"></a><h3>3.1.4.
OpenID Extention</h3>
<p>
As an extension of OpenID, CX JSON object must be included as "cx" member of OpenID JSON object.
Beause CX JSON object on OpenID message MUST be signed, "cx" member is actually a token string.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
{
... OpenID JSON object parameters ...
"cx" : "crypto_segment.claim_segment",
}
</pre></div>
<a name="anchor12"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.2"></a><h3>3.2.
Structures</h3>
<a name="anchor13"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.2.1"></a><h3>3.2.1.
Non-Normative Examples</h3>
<p>TODO: Here should be a sample use case description for a CX transaction for non-normative examples in this section and delivered to the RP from OP in an OpenID Artifact Binding assertion.
</p>
<p> An OpenID Artifact Binding assertion holding a CX Contract might be described here .
</p>
<p>
Here is a non-normative example of a CX Contract which is actually the <a class='info' href='#JSON_SIMPLE_SIGN_1_0'>JSON Simple Sign 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Sign ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_SIGN_1_0]version of CX Acceptance.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
{
"type" : "http://specs.openid.net/cx/1.0/#contract",
"id" : "http://op.com/contract/f43213214",
"signatory_certs" : "PEM string of OP(signer)'s X.509 certificate " ,
... (other JSON SIMPLE SIGN MEMBERS ) ...
}
</pre></div>
<p>
Here is a non-normative example of a CX Acceptance which is composed by the OP.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
{
// sample of a Acceptance
}
</pre></div>
<p>
Each privacy data encrypted and held in CX Acceptance and Response is originally formed like the following JSON object
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
{
// sample of a Sdata
}
</pre></div>
<p>Also original request files are formed like the following JSON before they are digitally signed
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
{
// sample of a Sdata
}
</pre></div>
<a name="anchor14"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.2.2"></a><h3>3.2.2.
Request</h3>
<p>
Request is a extended <a class='info' href='#OPENID_AB'>OpenID Artifact Binding 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “OpenID Artifact Binding 1.0,” September 2010.</span><span>)</span></a> [OPENID_AB] Request file enveloped by <a class='info' href='#JSON_SIMPLE_SIGN_1_0'>JSON Simple Sign 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Sign ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_SIGN_1_0].
Every party bound to Contract MUST prepare Request in signed token format.
</p>
<p>
Following parameters are placed in a JSON object held by "payload" parameter of <a class='info' href='#JSON_SIMPLE_SIGN_1_0'>JSON Simple Sign 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Sign ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_SIGN_1_0] JSON.
</p>
<p>
</p>
<ul class="text">
<li> type
<ul class="text">
<li>string(URI)
</li>
<li>http://specs.openid.net/cx/1.0/#request"
</li>
</ul>
</li>
<li> id
<ul class="text">
<li>optional,string(URI))
</li>
<li>Identifier for the particular Request file
</li>
</ul>
</li>
<li> client_id
<ul class="text">
<li>string(URI)
</li>
<li>Identifier for Client.
</li>
</ul>
</li>
<li> server_id
<ul class="text">
<li>optional,string(URI)
</li>
<li>Identifier for Server.
</li>
<li>This parameter MAY be specified only when Client wants End User to permit to use a particular service.
</li>
<li>In this case, Client has already known the service endpoint.
</li>
</ul>
</li>
<li> payment_to
<ul class="text">
<li>optional,string(any)
</li>
<li>End User SHOULD be given "payment_to" from Client for every CX service request to the service endpoint of Contract.
</li>
</ul>
</li>
<li> payment_from
<ul class="text">
<li>optional,string(any)
</li>
<li>End User SHOULD pay "payment_from" to Client for every CX service request of Contract.
</li>
</ul>
</li>
<li> template
<ul class="text">
<li>optional,string(any)
</li>
<li>End User MAY read "template" text to agree to create Contract.
</li>
</ul>
</li>
<li> template_type
<ul class="text">
<li>optiona,string(Content-Type)
</li>
<li>Type of text provided by "template". Default is "text/plain".
</li>
</ul>
</li>
<li> endpoint
<ul class="text">
<li>optional,string(URI)
</li>
<li>URI from which data is provieded at Server.
</li>
</ul>
</li>
<li> notify
<ul class="text">
<li>optional,string(URI)
</li>
<li>Notifiation endpoint directely called by Party like Propose if Contract is provieded.
</li>
</ul>
</li>
<li> identity
<ul class="text">
<li>optional,string
</li>
<li>End user's OpenID identfier at Server
</li>
</ul>
</li>
<li> client_certs
<ul class="text">
<li>string(base64url)
</li>
<li>The PEM formatted string version of client_id's X.509 certificate used for this <a class='info' href='#JSON_SIMPLE_SIGN_1_0'>JSON Simple Sign 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Sign ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_SIGN_1_0] JSON.
</li>
</ul>
</li>
<li> server_certs
<ul class="text">
<li>optional,string(base64url)
</li>
<li>The PEM formatted string version of server_id's X.509 certificate used when "server_id" specified in Request.
</li>
</ul>
</li>
</ul><p>
</p>
<p>The following is a non-normative sample for CX Request JSON object:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
{
"type": "http://jsonenc.info/jss/",
....
"payload": {
"type" : "http://specs.openid.net/cx/1.0/#request",
"client_id" : "http://rp.net",
"server_id": "http://op.com",
"payment_from" : "500JPY",
"payment_to" : "5PT",
"template" :
"...(base64 encoded text for End User to grant the CX contract)..."
"client_certs" : "...( PEM STRING OF client_id's X.509 CERTIFICATE)...",
"server_certs" : "...( PEM STRING OF server_id's X.509 CERTIFICATE )...",
... ( OTHER OPENID REQUEST PARAMTERS ) ...,
... ( OTHER JSON SIMPLE SIGN PARAMTERS ) ...
}
}
</pre></div>
<a name="anchor15"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.2.3"></a><h3>3.2.3.
Proposal</h3>
<p>
Proposal is a contrainer JSON to hold Request token of parties and enveloped by <a class='info' href='#JSON_SIMPLE_SIGN_1_0'>JSON Simple Sign 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Sign ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_SIGN_1_0].
</p>
<p>
Following parameters are placed in a JSON object held by "payload" parameter of <a class='info' href='#JSON_SIMPLE_SIGN_1_0'>JSON Simple Sign 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Sign ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_SIGN_1_0] JSON.
</p>
<p>
</p>
<ul class="text">
<li> type
<ul class="text">
<li>string(URI)
</li>
<li>http://specs.openid.net/cx/1.0/#proposal
</li>
</ul>
</li>
<li> id
<ul class="text">
<li>string(URI)
</li>
<li>unique identifier for a specific Proposal specified by Proposer
</li>
</ul>
</li>
<li> proposer_id
<ul class="text">
<li>string(URI)
</li>
<li>Identifier for Proposer
</li>
</ul>
</li>
<li> reqs
<ul class="text">
<li>array of object( <a class='info' href='#JSON_SIMPLE_SIGN_1_0'>JSON Simple Sign 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Sign ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_SIGN_1_0] )
</li>
<li>JSON array of Requests in token string format.
</li>
</ul>
</li>
<li> notify
<ul class="text">
<li>optional,string(URI)
</li>
<li>Signatory MAY directly send message to this URI. As described later in Notification, Signatory MAY notify the status of Contract to Proposer.
</li>
</ul>
</li>
<li> proposer_certs
<ul class="text">
<li>string(base64url)
</li>
<li>The PEM formatted string version of Proposer's X.509 certificate used for this <a class='info' href='#JSON_SIMPLE_SIGN_1_0'>JSON Simple Sign 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Sign ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_SIGN_1_0] envelope.
</li>
</ul>
</li>
</ul><p>
</p>
<p>The following is a non-normative sample for Proposal JSON object:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
{
"type": "http://jsonenc.info/jss/",
....
"payload": {
"type": "http://specs.openid.net/cx/1.0/#proposal",
"id" : "http://rp.net/432143214321",
"proposer_id" : "http://rp.net/",
"reqs": [
"6a82841eea9c17677083b2965bc4e51e0e8e22e208121ab69711b3e5918c6677.eyAndGVzdCc6J2RhdGEnfQ==",
"1cf28c36f7fbb9e97828a687706cd14458d4b81713264d12852a0c8a669bee78.eyAnc2FtcGxlJzondGhlIG90aGVyJ30=",
]
"proposer_certs": "...( PEM STRING OF PROPOSER's X.509 CERTIFICATE )...",
.... ( OTHER EXTENDED PROPOSAL JSON MEMBERS )...
}
}
</pre></div>
<a name="anchor16"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.2.4"></a><h3>3.2.4.
Acceptance</h3>
<p>
Acceptance is a copy form original Request "payload" with extra parameters including End User's privacy data added by Signagory and End User.
Signatory MUST produce two CX Acceptances for a single CX Request, one is for Client's Contract Part and the other is for Server's Contract Part.
Privacy data like canonical identifier SHOULD be different from each other.
</p>
<p>
Other paramters than the following have same meaning as ones defined in Request.
</p>
<p>
</p>
<ul class="text">
<li> type
<ul class="text">
<li>string(URI)
</li>
<li>"http://specs.openid.net/cx/1.0/#acceptance"
</li>
</ul>
</li>
<li> id
<ul class="text">
<li>string(URI)
</li>
<li>unique identifier given by Signatory
</li>
</ul>
</li>
<li> request_id
<ul class="text">
<li>string(URI)
</li>
<li>Identifier to original Request
</li>
</ul>
</li>
</ul><p>
</p>
<p>The following is a non-normative sample for Acceptance object:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
{
"type" : "http://specs.openid.net/cx/1.0/#acceptance",
"client_id" : "http://rp.net",
"server_id" : "http://op.com",
"payment_from" : "500JPY",
"payment_to" : "5PT",
"template" :
" ... (base64 encoded text for End User to grant the CX contract)....",
"request_id" : "http://rp.net/proposal/i393",
"endpoint" : "http://op.com/endpoint/",
"identifier" : "http://op.com/user/g3430",
...( OTHER OPENID REQUEST PARAMTERS ) ...,
}
</pre></div>
<a name="anchor17"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.2.5"></a><h3>3.2.5.
Contract Part</h3>
<p>
Contract Part is container JSON object of Acceptances and enveloped by <a class='info' href='#JSON_SIMPLE_SIGN_1_0'>JSON Simple Sign 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Sign ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_SIGN_1_0] and provided for each Party by Signatory. All Contract Part shares a Contract Indenfier.
</p>
<p>
Following parameters are placed in a JSON object held by "payload" parameter of <a class='info' href='#JSON_SIMPLE_SIGN_1_0'>JSON Simple Sign 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Sign ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_SIGN_1_0] JSON.
</p>
<p>
</p>
<ul class="text">
<li> type
<ul class="text">
<li>string(URI)
</li>
<li>http://specs.openid.net/cx/1.0/#contract_part
</li>
</ul>
</li>
<li> id
<ul class="text">
<li>opitinal,string(URI)
</li>
<li>Identifier to this Contract Part
</li>
</ul>
</li>
<li> contract_id
<ul class="text">
<li>string(URI)
</li>
<li>Unique URL given by Signatory. All Contract Part provided to each Party for a Proposal MUST be same.
</li>
</ul>
</li>
<li> party_id
<ul class="text">
<li>string(URI)
</li>
<li>client_id, server_id or proposer_id of this Contract.
</li>
</ul>
</li>
<li> proposal_id
<ul class="text">
<li>string(URI)
</li>
<li>Identifier to original Proposal. The signature segment of the original Proposal Token MUST be appended to the end of the original Proposal URI as URI fragment.
</li>
</ul>
</li>
<li> acceptances
<ul class="text">
<li>array of object(Acceptance)
</li>
<li>JSON array of Acceptance
</li>
</ul>
</li>
<li> signatory_certs
<ul class="text">
<li>string(base64url)
</li>
<li>The PEM formatted string version of Signatory's X.509 certificate used for this <a class='info' href='#JSON_SIMPLE_SIGN_1_0'>JSON Simple Sign 1.0<span> (</span><span class='info'>Protivity Government Services and Nomura Research Institute, “JSON Simple Sign ver.1 draft00,” September 2010.</span><span>)</span></a> [JSON_SIMPLE_SIGN_1_0] JSON.
</li>
</ul>
</li>
</ul><p>
</p>
<p>The following is a non-normative sample for Contract Part object:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
{
"type": "http://jsonenc.info/jss/",
....
"payload": {
"type" : "http://specs.openid.net/cx/1.0/#contract",
"id" : "http://op.com/id/f43213214",
"contract_id" : "http://op.com/id/contract/x43513514",
"party_id" : "http://res.net/",
"acceptances" : [
{
"type" : "http://specs.openid.net/cx/1.0/#acceptance",
"id" : "http://op.com/id/f43213215",
"client_id" : "http://rp1.net/",
"server_id" : "http://res.net/",
"endpoint" : "http://res.net/endpoint/",
"identifier": "http://op.com/user/x43432",
.....
},
{
"type" : "http://specs.openid.net/cx/1.0/#acceptance",
"id" : "http://op.com/id/f43213216",