I will check it.
I can't reproduce the problem.
Can you use the new project to reproduce the problem and share it with me? shiwei.liang@volosoft.com thanks.
This sounds weird, it works fine in the emulator, but it's wrong on the real machine. I'll check it out
a) The above is happening because the following method returns null for moduleRole.Name until relogin: If I modify the module roles assigned to an ordinary role - I want to modify the corresponding "moduleRole" claims. How and where to do that efficiently (possibly caching instead of pulling from DB each time) without user relogin? I think you might have used similar mechanism already for your data. I'd prefer to update the accessible pages (and APIs) even if the page in the Angular app is reloaded; Please keep in mind, that on one hand - we are talking about ABP roles (which differ from ordinary roles only by extra field), on other hand they are permission definitions for "MR" provider;
Because JWT is immutable, you need to re-login to load the roles. You also can reload the current character for each request via Middleware, for example https://support.abp.io/QA/Questions/2090/How-to-clear-cache-for-features
b)
https://docs.abp.io/en/abp/latest/Modules/Permission-Management#permission-management-providers
IPermissionManager uses these providers when you get/set permissions. You can define your own provider by implementing the IPermissionManagementProvider or inheriting from the PermissionManagementProvider base class.
IPermissionManager uses permission value providers when you check if permission is granted.
d) will permissionServive.getGrantedPolicy or *abpPermission directive in Angular work for my "MR" permissions in the same way as it work for ordinary "R" permissions?
I guess it's ok, the Front-end loads permission grant datas from backend
Hi,
The claim Properties not working with JWT.
You can try to add new claims:
foreach(var moduleRole in ModuleRoles)
{
identity.AddClaim(new Claim("ModuleRole", moduleRole.Name));
}
Hi,
Does this error also happen if you run locally?
Solved
Could not load file or assembly xxx
This problem usually occurs when a project directly or indirectly references a different version of a package.
You can check your solution to make sure the version of the ABP packages is consistent.
Run the dotnet clean & dotnet build command.
BTW, It still not working. could you share a minimal project that reproduces this problem? I'll check it out. shiwei.liang@volosoft.com
Hi,
Yes, you can..
var user = await UserManager.FindByIdAsync(....);
user.SetEmailConfirmed(true);
await UserManager.UpdateAsync(user);
Hi,
After my check, this is not related to ABP.
Even if you create an empty MAUI app using VisualStudio MAC you get the same error.
You can check this:
