The approach mentioned above only auto fill the tenant name when you landed on the login page.
You can always empty the tenant name to login as host
Hi, you can modify FindUsers in CommonLookupService to filter by input.Ids. Then use the first users in the responses.
Otherwise, you can also add FindUserById() in UserAppService.
Hi, Thanks for reporting.
We will fix it. https://github.com/aspnetzero/documents/pull/139
Hi, one possible solution is to add tenant name as query param to the application url in testing environmen. Then, implements auto tenant selection via query param in your application.
In this case, test user will always land on tenant login page.
Hi, do you see any errors in the server Log.txt or brower console?
Hi, @p.j.keukens Thanks for reporting. I have created a fix for it.
https://github.com/aspnetzero/aspnet-zero-core/pull/2395
Hi, automatically tenant selection is not recommended in general. For example, show the automatically selected tenant A information to a user from tenant B might even be more confusing.
Hi, it could be due to your virtual Product Product
See https://docs.microsoft.com/en-us/ef/ef6/fundamentals/proxies
Hi, the idea of creating your own permission dependency is good.
However, it might require quite a bit of work to get current project id in permission context.
you can consider checking for current project id in your own IUserNavigationManager instead
Hi, you can first get admin role via RoleAppService and use the roleId for admin role in the next call to UserAppService
