-
Notifications
You must be signed in to change notification settings - Fork 18
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
Release/v5.1.0 #446
Merged
Merged
Release/v5.1.0 #446
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
make_req -> makeReq, make_res -> makeRes
Feat/enc dec
Feat/generic messages
Tests and logic to make sure we honor the audience field if defined on request tokens. Slight refactor of the validateJWT function to improve readability.
397/issuance aud
The mocks / stubs needed an update. The goal was to have the tests pass after the merge.
… test one No API for injecting a custom resolver seems to be present. Will have to be addressed later.
Tests currently fail because of a breaking change in #399. Furthermore, a better API for passing in a custom resolover is needed
chore(d.ts): rebuilt d.ts files to match latest source
Fix token validation issues due to differing JSON key order The problem occurs when trying to reencode a JWT during validation. A key order must be enforced, and that used to be done by class transformer, which was removed in a previous commit This PR brings back class transformer usage for the interaction tokens themselves, to enforce an order. BUT for tokens which are not class based (i.e. custom ones like with Generic Tokens) the order must be enforced otherwise.
instanceOf assertions can be used again.
…pposed to IRegistry
…ests The change was pushed accidently.
fix(identityWallet.d.ts): rebuilt d.ts files
Passive resolve
Add to/from JSON conversion to Identity
Also includes tests for fromJSON / toJSON.
feat(identity): Class transformer annotations.
fix(sigs): ensure b64 signatures have no padding
Connectors are no longer configured directly. The DID Method abstraction is used, and should be defined elsewhere.
Docs/update readthedocs
Merge next branch
Bumps [elliptic](https://github.com/indutny/elliptic) from 6.4.1 to 6.5.3. - [Release notes](https://github.com/indutny/elliptic/releases) - [Commits](indutny/elliptic@v6.4.1...v6.5.3) Signed-off-by: dependabot[bot] <support@github.com>
Bumps [json-logic-js](https://github.com/jwadhams/json-logic-js) from 1.2.2 to 2.0.0. - [Release notes](https://github.com/jwadhams/json-logic-js/releases) - [Changelog](https://github.com/jwadhams/json-logic-js/blob/master/CHANGELOG.md) - [Commits](jwadhams/json-logic-js@1.2.2...2.0.0) Signed-off-by: dependabot[bot] <support@github.com>
…-6.5.3 chore(deps): bump elliptic from 6.4.1 to 6.5.3
…ic-js-2.0.0 chore(deps): bump json-logic-js from 1.2.2 to 2.0.0
Merged
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.
Identity
instance to / from JSON (Add to/from JSON conversion to Identity #436)Breaking changes
IRegistry
interface. Reworked DID Resolution and Registration abstractions (Integrate DIF Resolver #401, feat(registry): improve API for passing custom components to the registry + custom resolver #415, Feat/integrate registrar #416, Feat/remove iregistry #417)SoftwareKeyProvider
class, in favor of a Vaulted Key Provider implementation provided as a separate module. (Local reg vkp #424)