Closed pradeepgururani closed 7 months ago
Hi @pradeepgururani,
Your option 2 is possible because you can create a custom method to replace the normal SetupMultiTenantSharding
setup. This allows you add add / change the code to the multi-tenant setup code. This was added in version 5 to allow you use different database types - see this section from the 'Setup a custom database, which has a link to an example SetupMultiTenantShardingCustomDb
custom method.
We are using AuthP v6.2. We are going to deploy our service as Azure App service along with Azure App Configuration.
While using Azure App Configuration there is feature of prefixing settings so that same Azure App Configuration instance can be used by different components.
I have created the prefix "WebApi". With this my
ConnectionStrings
section is no more accessible by the same name. With prefix it has to be accessed byWebApi:ConnectionStrings
.SetupMultiTenantSharding
method inAuthPermissions.AspNetCore.SetupExtensions
is trying to get the section byConnectionStrings
name and failing.If I may suggest, I would suggest either of following two options:
SetupMultiTenantSharding
call. If none is provided thenConnectionStrings
can be fallback option.