Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(release): new version #2091

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Nov 19, 2024

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/[email protected]

Minor Changes

  • 14673b1: Remove dependency on abort-controller library. Abort Controller has been supported on all platforms for quite some time already.

Patch Changes

  • 607659a: feat: fetch sd-jwt type metadata

@credo-ts/[email protected]

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 a clientId and clientSecret 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

@credo-ts/[email protected]

Patch Changes

@credo-ts/[email protected]

Patch Changes

@credo-ts/[email protected]

Patch Changes

@credo-ts/[email protected]

Patch Changes

@credo-ts/[email protected]

Patch Changes

@credo-ts/[email protected]

Patch Changes

@credo-ts/[email protected]

Patch Changes

@credo-ts/[email protected]

Patch Changes

@credo-ts/[email protected]

Patch Changes

@credo-ts/[email protected]

Patch Changes

@credo-ts/[email protected]

Patch Changes

@credo-ts/[email protected]

Patch Changes

@TimoGlastra TimoGlastra added the ci-test Trigger tests on a pull request label Nov 19, 2024
@github-actions github-actions bot force-pushed the changeset-release/main branch 12 times, most recently from b250ab1 to 784992d Compare November 26, 2024 22:30
@github-actions github-actions bot force-pushed the changeset-release/main branch 3 times, most recently from 48e6da2 to 6c7a545 Compare December 9, 2024 08:28
Signed-off-by: "github-actions[bot]" <"github-actions[bot]@users.noreply.github.com">
@github-actions github-actions bot force-pushed the changeset-release/main branch from 6c7a545 to 1ea3962 Compare December 17, 2024 15:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-test Trigger tests on a pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant