search

oauth-wg / oauth-selective-disclosure-jwt

https://datatracker.ietf.org/doc/draft-ietf-oauth-selective-disclosure-jwt/
Other
54 stars 27 forks source link

Give "JSON document of the SD-JWT processing and verification algorithm" a name #443

Open awoie opened 4 days ago

awoie commented 4 days ago

We had the discussion in SD-JWT VC how to refer to the dehydrated (or maybe hydrated) result (Issuer-signed JWT payload) of the processing and verification algorithm. It would help if we could give it a name to allow us to be more precise in other specs that are building on top of SD-JWT.

The discussion occurred when adding the Schema for SD-JWT VCs that uses that result of the SD-JWT processing section to match the JSON schema against: https://github.com/oauth-wg/oauth-sd-jwt-vc/pull/231/files#diff-e750c0958ca10e395b4d3b77bb5aafccc668b4a1a50675dda79a8d90b39a2468R714-R715

We also have another issue that asks for an example of the result as well which would benefit from giving it a defined name: https://github.com/oauth-wg/oauth-sd-jwt-vc/issues/194

awoie commented 4 days ago

Perhaps you can also confirm that this result in fact contains things like iss, cnf, exp etc., and would only remove _sd, _sd_alg, ....

bc-pi commented 4 days ago

I was typing the following over in #442 when it closed out from under me in favor of this issue.

By Give " a name here what @awoie means is that it'd be useful to have a name to refer to what we call the "processed SD-JWT payload" that's "passed to the application" here and is really the JSON after verification and processing and replacing _sd and ... occurrences with the real values.