Skip to content

Commit 4e1f9e2

Browse files
authored
Merge branch 'master' into phrase-non-selectively-disclosable-claims-is-confusing
2 parents 8e960e6 + 7d53d54 commit 4e1f9e2

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

draft-ietf-oauth-selective-disclosure-jwt.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -642,6 +642,9 @@ The Key Binding JWT MUST be a JWT according to [@!RFC7519] and its payload MUST
642642
* `nonce`: REQUIRED. Ensures the freshness of the signature. The value type of this claim MUST be a string. How this value is obtained is up to the protocol used and out of scope of this specification.
643643
* `sd_hash`: REQUIRED. The base64url-encoded hash value over the Issuer-signed JWT and the selected Disclosures as defined below.
644644

645+
The general extensibility model of JWT means that additional claims and header parameters can be added to the Key Binding JWT.
646+
However, unless there is a compelling reason, this SHOULD be avoided, as it may harm interoperability and burden conceptual integrity.
647+
645648
### Binding to an SD-JWT {#integrity-protection-of-the-presentation}
646649

647650
The hash value in the `sd_hash` claim binds the KB-JWT to the specific SD-JWT.
@@ -1984,6 +1987,7 @@ data. The original JSON data is then used by the application. See
19841987
* Update PID example to align with the latest ARF and update the ARF reference
19851988
* Editorial updates from SECDIR IETF LC review
19861989
* Terminology improvements around the phrase "non-selectively disclosable claims" and "not disclosable"
1990+
* Suggest against using extra claims/headers in the KB-JWT without a good reason
19871991

19881992
-17
19891993

0 commit comments

Comments
 (0)