Wallet Addresses should become tenanted as per the Multi-Tenancy design, and will be logically separated in the backend database by a tenantId row that serves as a foreign key on the tenants table.
[ ] Add tenantId row to walletAddresses table that is required and maps to an id on the tenants table.
[ ] Add tenantId to database queries on wallet addresses
[ ] Acquire tenantId from request headers on wallet address GraphQL requests and pass them into wallet address service logic.
[ ] Include tenantId in base URL of authServer and resourceServer fields of the current wallet address response.
Wallet Addresses should become tenanted as per the Multi-Tenancy design, and will be logically separated in the
backend
database by atenantId
row that serves as a foreign key on the tenants table.tenantId
row towalletAddresses
table that is required and maps to an id on thetenants
table.tenantId
to database queries on wallet addressestenantId
from request headers on wallet address GraphQL requests and pass them into wallet address service logic.tenantId
in base URL ofauthServer
andresourceServer
fields of the current wallet address response.Prerequisites