-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathopenid-attribute-exchange.txt
1233 lines (539 loc) · 29.8 KB
/
openid-attribute-exchange.txt
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
Draft 01 D. Hardt
J. Bufu
Sxip Identity
J. Hoyt
JanRain
N. Sakimura
Nomura Research Institute, Ltd.
December 9, 2009
OpenID Attribute Exchange 1.1 - Draft 02
Hardt, et al. [Page 1]
OpenID Attribute Exchange 1.1 - Draft 02 December 2009
Abstract
OpenID Attribute Exchange is an OpenID service extension for
exchanging identity information between endpoints. Messages for
retrieval and storage of identity information are provided.
Table of Contents
1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Definitions and Conventions . . . . . . . . . . . . . . . 3
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Information Model . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Subject Identifier . . . . . . . . . . . . . . . . . . . . 5
3.2. Attribute Type Identifier . . . . . . . . . . . . . . . . 5
3.3. Attribute Value . . . . . . . . . . . . . . . . . . . . . 5
3.3.1. Attribute-Specific Encodings . . . . . . . . . . . . . 6
4. Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Fetch Message . . . . . . . . . . . . . . . . . . . . . . . . 8
5.1. Fetch Request Format . . . . . . . . . . . . . . . . . . . 8
5.2. Fetch Response Format . . . . . . . . . . . . . . . . . . 10
6. Store Message . . . . . . . . . . . . . . . . . . . . . . . . 13
6.1. Store Request Format . . . . . . . . . . . . . . . . . . . 13
6.2. Store Response Format . . . . . . . . . . . . . . . . . . 14
6.2.1. Storage Success . . . . . . . . . . . . . . . . . . . 14
6.2.2. Storage Failure . . . . . . . . . . . . . . . . . . . 14
7. Default Schemas . . . . . . . . . . . . . . . . . . . . . . . 16
7.1. Mandatory Data Type . . . . . . . . . . . . . . . . . . . 16
8. Security Considerations . . . . . . . . . . . . . . . . . . . 18
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
10.1. Normative References . . . . . . . . . . . . . . . . . . . 20
10.2. Non-normative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22
Hardt, et al. [Page 2]
OpenID Attribute Exchange 1.1 - Draft 02 December 2009
1. Terminology
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 [RFC2119].
1.1. Definitions and Conventions
User: Also referred to as "End User" or "Subject". A person with a
digital identity who participates in OpenID-based identity
information exchanges using their client software, typically a web
browser.
Identity Data: A property of a digital identity in which the
Property Name and Property Value are represented as a name-value
pair.
Attribute The base of the information model used to describe the
Identity Data, for the purpose of exchanging it.
Persona: A subset of the user's identity data. A user can have
multiple personas as part of their identity. For example, a user
might have a work persona and a home persona.
OpenID Provider: Also called "OP" or "Server". An OpenID
Authentication server on which a Relying Party relies for an
assertion that the end user controls an Identifier.
Relying Party: Also called "RP" or "Consumer". A Web application
that wants proof that the end user controls an Identifier, and
requests identity data associated with the end user.
All OpenID Attribute Exchange messages MUST contain the following
extension namespace declaration, as specified in the Extensions
section of OpenID-Authentication-2.0:
openid.ns.<extension_alias>=http://openid.net/srv/ax/1.1
The actual extension namespace alias should be determined on a per-
message basis by the party composing the messages, in such a manner
as to avoid conflicts between multiple extensions. For the purposes
of this document, the extension namespace alias for the attribute
exchange service will be "ax".
Hardt, et al. [Page 3]
OpenID Attribute Exchange 1.1 - Draft 02 December 2009
2. Overview
The attribute exchange service extension is identified by the URI
"http://openid.net/srv/ax/1.1". This URI MUST be specified in the
extension namespace declaration.
An attribute is a unit of personal identity information that is
identified by a unique URI. It may refer to any kind of information.
A reference example of defining attribute types is provided by
[OpenID.axschema].
This service extension defines two message types for transferring
attributes: fetch (see Section 5) and store (see Section 6). Fetch
retrieves attribute information from an OpenID Provider, while store
saves or updates attribute information on the OpenID Provider. Both
messages originate from the Relying Party and are passed to the
OpenID Provider via the user agent as per the OpenID Authentication
protocol specification.
The request parameters detailed here MUST be sent using the
[OpenID.authentication-2.0] extension mechanism.
Hardt, et al. [Page 4]
OpenID Attribute Exchange 1.1 - Draft 02 December 2009
3. Information Model
The OpenID Attribute Exchange service extension provides a mechanism
for moving identity information between sites, as such its
information model is simple:
An attribute is associated with a Subject Identifier
An attribute has a type identifier and a value
An attribute type identifier is a URI
An attribute value can be any kind of data.
3.1. Subject Identifier
An identifier for a set of attributes. It MUST be a URI. The
subject identifier corresponds to the end-user identifier in the
authentication portion of the messages. In other words, the subject
of the identity attributes in the attribute exchange part of the
message is the same as the end-user in the authentication part. The
subject identifier is not included in the attribute exchange.
3.2. Attribute Type Identifier
An attribute type identifier MUST be a URI, which is used for
referring to property values.
If an attribute type identifier URI can be resolved then it MAY be
dereferenced to retrieve a description of the property. OpenID
Providers can use the metadata obtained through dereferencing new or
unknown attribute types to dynamically assist the user in providing
the attribute.
This provides for flexibility and extensibility. Flexibility in that
both URNs and URLs can be used to refer to property values.
Extensibility allows any individual site, or consortium of sites, to
define their own attribute types with agreements on the syntax and
semantics of their associated attribute values.
[OpenID.axschema] outlines an example method of defining new
attribute type URIs, and also provides a set of attribute types with
their associated metadata schema and data formats.
3.3. Attribute Value
A attribute value MUST be a UTF-8 [RFC3629] string. In order to
comply with the data formats defined by the underlying
Hardt, et al. [Page 5]
OpenID Attribute Exchange 1.1 - Draft 02 December 2009
[OpenID.authentication-2.0] protocol, attribute values MUST NOT
contain newlines (UCS codepoint 10, "\n").
OpenID Attribute Exchange can be used to transfer any kind of data.
If the data contains newlines, is not a UTF-8 string or it is so
desired by the parties transferring the data, the data MUST be
encoded to a UTF-8 string without newlines.
3.3.1. Attribute-Specific Encodings
Attribute-specific encodings can be defined using the attribute
metadata descriptions and may be applied by the protocol layer above
OpenID Attribute Exchange.
Optionally, attribute-specific encodings may use language tags
[OpenID.value-lang-1.0] for localization.
Hardt, et al. [Page 6]
OpenID Attribute Exchange 1.1 - Draft 02 December 2009
4. Discovery
Discovery of the attribute exchange service extension is achieved via
the mechanism described in [OpenID.authentication-2.0]. The
attribute exchange namespace "http://openid.net/srv/ax/1.1" SHOULD be
listed as an <xrd:Type> child element of the <xrd:Service> element in
the XRDS discovery document.
To advertise the attribute types supported, the Provider SHOULD list
the attribute Type URL as an <xrd:Type> child element of the <xrd:
Service> element in the XRDS discovery document.
Hardt, et al. [Page 7]
OpenID Attribute Exchange 1.1 - Draft 02 December 2009
5. Fetch Message
The fetch message is used to retrieve personal identity attributes
from an OpenID Provider.
5.1. Fetch Request Format
With the exception of "openid.ax.mode", all of the following request
fields are OPTIONAL, though at least one of "openid.ax.required" or
"openid.ax.if_available" MUST be specified in the request, and any
attribute alias present in a "openid.ax.required" or
"openid.ax.if_available" parameter MUST have an associated
"openid.ax.type.<alias>" parameter. The supported length for
attribute aliases MUST be at least 32 characters.
Multiple attribute aliases in the "openid.ax.required" and
"openid.ax.if_available" directives are separated with a comma, ",".
openid.ax.mode
REQUIRED. Value: "fetch_request".
openid.ax.type.<alias>
The value of this parameter specifies the type identifier URI
of a requested attribute. The <alias> will further be used to
identify the attribute being exchanged.
Attribute aliases MUST NOT contain newline and colon
characters, as specified in the Data Formats / Protocol
Messages section of [OpenID.authentication-2.0]; they also MUST
NOT contain commas (",") and periods (".").
openid.ax.required
Value: an attribute alias, or a list of aliases corresponding
to the URIs defined by "openid.ax.type.<alias>" parameters.
Multiple attribute aliases are separated with a comma, ",".
By requesting attributes using this field, a hint is sent to
the OP about the RP's requirements for offering certain
functionality and should be used by the OP to help the user
decide what attributes to release. RP's requirements should
not be enforced by the OP.
The RP should offer, out of band of attribute exchange, an
alternate method of collecting the attributes it needs, if they
weren't obtained via attribute exchange.
Hardt, et al. [Page 8]
OpenID Attribute Exchange 1.1 - Draft 02 December 2009
openid.ax.if_available
Value: an attribute alias, or a list of aliases corresponding
to the URIs defined by "openid.ax.type.<alias>" parameters.
Multiple attribute aliases are separated with a comma, ",".
Attributes requested using this field are deemed optional by
the RP; the RP should be able to complete the interaction with
the user even if values are not provided by the OP for the
optional attributes.
openid.ax.count.<alias>
The number of values for the specified attribute alias the
Relying Party wishes to receive from the OpenID Provider. If
present, the value MUST be greater than zero, or the special
value "unlimited" which signifies that the RP is requesting as
many values as the OP has for the attribute. If absent,
exactly one value is requested.
OpenID Providers MAY return less than or the exact number of
values speficied by this field for the associated attribute,
but MUST NOT return more than the number of requested values
for the attribute.
openid.ax.value.<alias>.<number>
Assigns a value to the attribute referred to as <alias>. The
<number> uniquely identifies the index of the value, ranging
from one to the value specified by "openid.ax.count.<alias>".
This parameter format MUST be used if "openid.ax.count.<alias>"
is sent, and the number of these parameters MUST be equal to
the value specified by "openid.ax.count.<alias>".
openid.ax.update_url
If present, the OpenID Provider may re-post the fetch response
message to the specified URL at some time after the initial
response has been sent, using a OpenID Authentication Positive
Assertion. If the OpenID Provider supports this feature it
MUST return the parameter as part of the fetch response
message. If it does not support this feature it may legally
ignore this parameter.
The value of the "openid.ax.update_url" field MUST be used as
value for "openid.return_to" field of the underlying OpenID
Authentication Positive Assertion of the fetch response update.
Hardt, et al. [Page 9]
OpenID Attribute Exchange 1.1 - Draft 02 December 2009
The "openid.ax.update_url" value MUST also match the realm
specified in the underlying OpenID message of the fetch
request, if a "openid.realm" field is present. The matching
rules are the ones specified in the "Realms" section of the
OpenID Authentication protocol.
This "unsolicited" response message would be generated in
response to an attribute information update, and would contain
the updated data. The OP should obtain the user's consent for
resending the updated data to the RPs, as with any OpenID
Positive Assertion.
The relying party may include transaction data encoded in the
URL such that it contains enough information to match the
attribute information to the identity subject. Additional
information may be encoded in the URL by the relying party as
necessary.
If an RP wishes to receive no further updates for an attribute,
it MAY return the HTTP 404 response code to the corresponding
"update_url". OPs MAY decide to stop sending updates after
encountering 404 response codes.
This example requests the required full name and gender information,
and the optional favourite dog and movie information. The Relying
Party is interested in up to three favorite movies associated with
the subject identifier.
openid.ns.ax=http://openid.net/srv/ax/1.1
openid.ax.mode=fetch_request
openid.ax.type.fname=http://example.com/schema/fullname
openid.ax.type.gender=http://example.com/schema/gender
openid.ax.type.fav_dog=http://example.com/schema/favourite_dog
openid.ax.type.fav_movie=http://example.com/schema/favourite_movie
openid.ax.count.fav_movie=3
openid.ax.required=fname,gender
openid.ax.if_available=fav_dog,fav_movie
openid.ax.update_url=http://idconsumer.com/update?transaction_id=a6b5c41
5.2. Fetch Response Format
The fetch response message supplies the information requested in the
fetch request. Each attribute is supplied with the assigned alias
prefixed by "openid.ax.value." as the lvalue and the attribute value
as the rvalue. Attribute types are also returned in the
"openid.ax.type.<alias>" parameters. The supported length for
Hardt, et al. [Page 10]
OpenID Attribute Exchange 1.1 - Draft 02 December 2009
attribute aliases MUST be at least 32 characters.
With the exception of "openid.ax.mode", all of the following request
fields are OPTIONAL, though any attribute value present in a
"openid.ax.value.<alias>" parameter MUST have an associated
"openid.ax.type.<alias>" parameter.
If a value was not supplied or available from the user, the
associated "openid.ax.value.<alias>" field SHOULD NOT be included by
the OP in the fetch response. An "openid.ax.count.<alias>" with a
value of "0" together with its corresponding "openid.ax.type.<alias>"
field MAY be included to explicitly state that no values are provided
for an attribute.
Validation of the received data should be performed out of band of
attribute exchange by the RP.
openid.ax.mode
REQUIRED. Value: "fetch_response".
openid.ax.type.<alias>
The value of this parameter specifies the type identifier URI
for an attribute in the fetch response. The <alias> will
further be used to identify the attribute being exchanged.
Attribute aliases MUST NOT contain newline and colon
characters, as specified in the Data Formats / Protocol
Messages section of [OpenID.authentication-2.0]; they also MUST
NOT contain commas (",") and periods (".").
openid.ax.count.<alias>
The number of values returned for the attribute referred to as
<alias>.
openid.ax.value.<alias>
Assigns a value to the attribute referred to as <alias>. This
parameter format MUST be used if "openid.ax.count.<alias>" is
not sent.
openid.ax.value.<alias>.<number>
Assigns a value to the attribute referred to as <alias>. This
parameter format MUST be used if "openid.ax.count.<alias>" is
sent and at least one value is provided for the associated
Hardt, et al. [Page 11]
OpenID Attribute Exchange 1.1 - Draft 02 December 2009
attribute.
The <number> uniquely identifies the index of the value,
ranging from one to the value specified by
"openid.ax.count.<alias>". The number of parameters MUST be
equal to the value specified by "openid.ax.count.<alias>". The
OP is not required to preserve the order of attribute values
among fetch responses.
openid.ax.update_url
Returns the "update_url" parameter specified in the request.
If the OpenID Provider receives an "update_url" parameter and
it intends to support the attribute update feature, it MUST
present the "update_url" parameter and value as part of the
fetch response message.
A fetch response message may also be sent to the "update_url"
specified in Section 5.1 in response to attribute value updates on
the OpenID Provider.
The response to the previous request example, in which the required
full name information, and the optional favourite dog information are
supplied. Even though three movie names were requested, the OP
supplied only two values.
openid.ns.ax=http://openid.net/srv/ax/1.1
openid.ax.mode=fetch_response
openid.ax.type.fname=http://example.com/schema/fullname
openid.ax.type.gender=http://example.com/schema/gender
openid.ax.type.fav_dog=http://example.com/schema/favourite_dog
openid.ax.type.fav_movie=http://example.com/schema/favourite_movie
openid.ax.value.fname=John Smith
openid.ax.count.gender=0
openid.ax.value.fav_dog=Spot
openid.ax.count.fav_movie=2
openid.ax.value.fav_movie.1=Movie1
openid.ax.value.fav_movie.2=Movie2
openid.ax.update_url=http://idconsumer.com/update?transaction_id=a6b5c41
Hardt, et al. [Page 12]
OpenID Attribute Exchange 1.1 - Draft 02 December 2009
6. Store Message
The store message is used to store personal identity information to
the OpenID Provider; it provides the means for an RP to transfer to
the OP attributes that the user may consider useful, such as by
providing them to other RPs. The supported length for attribute
aliases MUST be at least 32 characters.
The manner in which the OP processes the attribute payload in a store
request if out of scope of this document.
6.1. Store Request Format
With the exception of "openid.ax.mode", all of the following request
fields are OPTIONAL. Any alias referred to in a
"openid.ax.value.<alias>" or "openid.ax.value.<alias>.<number>"
parameter MUST have an associated "openid.ax.type.<alias>" parameter.
openid.ax.mode
REQUIRED. Value: "store_request".
openid.ax.type.<alias>
The value of this parameter specifies the type identifier URI
for an attribute in the sore request. The <alias> will further
be used to identify the attribute being exchanged.
Attribute aliases MUST NOT contain newline and colon
characters, as specified in the Data Formats / Protocol
Messages section of [OpenID.authentication-2.0]; they also MUST
NOT contain commas (",") and periods (".").
openid.ax.count.<alias>
The number of values sent for the attribute referred to as
<alias>. If present, it MUST be greater than zero.
openid.ax.value.<alias>
Assigns a value to the attribute referred to as <alias>. This
parameter format MUST be used if "openid.ax.count.<alias>" is
not sent.
Hardt, et al. [Page 13]
OpenID Attribute Exchange 1.1 - Draft 02 December 2009
openid.ax.value.<alias>.<number>
Assigns a value to the attribute referred to as <alias>. The
<number> uniquely identifies the index of the value, ranging
from one to the value specified by "openid.ax.count.<alias>".
This parameter format MUST be used if "openid.ax.count.<alias>"
is sent, and the number of these parameters MUST be equal to
the value specified by "openid.ax.count.<alias>".
openid.ns.ax=http://openid.net/srv/ax/1.1
openid.ax.mode=store_request
openid.ax.type.fname=http://example.com/schema/fullname
openid.ax.value.fname=Bob Smith
openid.ax.type.fav_movie=http://example.com/schema/favourite_movie
openid.ax.count.fav_movie=2
openid.ax.value.fav_movie.1=Movie1
openid.ax.value.fav_movie.2=Movie2
6.2. Store Response Format
6.2.1. Storage Success
The successful store operation is indicated by the mode parameter in
the store response:
openid.ax.mode
REQUIRED. Value: "store_response_success".
openid.ns.ax=http://openid.net/srv/ax/1.1
openid.ax.mode=store_response_success
6.2.2. Storage Failure
A storage failure response has the following format:
openid.ax.mode
REQUIRED. Value: "store_response_failure".
Hardt, et al. [Page 14]
OpenID Attribute Exchange 1.1 - Draft 02 December 2009
openid.ax.error
OPTIONAL. Parameter describing the error condition leading to
the failure response, intended to be presented to the user.
The locale of the message should match the locale of the HTTP
message.
openid.ns.ax=http://openid.net/srv/ax/1.1
openid.ax.mode=store_response_failure
openid.ax.error=General storage failure
Hardt, et al. [Page 15]
OpenID Attribute Exchange 1.1 - Draft 02 December 2009
7. Default Schemas
OpenID Attribute Exchange allows any attribute type identifier to be
defined and used. However, it is in the interest of the community to
have a small set of common identifiers. This section describes these
common identifies.
7.1. Mandatory Data Type
Followings are the identifiers that MUST be supported. Note that
this only means that the OpenID Provider must have these attributes
available. It mearly means that the OpenID Provider must understand
the request.
http://axschema.org/policy_url
A URL which the Consumer provides to give the End User a place
to read about the how the profile data will be used. The
Identity Provider SHOULD display this URL to the End User if it
is given.
http://axschema.org/namePerson/friendly
Any UTF-8 string that the End User wants to use as a nickname.
Equivalent to openid.sreg.nickname.
http://axschema.org/contact/email
The email address of the End User as specified in section 3.4.1
of [RFC2822]. Equivalent to openid.sreg.email.
http://axschema.org/namePerson
UTF-8 string free text representation of the End User's full
name. Equivalent to openid.sreg.fullname
http://axschema.org/birthDate
The End User's date of birth as YYYY-MM-DD. Any values whose
representation uses fewer than the specified number of digits
should be zero-padded. The length of this value MUST always be
10. If the End User user does not want to reveal any
particular component of this value, it MUST be set to zero.
For instance, if a End User wants to specify that his date of
birth is in 1980, but not the month or day, the value returned
SHALL be "1980-00-00". Equivalent to openid.sreg.dob
Hardt, et al. [Page 16]
OpenID Attribute Exchange 1.1 - Draft 02 December 2009
http://axschema.org/person/gender
The End User's gender, "M" for male, "F" for female.
Equivalent to openid.sreg.gender
http://axschema.org/contact/postalCode/home
UTF-8 string free text that SHOULD conform to the End User's
country's postal system. Equivalent to openid.sreg.postcode
http://axschema.org/contact/country/home
The End User's country of residence as specified by
ISO3166 [1]. Equivalent to openid.sreg.country
http://axschema.org/pref/language
End User's preferred language as specified by ISO639 [2].
Equivalent to openid.sreg.language
http://axschema.org/pref/timezone
ASCII string from TimeZone database [3]
For example, "Europe/Paris" or "America/Los_Angeles".
Equivalent to openid.sreg.timezone
Hardt, et al. [Page 17]
OpenID Attribute Exchange 1.1 - Draft 02 December 2009
8. Security Considerations
OpenID Attribute Exchange is an OpenID extension, and thus uses
OpenID Authentication request and response messages for exchanging
attributes.
See the "Security Considerations" section of
[OpenID.authentication-2.0].