You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge pull request #91 from Sphereon-Opensource/develop
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 <timo@animo.id>
* feat: ldp issuance
Signed-off-by: Timo Glastra <timo@animo.id>
* 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 <timo@animo.id>
* 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 <timo@animo.id>
* 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 <timo@animo.id>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Fendy Putra <fendy.putra@meeco.me>
Co-authored-by: Timo Glastra <timo@animo.id>
Co-authored-by: Ron Kreutzer <ron@rktechworks.com>
Co-authored-by: A.G.J. Cate <brummos@gmail.com>
The OID4VCI Server metadata contains information about token endpoints, credential endpoints, as well as additional
74
74
information about supported Credentials, and their cryptographic suites and formats.
75
-
The code above already retrieved the metadata, so it will not be fetched again. If you however not used
75
+
The code above already retrieved the metadata, so it will not be fetched again, and this method places the data in another variable. If you however have not used
76
76
the `retrieveServerMetadata` option, you can use this method to fetch it from the Issuer:
0 commit comments