Skip to content
This repository has been archived by the owner on Sep 11, 2024. It is now read-only.

Migrate to new, separate APIs for cross-signing and secret storage #5149

Merged
merged 4 commits into from
Aug 28, 2020

Conversation

jryans
Copy link
Collaborator

@jryans jryans commented Aug 27, 2020

This migrates to the new JS SDK APIs, which now use separate paths for
cross-signing and secret storage setup. There should be no functional change
here.

Part of element-hq/element-web#13895
Depends on matrix-org/matrix-js-sdk#1450

jryans added 3 commits August 25, 2020 13:20
This visits all places that were checking for cross-siging readiness and adapts
them to also check for secret storage readiness if needed.

Part of element-hq/element-web#13895
This migrates to the new JS SDK APIs, which now use separate paths for
cross-signing and secret storage setup. There should be no functional change
here.

Part of element-hq/element-web#13895
The bare word `force` has bothered me, so this adds a tiny amount more meaning.
This supplies a cache callback to the JS SDK so that we can be notified if a new
storage key is created e.g. by resetting secret storage. This allows it to be
supplied automatically in case it's needed in the same user operation, as it is
when resetting both secret storage and cross-signing together.
@jryans jryans merged commit e2acec6 into develop Aug 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants