Hello,
By default, permission can be used on both the tenant and the host side. See: https://docs.abp.io/en/abp/latest/Authorization#multi-tenancy
Also, as you know, AbpHangfireAuthorizationFilter class has the enableTenant and requiredPermissionName fields.
I think assigning the relevant permission to the user in the tenant will solve the problem. See: https://docs.abp.io/en/abp/latest/Background-Jobs-Hangfire#abphangfireauthorizationfilter
Any chance to try this case?
Can't do this from the user interface?
Any chance of posting a minimally reproducible example where we can reproduce the problem?
Thanks for the reporting, we will fix the problem as soon as possible.
I'm closing this question as the follow-up of the issue will be done together with the internal issue.
Thanks for the report 🙏
I'm closing this question because we will follow up with the internal issue.
Thanks for the explanation and report.
I agree, I think this is a problem.
As a result, I am creating an internal issue related to the subject.
Closing the issue. Feel free to create a new issue if you have further questions.
Creating a tag helper is standard, you can check Microsoft's documents. If you want to customize one of the ABP's tag helpers, you can create a class deriving from the taghelperservice class of any one (example: https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.AspNetCore.Mvc.UI.Bootstrap/TagHelpers/Button/AbpButtonTagHelperService.cs), then replace the original in the dependency injection system.
I want to customize some abp tag helper or add a new tag helper
https://github.com/abpframework/abp/pull/11985
We solved the problem, it will be in use with the 5.2.0-rc.2 version, FYI.
Thanks for the suggestion. I agree with you on this.
I will create an internal issue about this and if the team sees it appropriate, we will implement it.
Closing the issue. Feel free to re-open or create a new issue if you have further questions related to this.