Skip to content

Commit

Permalink
Corrected mistakes in README grammar
Browse files Browse the repository at this point in the history
Signed-off-by: Gavin Jaeger-Freeborn <[email protected]>
  • Loading branch information
Gavinok committed Nov 21, 2023
1 parent 61ca4d1 commit 6f86597
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

0 comments on commit 6f86597

Please sign in to comment.