Connection string resolver based on claim

[andrew-vdb]

Hi, i cant find any sample how to set connection string other than putting it on json config file is there a way to have connection string resolver based on tenant id that i put in jwt claim which get connection string stored in key vault?

[seantleonard]

Hi @andrew-vdb,

Sorry for the delay in getting back to you.

DAB doesn't support resolving a connection string based on JWT claims.

DAB supports:

• Reading the connection string from an environment variable as shown here: https://learn.microsoft.com/azure/data-api-builder/configuration-file#setting-environment-variables
• Usage of EntraID Managed Identities: https://learn.microsoft.com/azure/data-api-builder/database-connections#azure-sql-and-sql-server

[andrew-vdb]

@seantleonard how can we support multi tenant scenario? other than having tenantId column in each table?

[JerryNixon]

This is not how tenant should be implemented and we already support permissions on each entity. Having different connects for different types/claims would introduce different behaviors for the same entity without any indication to the user why it is behaving differently.