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
In multitenant mode, when doing the anoncreds upgrade it was decided to force new wallets to be the same type as the admin wallet. The down side of this is it forces the controller to upgrade the admin wallet when it isn't needed. The admin wallet is indifferent to the subwallet wallet type. If the admin wallet is upgraded, now the controller can't create askar(indy) type wallets anymore.
I think we should remove this restriction when creating subwallets.
The text was updated successfully, but these errors were encountered:
As mentioned in the above link, I think that a restriction only makes sense if it impacts functionality.
Assume here the admin has an askar wallet. Restricting wallet creation to not allow askar-anoncreds, but allowing them to create askar and then separately upgrade to askar-anoncreds -- if that's the case, it feels like the initial restriction is unnecessary.
The only reasons I can think of for such a restriction is if something doesn't work properly, or if there's a change coming in a next release that'll impact it. If it just creates a hurdle of creating and then upgrading separately, that doesn't make sense imo
In multitenant mode, when doing the anoncreds upgrade it was decided to force new wallets to be the same type as the admin wallet. The down side of this is it forces the controller to upgrade the admin wallet when it isn't needed. The admin wallet is indifferent to the subwallet wallet type. If the admin wallet is upgraded, now the controller can't create askar(indy) type wallets anymore.
I think we should remove this restriction when creating subwallets.
The text was updated successfully, but these errors were encountered: