Skip to content

Commit

Permalink
Merge pull request #2328 from esune/fix/multitenancy-doc-update
Browse files Browse the repository at this point in the history
Added base wallet provisioning details to Multitenancy.md
  • Loading branch information
dbluhm authored Jul 20, 2023
2 parents 9aec175 + 58cc164 commit 621e4dd
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Multitenancy.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ Multi-tenancy in ACA-Py makes a distinction between a base wallet and sub wallet

The wallets used by the different tenants are called **sub wallets**. A sub wallet is almost identical to a wallet when multi-tenancy is disabled. This means that you can do everything with it that a single-tenant ACA-Py instance can also do.

The **base wallet** however, takes on a different role and has limited functionality. Its main function is to manage the sub wallets, which can be done using the [Multi-tenant Admin API](#multi-tenant-admin-api). It stores all settings and information about the different sub wallets and will route incoming messages to the corresponding sub wallets. See [Message Routing](#message-routing) for more details. All other features are disabled for the base wallet. This means it cannot issue credentials, present proof, or do any of the other actions sub wallets can do. This is to keep a clear hierarchical difference between base and sub wallets
The **base wallet** however, takes on a different role and has limited functionality. Its main function is to manage the sub wallets, which can be done using the [Multi-tenant Admin API](#multi-tenant-admin-api). It stores all settings and information about the different sub wallets and will route incoming messages to the corresponding sub wallets. See [Message Routing](#message-routing) for more details. All other features are disabled for the base wallet. This means it cannot issue credentials, present proof, or do any of the other actions sub wallets can do. This is to keep a clear hierarchical difference between base and sub wallets. For this reason, the base wallet should generally _not_ be provisioned using the `--wallet-seed` argument as not only it is not necessary for sub wallet management operations, but it will also require this DID to be correctly registered on the ledger for the service to start-up correctly.

![Multi-tenancy Architecture](/docs/assets/multitenancyDiagram.png)

Expand Down

0 comments on commit 621e4dd

Please sign in to comment.