Activities of "jfistelmann"

As far as I know, there is no UI to configure if multitenancy is enabled. If you do not want multitenancy:

• Option A: set MultiTenancyConsts.IsEnabled to false and hide the SaaS menu through your menu contributor
• Option B: Delete everything related to multitenancy (along with related package references) and create a new migration

this add versions in dropdown of swagger ui i want two swagger ui on diff routes like

/admin/swagger /public/swagger

like that

can you try this? https://stackoverflow.com/a/77216365

can you try one thing (its a bit of effort though)

remove all localizations in appshell and in the main page (or whatever would come first). goal is that the app can load without needing the localization as they are loaded from the server.

that could be a starting point

Hey,

it seems like the issue is resolved. I close this question now.

feel free to reopen if i am wrong :)

that's simply due to some default css styling. you can just override it if it does not fit your prefences.

Thanks @jfistelmann. Can you please share some expample to create new middle layer

You just need to implement the interface and ensure it's added to the ServiceProvider. Are you experiencing any issues with that?

Thanks @jfistelmann.

Is it possible that i keep some placeholder in connection string and replace that placeholder in code with the actual value? if yes, what exactly i have to do?

With this here you can do anything you imagine :) by just implementing your own ConnectionStringResolver

You can refer to this: https://learn.microsoft.com/en-us/aspnet/core/security/key-vault-configuration?view=aspnetcore-7.0

or this:

https://stackoverflow.com/questions/68224000/using-keyvault-secrets-to-override-appsettings-in-azure-app-service-and-locally

just search google for something like azure key vault asp .net core appsettings.json and you'll find plenty of resources about that topic.

You may refer to this:

https://github.com/aspnetboilerplate/aspnetboilerplate/issues/3354#issuecomment-393793398

or this:

https://github.com/domaindrivendev/Swashbuckle.AspNetCore#generate-multiple-swagger-documents

you basically add some extra source to your OnApplicationInitialization with something like:

app.UseSwaggerUI(options =>
	{
		options.SwaggerEndpoint("/swagger/v1/swagger.json", "AbpProjectName API V1");
		options.SwaggerEndpoint("/swagger/v2/swagger.json", "AbpProjectName API V2");
	}

Are you really sure that you want to allow anonymous access to that?

what is the exact flow?

depending on your specific needs, you may want to create your own registration flow. Just a suggestion based on what you wrote:

Upon registration, you may create a form where you ask for the information you need to build a tenant. Create your own appservice for that, where registration alone can be done without the requirement of being logged in. When the user registrates -> you create a tenant with the information you need, based on what the user specified. First create a tenant, then create a new user in that tenant.

After that, you'll end up with a fresh tenant with a user inside. The rest can be done with an authorized user. You would not need to expose too many things.

In addition, you may want to store information about the registration state to allow for clean up scenarios.

In addition to the link you referred to: I think you can only change the permission needed, not disabling it entirely. You could try to add the [AllowAnonymous] attribute - but even if it works it would not be best practice to do that. Application Services handle specific needs. Your needs seem to be different from what the default provides. Therefore it's best to create your own implementation of Tenant/ User creation.