Ok, so the refactoring will be in a future release?
Can you clarify on what source code to copy and to where/how?
Hi, This setting almost satisfies our requirements. I'm assuming this setting applies to both Registering and Logging In, correct?. What we actually need is for the system to always require Email or Phone verification in order to register, and then have these settings to be able to be turned on and off for just signing in.
Any guidance as to how to accomplish that would be greatly appreciated.
Hi Spospisil, I had ran into the exact same problem, but was forced to implement IMultiTenancy even with separate databases for each tenant. I am using version 4.4.3 though.
Are you still running into this issue?
and did you implement the
IMultiTenantinterface for your new entities. https://docs.abp.io/en/abp/latest/Multi-Tenancy#imultitenant
Thank you albert. Implementing IMultiTenant resolved the issue. We had thought that since every tenant will have it's own separate tenant database, a TenantId column was not needed and therefore IMultiTenant would not need to be implemented.
For anyone running into this issue... the following link provided the resolution. Websockets in your Azure App Service need to be turned on
https://stackoverflow.com/questions/47652865/azure-webapps-404-error