New release #63
Merged
New release #63
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…Also moved endpoints to functions, so solutions can include their own set of endpoints
nklomp
added a commit
that referenced
this pull request
Nov 3, 2023
nklomp
added a commit
that referenced
this pull request
Feb 16, 2024
fix: opts passed to getCredentialOfferEndpoint() chore: add Sphereon E2E test as well as code from #63 to test potential issue chore: remove duplicate test feat: add sd-jwt support feat: Add optional QR code generation docs: Update README.md for code discrepancies docs: Update README.md for DIDDocument feat: update sd-jwt profile from oid4vci feat: Add initial support for creating a client without credential offer fix: Add back jwt_vc format support for older versions feat: EBSI compatibility chore: test fix chore: issuer type fix chore: test fixes feat: Add deferred credential support * chore: update lock file * fix(sd-jwt): cnf instead of kid * chore: missed to remove actual es-line line chore: missed to remove actual es-line line * Update VcIssuer.ts * chore: update ssi-types to 0.18 Signed-off-by: Timo Glastra <[email protected]> * feat: ldp issuance Signed-off-by: Timo Glastra <[email protected]> * feat: Support sd-jwt 0.2.0 library * chore: update lock file * chore: update lock file * fix: add sd-jwt to issuer callback Signed-off-by: Timo Glastra <[email protected]> * Update packages/client/lib/CredentialRequestClient.ts * feat: PKCE support improvements. Now you can omit PKCE code verifier/challenge params for authorization code flows. They will be generated automatically. Be aware the API of the createAuthorizationUrl method changed as a result. It now has a PKCE param * feat: PAR improvements The createAuthorizationRequestUrl now automatically handles PAR, instead of having a separate method. There is a new Param to determine whether PAR should be used automatically, never be used, or whether it is required. The latter is also set when the AS has a PAR required metadata value. As a result the createAuthorizationUrl method now is asynchronous * chore: Use calculated codeVerifier when acquiring the access token * feat: Allow to create an authorization request URL when initiating the OID4VCI client Including support for PAR, when initializing the client from an issuer, or when using a credential offer that supports an authorization code flow. Improvements to create authorization request URL in general. Please be aware that the API for this method has changed * chore: fix test * feat: Add support to get a client id from an offer, and from state JWTs. EBSI for instance is using this * chore: fix clientId from offer * chore: fix clientId from offer * chore: fix clientId from offer * chore: fix clientId from offer * chore: disable EBSI tests, because of timeout * chore: investigate req opts not properly filled * chore: investigate req opts not properly filled * chore: investigate req opts not properly filled * feature: Add support to pass in an authorization response to the access token request. The authorization response can either be a JSON or URI * feat: Make sure redirect_uri is the same for authorization and token endpoint when used and made redirect_uri optional. The redirect_uri is automatically passed to the token request in case one was used for authorization * fix: Fix uri to json conversion when no required params are provided * fix: Do not set a default redirect_uri, unless no authorization request options are set at all * fix: the client_id used in the auth request was not taken into account when requesting access token * fix: Do not sort credential types, as issuers might rely on their order * chore: Make sure the body debug log does not confuse people, by not JSON stringifying when the body is already a string. Was only used in logging, not in the actual payload * chore: Add a default clientId * fix: disable awesome-qr in rn Signed-off-by: Timo Glastra <[email protected]> * chore: v11 context fix * chore: v11 context fix * chore: allow to set clientId * chore: fix imports * feat: Allow to set the clientId at a later point on the VCI client * chore: Cleanup * fix: Do not set default client_id * feat: added state recovery * chore: move OpenID4VCIClient fields into state object * chore: constructor fixes * chore: test fixes * chore: addressing pr comments * chore: code cleanup * chore: code cleanup * chore: Disable E2E test because of infra issue * chore: PAR fixes --------- Signed-off-by: Timo Glastra <[email protected]> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Fendy Putra <[email protected]> Co-authored-by: Timo Glastra <[email protected]> Co-authored-by: Ron Kreutzer <[email protected]> Co-authored-by: A.G.J. Cate <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.