hi
We have reset your developer machine.
You can try again.
Thanks
hi
The Shared strategy works as "authenticate first, select tenant after" — at the point the login page is rendered, there's no tenant context yet, so the system doesn't know which tenant's IdP credentials to use. That's why external IdP configuration (along with other security settings like 2FA, lockout, password policies) is handled at the Host level in this mode.
For scenarios where each customer needs their own Azure AD app registration or similar per-tenant IdP setup, the Isolated strategy would be a better fit — it resolves the tenant before authentication, so tenant-specific IdP settings can be loaded properly.
Thanks.
hi
We will check your license.
Thanks.
hi
You can override the CreateAsync method and remove the DataSeeder.SeedAsync code.
https://abp.io/docs/latest/framework/architecture/modularity/extending/customizing-application-modules-overriding-services
Thanks.
hi
You can try changing an email in https://account.abp.io/Account/Manage, and then send an email. How about that?
hi
You can send an email to info@abp.io
Thanks.
hi
Volo.Abp.TenantManagement is an open-source module. You have a commercial license; you should use Volo.Saas.Host.Application
But I will check the open source side as well.
Thanks.
Hi, is the code you shared from the ABP module, or is it your own custom code?
Thanks.