I am trying to understand the purpose of having different Roles for different tenants. The issue is that based on how security is designed, roles access is applied at the application level....not the tenant or user level. In addition, if I have a role name "Admin" in both tenants, it may mean something different in the other tenant.
At an even higher level of application security design, what happens when an enduser/admin adds a new role...it really doesn't mean anything because the role was not implemented in the application.
Any suggestions that you all have already done?
If none, would anyone be interested in collaborating on developing a solution?
I am suspecting that Radzen will need to change/add the flexibility to allow the IDE to specify a custom AuthorizeAttribute.
To me...that is still at the code level whether it is generated or hand coded...What happens when the user creates a new Role? The application has to be regenerated to support the new role. Design time vs. Run time.
This is how ASP.NET security works - via code. One has to specify the role names either via AuthorizeAttribute or a custom policy. We don't know of any way around it.
So what I am suggesting is if anyone is interested in collaborating on building a custom policy security framework so that you can apply security at runtime.