hyperledger / aries-acapy-tools Goto Github PK

After this issue and PR were addressed in Aries Agent Test Harness, I looked for other instances of the use of “-slim” and found this one. Should be updated to be more specific — e.g. to use bullseye.

Dear team.

Currently were holders of several wallets in indy format and we are using mwst with independent agents, and we want to move to a multitenant agent, as we know the keys of all wallets, is there any way to convert them to multi tenant?

As askar doesn't support mwst, using mwst-as-stores generates a lot of databases which require a lot more space than the original.

Thanks in advance.

I ran a test with a small OrgBook wallet (~1800 credentials):

$ askar-upgrade --strategy dbpw --uri postgres://postgres:mysecretpassword@localhost:5433/icat_agent_wallet --wallet-name icat_agent_wallet --wallet-key key
Opening wallet with Askar...
Updating keys... 6 updated
Updating master secret(s)... 1 updated
Updating DIDs... 4 updated
Updating stored schemas... 0 updated
Updating stored credential definitions... 0 updated
Updating stored revocation registry definitions... 0 updated
Updating stored revocation registry keys... 0 updated
Updating stored revocation registry states... 0 updated
Updating stored revocation registry info... 0 updated
Updating stored credentials... 1893 updated
Closing wallet

There were two steps that took "awhile" - it took a few seconds (maybe 10 seconds?) before the Opening wallet with Askar ... message came up, and the Updating stored credentials step obviously took some amount of time.

Would be nice to see some "progress" messages to know what is happening during these intervals (or anywhere that might take longer to run)

The use “wallet” in this repo is likely confusing. How about we rename it now while it is new?

Other options:

• aries-acapy-indy-to-askar-migration
• aries-acapy-askar-migration

@dbluhm @cjhowland @andrewwhitehead — thoughts?

Looks like PRs in this repo can be merged without an approval.

Looking at the current state of the implementation in this repo, it seems that the pgsql functionality is still WIP.
Is there a plan to update and implement the missing chunk of the functionality so that postgres based wallets can also be upgraded from indy to askar?

This issue on the Aries-Askar repository describes the blocker for implementing a one-to-one migration of the Indy-SDK MultiWalletSingleTable setup to Askar. For lack of an exact mapping, we have implemented two options for migrating Indy-SDK wallets using MultiWalletSingleTable mode depending on whether the agents are standard or multi-tenanted. See documentation for more details on migrating the MultiWalletSingleTable setup to profiles or separate stores on the Askar side.

cc @dbluhm @burdettadam @cjhowland

Currently mwst-as-stores strategy get the keys as a json structure on the command line, this is not a good approach for big structures, also, having the keys in the shell history is not a good idea.

Please add a parameter like --wallet-keys-file to allow getting the keys from a file.

Does the provided script function as expected when targeting attached sqlite wallet?

Attempting to execute the following: python ./bin/askar-upgrade.py ./faber.agent326531.db Faber.Agent372766
results in:

ACA-Py will eventually move a feature that is currently experimental to ready-for-use status: AnonCreds RS support. With this change, the migration strategy used in the wallet upgrade tool will require tweaks to migrate an Indy wallet to the new AnonCreds format.

Is this something we should worry about? It should be technically possible to upgrade using this tool as is and then use the upgrade endpoint @jamshale is working on in hyperledger/aries-cloudagent-python#2922.

cc: @swcurran