User is IMayHaveTenant.
When is IMayHaveTenant enabled?
IMayHaveTenant is always enabled unless you explicitly disable it.
Order by Id for GetUserPermissionsForEdit in UserAppService.
- Permissions = ObjectMapper.Map<List<FlatPermissionDto>>(permissions).OrderBy(p => p.DisplayName).ToList(),
+ Permissions = ObjectMapper.Map<List<FlatPermissionDto>>(permissions).OrderBy(p => p.Id).ToList(),
That causes problems if event handlers make additional changes in database. It was the original way: aspnetboilerplate/aspnetboilerplate#1695
Mark the method as [UnitOfWork] or begin a unit of work using IUnitOfWorkManager.
https://aspnetboilerplate.com/Pages/Documents/Unit-Of-Work
Duplicate of aspnetboilerplate/aspnetboilerplate#4425
Fixed in aspnetboilerplate/aspnetboilerplate#4428. Will be released in next version.
ASP<span></span>.NET MVC 5? Entity Framework 6?
Do you have the following line in service-proxy.module.ts?
@NgModule({
providers: [
// ...
ApiServiceProxies.StripePaymentServiceProxy, // This line
// ...
]
})
semantics, etymology and a tendency to dictate how one uses available tools to bring attention to a point whilst not adhering to your particular rules does not impress.
It isn't my rule, but a convention among developers. Also, code blocks are meant to be used to format code and logs. These are merely suggestions to help you make your posts more effective.
All that given, can you give me an answer as to why email verification appears on the sign in page?
(It does not actually appear on the sign in page, but a different page.) Email activation is done by many applications, to prevent an unauthenticated new user from signing in and creating content. Phone number verification on the User Settings page serves a different purpose. 2FA is still done on the sign in page, similar to email activation.
Or can you give me information on possible penetration attacks on the current sign in page and give any guarantee that the Zero framework will not flood my logs under any DDoS attack.
No, I am unable to. I suggest contributing to the discussion on the GitHub Issue that you linked.