From 6f86597571e47ebf386829d9991730944418bf54 Mon Sep 17 00:00:00 2001 From: Gavin Jaeger-Freeborn Date: Tue, 21 Nov 2023 13:44:26 -0800 Subject: [PATCH] Corrected mistakes in README grammar Signed-off-by: Gavin Jaeger-Freeborn --- docs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/README.md b/docs/README.md index a5ee2da7..aef7b0e6 100644 --- a/docs/README.md +++ b/docs/README.md @@ -310,7 +310,7 @@ To quote from the OpenID Connect specification on [ID tokens](https://openid.net `sub : REQUIRED. Subject Identifier. A locally unique and never reassigned identifier within the Issuer for the End-User, which is intended to be consumed by the Client, e.g., 24400320 or AItOawmwtWwcT0k51BayewNvutrJUqsvl6qs7A4. It MUST NOT exceed 255 ASCII characters in length. The sub value is a case sensitive string` -When an OP is performing VC-AuthN, and the request has reached the point where the VC presentation has been generated and sent by the IW to the OP, the OP must now map contents of this VC presentation to an OpenID ID token. The question is then raised on what should populate this field. The three available are: +When an OP is performing VC-AuthN, and the request has reached the point where the VC presentation has been generated and sent by the IW to the OP, the OP must now map contents of this VC presentation to an OpenID ID token. The question is then raised on what should populate this field. The three options available are: 1. Nominate a disclosed attribute in the verifiable credential presentation that is used to populate the subject field. 2. Ephemeral generate an identifier for this field e.g a randomly generated GUID.