Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@credo-ts/openid4vc@0.6.0
Minor Changes
17ec6b8: feat(openid4vc): oid4vci authorization code flow, presentation during issuance and batch issuance.
This is a big change to OpenID4VCI in Credo, with the neccsary breaking changes since we first added it to the framework. Over time the spec has changed significantly, but also our understanding of the standards and protocols.
Authorization Code Flow
Credo now supports the authorization code flow, for both issuer and holder. An issuer can configure multiple authorization servers, and work with external authorization servers as well. The integration is based on OAuth2, with several extension specifications, mainly the OAuth2 JWT Access Token Profile, as well as Token Introspection (for opaque access tokens). Verification works out of the box, as longs as the authorization server has a
jwks_uri
configured. For Token Introspection it's also required to provide aclientId
andclientSecret
in the authorization server config.To use an external authorization server, the authorization server MUST include the
issuer_state
parameter from the credential offer in the access token. Otherwise it's not possible for Credo to correlate the authorization session to the offer session.The demo-openid contains an example with external authorization server, which can be used as reference. The Credo authorization server supports DPoP and PKCE.
Batch Issuance
The credential request to credential mapper has been updated to support multiple proofs, and also multiple credential instances. The client can now also handle batch issuance.
Presentation During Issuance
The presenation during issuance allows to request presentation using OID4VP before granting authorization for issuance of one or more credentials. This flow is automatically handled by the
resolveAuthorizationRequest
method on the oid4vci holder service.Patch Changes
vp_formats
in client_metadata instead ofvp_formats supported
(Verifier uses parametervp_formats_supported
instead ofvp_formats
#2089)@credo-ts/action-menu@0.6.0
Patch Changes
@credo-ts/anoncreds@0.6.0
Patch Changes
@credo-ts/askar@0.6.0
Patch Changes
@credo-ts/bbs-signatures@0.6.0
Patch Changes
@credo-ts/cheqd@0.6.0
Patch Changes
@credo-ts/core@0.6.0
Patch Changes
@credo-ts/drpc@0.6.0
Patch Changes
@credo-ts/indy-sdk-to-askar-migration@0.6.0
Patch Changes
@credo-ts/indy-vdr@0.6.0
Patch Changes
@credo-ts/node@0.6.0
Patch Changes
@credo-ts/question-answer@0.6.0
Patch Changes
@credo-ts/react-native@0.6.0
Patch Changes
@credo-ts/tenants@0.6.0
Patch Changes