hi,
so far what I have understood is that. if I wanna change the role of the current user (dynamic claim) so I should stick with IdentityUserManager to change the role of the current user, but for other purpose I can use CurrentUser service to read some data about user.
because in my implementation, all I wanna do change the role of the current user based on some conditions.
am I correct ?
lets say If I don't want to change the Current Principal, but the other approach I'm taking to change the role of the user.
is it right approach or is there any better way to solve it.
Hi, I have the following method that I'm using to test the dynamic claims
as you can see I'm changing the role of the current user on the backend.
if I return the first line with CurrentUser.Roles, it still shows old roles, (this means CurrentUser service is not updating with latest data)
but if I return the second line then it return the new roles
Hi,
after seeing your screenshot when I tried that endpoint from swagger. its working fine with swagger returning 400 but with postman its still returning 500. not sure, seems like postman issue
any update on new patch about fixing the proxy issue
Hi, I'm glad that you are able to replicate the issue on your end.
for now, I will manually fix it. may I know when are you going to release this patch.
Hi, FYI, I'm able to fix the following issue
but text-template issue is still there
try to delete the proxy folder and re-generate the proxies
Hi, you are saying somewhere in the code we are directly returning domain objects instead of DTOs. let me check into that.
how about this issue, its coming from text-template
Hi, I don't have first screenshot folder in my source code
but I have the following lines in the angular\node_modules\@abp\ng.schematics\utils\model.js file
@liangshiwei has already access to my source code. you can look into that to troubleshoot the error.
