While configuring hangfire dashboard I was thinking it would be nice to provide an authorization delegate that can be used instead of using the authorization filter. Under the hood it could still do the same thing, but the way the user wires it up would be simpler.
Under the hood the authorization delegate could be provided to a default internal AuthorizationFilter. And the existing Authorization property could take priority if someone provides both. Or as mentioned in the documentation "The second step is to pass it to the UseHangfireDashboard method. You can pass multiple filters, and the access will be granted only if all of them return true." we could make sure that all (not including the default local only filter) return true.
I would be willing to open a PR with the change if you are open to it.
While configuring hangfire dashboard I was thinking it would be nice to provide an authorization delegate that can be used instead of using the authorization filter. Under the hood it could still do the same thing, but the way the user wires it up would be simpler.
Under the hood the authorization delegate could be provided to a default internal AuthorizationFilter. And the existing Authorization property could take priority if someone provides both. Or as mentioned in the documentation "The second step is to pass it to the UseHangfireDashboard method. You can pass multiple filters, and the access will be granted only if all of them return true." we could make sure that all (not including the default local only filter) return true.
I would be willing to open a PR with the change if you are open to it.