Askar support for MultiWalletSingleTable migration #26
Comments
|
Superseded by openwallet-foundation#7 |
dbluhm
pushed a commit
that referenced
this issue
May 2, 2024
Bumps [aiohttp](https://github.com/aio-libs/aiohttp) from 3.8.5 to 3.9.2. - [Release notes](https://github.com/aio-libs/aiohttp/releases) - [Changelog](https://github.com/aio-libs/aiohttp/blob/master/CHANGES.rst) - [Commits](aio-libs/aiohttp@v3.8.5...v3.9.2) --- updated-dependencies: - dependency-name: aiohttp dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue on the Aries-Askar repository describes the blocker for implementing a one-to-one migration of the Indy-SDK
MultiWalletSingleTablesetup to Askar. For lack of an exact mapping, we have implemented two options for migrating Indy-SDK wallets usingMultiWalletSingleTablemode depending on whether the agents are standard or multi-tenanted. See documentation for more details on migrating theMultiWalletSingleTablesetup to profiles or separate stores on the Askar side.cc @dbluhm @burdettadam
The text was updated successfully, but these errors were encountered: