Regarding the permission bug, it was caused by user/role permission cache not being invalidated when the organization unit assignment changes for user/role.
I have created an issue at https://github.com/aspnetboilerplate/aspnetboilerplate/issues/4476
I think I understand Git enough to do the update OK. The ANZ, I assume is done in a simular way using the current master: https://github.com/aspnetzero/aspnet-zero-core/tree/master.
ANZ project upgrade isn't sole relying on the git repository.
You should download new version of ANZ with the same configuration (e.g MVC + jQuery or Asp Net Core + Angular , or etc ...) and replace the content in your current ANZ project.
See https://support.aspnetzero.com/QA/Questions/6887#answer-caab10c6-3454-dec9-8f8c-39ed571dae4e
also, ANZ 6.5 uses Abp 4.1 https://github.com/aspnetzero/aspnet-zero-core/releases/tag/v6.5.0
and organization unit roles are implemented in Abp 4.2 https://github.com/aspnetboilerplate/aspnetboilerplate/releases/tag/v4.2.0
did you upgrade only abp packages and not ANZ project?
Hi, do you meant the following?
when assigining user A to organization unit X (which has role M and the role M contains some permissions), user A does not have the permission grantes by role M?
Hi, you can use similar implementation as entity history.
Add Custom Config Provider https://github.com/aspnetzero/aspnet-zero-core/blob/e70c1dfad2f5f634a975948792239cc0bd1bfc10/aspnet-core/src/MyCompanyName.AbpZeroTemplate.EntityFrameworkCore/EntityFrameworkCore/AbpZeroTemplateEntityFrameworkCoreModule.cs#L43-L45
Define Custom Config Provider https://github.com/aspnetzero/aspnet-zero-core/blob/dev/aspnet-core/src/MyCompanyName.AbpZeroTemplate.Core/EntityHistory/EntityHistoryConfigProvider.cs
Get Custom Config (Client Side)
Angular https://github.com/aspnetzero/aspnet-zero-core/blob/312aa8b77542dbcc360c914c400a566cd7a00f7b/angular/src/app/admin/roles/roles.component.ts#L38-L41
jQuery https://github.com/aspnetzero/aspnet-zero-core/blob/62bbacdf02bcdd605ed42c22dbe61724a715a28b/aspnet-core/src/MyCompanyName.AbpZeroTemplate.Web.Mvc/wwwroot/view-resources/Areas/AppAreaName/Views/Roles/Index.js#L23-L29
Hi, just to proivde more clarifications, tenant subscription applies to all the users in the same tenant.
if you want to restrict functionalities on specific users within the same tenant , you should use permissions to achieve it.
Hi, metronic 5.x is only implemented for asp net core project.
asp net mvc 5.x project only supports up to metronic 4.x
see the comparison for different projects https://docs.aspnetzero.com/documents/aspnet-mvc-jquery/latest/Version-Difference
Hi, thanks for reporting. I hve created an issue for this.
https://github.com/aspnetzero/aspnet-zero-core/issues/2350
Hi, you can refer to this issue.
https://github.com/aspnetzero/aspnet-zero-core/issues/2159
Removal of
LastLoginTime
was announced in Abp 4.2.0
You can use
UserLoginAttempts
table in place ofLastLoginTime
of a user.
See https://github.com/aspnetboilerplate/aspnetboilerplate/issues/3355#issuecomment-453975524
Hi, @davidharrison the feature dependency is actually being checked after permission dependency, see https://github.com/aspnetboilerplate/aspnetboilerplate/blob/59cd65143f59238664e0dd98826510eb38ea23ba/src/Abp/Application/Navigation/UserNavigationManager.cs#L93
so in your case, the logged in user is a tenant admin and it has all permissions but not the specified tenant feature right?
can you inject feature checker and check for if the feature is enabled for the logged in user? e.g. _featureChecker.IsEnabled(featureName)
or _featureChecker.GetValue(featureName)