From: regext <[email protected]> On Behalf Of Mario Loffredo
Sent: Wednesday, February 9, 2022 1:07 PM
To: Hollenbeck, Scott <[email protected]>;
[email protected]
Subject: [EXTERNAL] Re: [regext] I-D Action:
draft-ietf-regext-rdap-openid-10.txt
Caution: This email originated from outside the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
Hi Scott,
a first feedback is about the "notice" object used in the examples.
It seems to me that the values of the "description" member are not compliant
with what is stated in section 4.3 of RFC 9083:
an array of strings named "description" for the purposes of conveying any
descriptive text
As a general rule, I think we should not use jagged arrays. They are harmful
for clients because they cannot be deserialized straightforwardly.
This is also one of the reasons why jCard is considered inefficient.
So I would opt for defining a new "session response" based on an unambiguous
data model.
[SAH] Thanks for catching that, Mario. What about something like this (might
not be valid json…)?
{
"notices": {
"title": "Login Result",
"description": [
"Login succeeded", "user.idp.example"
],
"lang": "en-US"
},
"userInfo": {
"claims": {
"iss": "https://accounts.someprovider.com";,
"azp": "729559086898-onapsvnhf2og.apps.someprovider.com",
"aud": "729559086898-onapsvnhf2og.apps.someprovider.com",
"sub": "103892603076825016132",
"email": "[email protected]",
"email_verified": true,
"at_hash": "es5maY5y9jBAWCBMhLokAQ",
"nonce": "dcb29f97c836726ddc074f76fbc21bfd",
"name": "User Person",
"picture": "https://lh3.someprovider.com/a-/AOh14=s96-c";,
"given_name": "User",
"family_name": "Person",
"locale": "en",
"iat": 1644239971,
"exp": 1644243571,
"purpose": "domainNameControl",
"dnt": false
},
"session": {
"Expires in (seconds)": 3599
}
},
}
_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext
