Skip to content

Conversation

@awoie
Copy link
Contributor

@awoie awoie commented Feb 7, 2025

This PR does:

  • make type and values for credential_signing_alg_values_supported format specific
  • change algorithm identifiers for credential_signing_alg_values_supported to COSE algorithm values for mdocs
  • add credential_signing_crv_values_supported to mdoc format because of polymorphic COSE algorithm identifiers

Fixes #354 and fixes #303

Note that this is also how it is used in 23220-3 atm.

awoie added 2 commits February 7, 2025 14:45
… format specific and introduced credential_signing_crv_values_supported for mdocs
@awoie awoie changed the title fix: made type and values for credential_signing_alg_values_supported… make credential_signing_alg_values_supported type and values format specific Feb 7, 2025
Copy link
Collaborator

@Sakurann Sakurann left a comment

Choose a reason for hiding this comment

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

i think this is an improvement - thank you!

Copy link
Contributor

@davidz25 davidz25 left a comment

Choose a reason for hiding this comment

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

I think this is an improvement, thanks.

(As an aside, would be nice if we could depend on fully specified algorithms - that way we wouldn't need e.g. credential_signing_crv_values_supported. But I don't think we can add that dependency.)

@paulbastian
Copy link
Contributor

agree with David, we should use fully-specified algorithms right away to make things easier. It's close to final and apparently its not a too big of a problem to reference non-final specs.

@tplooker
Copy link
Contributor

tplooker commented Apr 27, 2025

(As an aside, would be nice if we could depend on fully specified algorithms - that way we wouldn't need e.g. credential_signing_crv_values_supported. But I don't think we can add that dependency.)

If we did this too though we wouldn't be able to point at the COSE IANA registry like we are because the polymorphic algorithm identifiers are already registered there. That would then limit us in being cryptographically agile in future as new PQ algs get finalised.

Hopefully fully specified algs just become more common use in future thus making this metadata element redundant.


* `doctype`: REQUIRED. String identifying the Credential type, as defined in [@!ISO.18013-5].
* `claims`: OPTIONAL. An array of claims description objects as defined in (#claims-description-issuer-metadata).
* `credential_signing_crv_values_supported`: OPTIONAL. Array of cryptographic curve identifiers that the Issuer uses with one of the algorithms listed in `credential_signing_alg_values_supported` to sign the issued Credential. Curve identifier types and values used are numeric values and SHOULD be one of those COSE eliptic curve values defined in [@IANA.COSE]. Note that `credential_signing_crv_values_supported` MAY be used if one of the algorithms in `credential_signing_alg_values_supported` supports multiple curves.
Copy link
Collaborator

Choose a reason for hiding this comment

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

this needs to be changed to align with openid/OpenID4VP#553

Copy link
Contributor

Choose a reason for hiding this comment

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

How does this relate to #495 ?

Copy link
Collaborator

@Sakurann Sakurann left a comment

Choose a reason for hiding this comment

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

needs to be changed to align with openid/OpenID4VP#553

@Sakurann Sakurann added this to the Final 1.0 milestone May 5, 2025
@awoie
Copy link
Contributor Author

awoie commented May 12, 2025

Closing this PR in favor of #495

@awoie awoie closed this May 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

6 participants