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.
  • See feat(backend): wallet address response with tenant id #2986 for existing implementation on old feature branch.
  • eg: { ..., resourceServer: OPEN_PAYMENTS_URL/tenantId/ }

Prerequisites

• [Multi-Tenant] Use http-signatures to determine tenant identity during requests #2928

Pull Request

#3152