Skip to content

group credential_response_encryption parameters in the Issuer Metadata#153

Merged
Sakurann merged 9 commits into
mainfrom
152-merge-credential-response-encryption-issuer-metadata
Jan 4, 2024
Merged

group credential_response_encryption parameters in the Issuer Metadata#153
Sakurann merged 9 commits into
mainfrom
152-merge-credential-response-encryption-issuer-metadata

Conversation

@paulbastian

Copy link
Copy Markdown
Contributor

Closes #152

I want to note that we don't have an example for the usage of this parameter in the issuer metadata yet.
Should we add an example?

@paulbastian paulbastian linked an issue Dec 14, 2023 that may be closed by this pull request
Comment thread openid-4-verifiable-credential-issuance-1_0.md Outdated
@peppelinux

Copy link
Copy Markdown
Member

@paulbastian yes an example would improve this PR

Comment thread openid-4-verifiable-credential-issuance-1_0.md Outdated

@Sakurann Sakurann left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i don't think the current description is sufficient, and would like to see it expanded. having an example would be nice, but not mandatory to merge this PR IMO

Co-authored-by: Kristina <52878547+Sakurann@users.noreply.github.com>
Comment thread openid-4-verifiable-credential-issuance-1_0.md Outdated
Comment thread openid-4-verifiable-credential-issuance-1_0.md Outdated

@bc-pi bc-pi left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am in favor of grouping these parameters but I think the case of a credential issuer being able to encrypt a credential response and publishing the supported alg/enc values while not requiring the credential response be encrypted should be retained.

@awoie awoie left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally looks good. I made some comments. Please accept them. I'm ok if jwk_values_supported does not get accepted but I think it might be useful. Especially with brainpool etc.

Comment thread openid-4-verifiable-credential-issuance-1_0.md Outdated
Comment thread openid-4-verifiable-credential-issuance-1_0.md Outdated
Comment thread openid-4-verifiable-credential-issuance-1_0.md Outdated
Comment thread examples/credential_issuer_metadata_jwt_vc_json.json Outdated
@Sakurann

Copy link
Copy Markdown
Collaborator

@bc-pi I don't see anything in the PR that mandates the encryption when these metadata parameters are present.

@bc-pi

bc-pi commented Dec 20, 2023

Copy link
Copy Markdown
Member

@bc-pi I don't see anything in the PR that mandates the encryption when these metadata parameters are present.

These bits of text, for example, that use the word "require" read that way to me.

The Credential Issuer MAY require encrypted responses by including credential_response_encryption object in the Credential Issuer Metadata.

credential_response_encryption: OPTIONAL. Object containing information whether the Credential Issuer requires encryption of the Credential and Batch Credential Response on top of TLS.

Comment thread openid-4-verifiable-credential-issuance-1_0.md Outdated
@Sakurann

Copy link
Copy Markdown
Collaborator

@bc-pi I see your point - I made two suggestions to address them. changing "requires" to "supports" made a difference.

@Sakurann Sakurann left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

assuming something like my suggested changes will be accepted

@Sakurann Sakurann added this to the ID-1 milestone Dec 21, 2023
paulbastian and others added 2 commits December 21, 2023 15:20
Co-authored-by: Kristina <52878547+Sakurann@users.noreply.github.com>
Co-authored-by: Kristina <52878547+Sakurann@users.noreply.github.com>
Comment thread openid-4-verifiable-credential-issuance-1_0.md Outdated
@Sakurann

Copy link
Copy Markdown
Collaborator

to clarify, the existence of the encryption related parameters signal that issuer supports the encryption, and the existence of the boolean signals that the issuer requires encryption

@selfissued

Copy link
Copy Markdown
Member

I plan to review this after the disposition of the set of suggested changes is known.

@selfissued selfissued self-requested a review December 31, 2023 19:37
@paulbastian

Copy link
Copy Markdown
Contributor Author

@bc-pi @selfissued please review

Comment thread examples/credential_issuer_metadata_jwt_vc_json.json Outdated
Co-authored-by: Joseph Heenan <joseph@heenan.me.uk>
@paulbastian paulbastian requested a review from jogu January 4, 2024 14:55
* `credential_response_encryption`: OPTIONAL. Object containing information whether the Credential Issuer supports encryption of the Credential and Batch Credential Response on top of TLS.
* `alg_values_supported`: REQUIRED. Array containing a list of the JWE [@!RFC7516] encryption algorithms (`alg` values) [@!RFC7518] supported by the Credential and Batch Credential Endpoint to encode the Credential or Batch Credential Response in a JWT [@!RFC7519].
* `enc_values_supported`: REQUIRED. Array containing a list of the JWE [@!RFC7516] encryption algorithms (`enc` values) [@!RFC7518] supported by the Credential and Batch Credential Endpoint to encode the Credential or Batch Credential Response in a JWT [@!RFC7519].
* `encryption_required`: REQUIRED. Boolean value specifying whether the Credential Issuer requires the additional encryption on top of TLS for the Credential Response. If the value is `true`, the Credential Issuer requires the encryption for every Credential Response and therefore the Wallet MUST provide encryption keys in the Credential Request. If the value is `false`, the Wallet MAY chose whether it provides encryption keys or not.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it logically makes more sense to bring this parameter before enc_values_supported and alg_values_supported when describing?

@Sakurann Sakurann requested a review from bc-pi January 4, 2024 14:57
@Sakurann

Sakurann commented Jan 4, 2024

Copy link
Copy Markdown
Collaborator

DCP WG call - Jan-04-2024 agreed to merge once Brian's approval is in. agreed encryption_required is a good trade-off as a parameter name.

@bc-pi

bc-pi commented Jan 4, 2024

Copy link
Copy Markdown
Member

Brian's approval is in

@Sakurann Sakurann merged commit d8724f3 into main Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Merge Credential Response encryption Issuer Metadata

7 participants