Open MilesFan opened 2 years ago
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
In a blazor server application, I can obviously customized a default unauthorized message globally in App.razor as follows:
This is nice in a simple application, as it gives a hint what users should do when they are not authorized to do what is supposed to be done.
However, in a large or complex organization where business along with relevant permissions are managed seperately, John Doe the administrator may not be able to answer all the user queries or make a decision on the permissions.
As far as I know, to achieve the goal of letting a rejected user to know what to do exactly, I have to handle unauthorized requests in each razor page repeatedly.
Describe the solution you'd like
I propose extending AuthorizeRouteView to be capable to handling differrent reasons for authorization failure:
Additional context
No response