I read currentUser info with configStateService, which this info comes from application-configuration request, but this has bug and after changing the name and surName of user in account manage form, it does not change in this configuration and it is still previous data and when I reload the page, name and surName are null. I have to log out and then again login to system to data change. I checked it in abp commercial demo and there is also this issue and user name and surName do not change. Also, when I change account in "Linked Accounts", it does not load this data and name and surName are null here too in response of application-configuration request, but userName is correct hopefully. But it read account profile data in account/manage route with profile request and there these data are correct. But I cannot send this request by myself because I do not have access to save button in this form to call it after save. When this issue will be fixed? We use it in our commercial panel and it has bugs.
3 Answer(s)
-
0
did you try log out > login
-
0
Yes, this is working with log out > login but this is still an issue. Why a user must log out and then login after editing his profile? Why should incorrect data come from server after that profile name and surName is edited? These are bugs. Also, The other problem is when you switch between Linked Accounts and these data are null for new switched account, while the name and surName are previously set and exist for each account.
-
1
Yes, this is working with log out > login but this is still an issue. Why a user must log out and then login after editing his profile? Why should incorrect data come from server after that profile name and surName is edited? These are bugs. Also, The other problem is when you switch between Linked Accounts and these data are null for new switched account, while the name and surName are previously set and exist for each account.
Yes. I have tested. There is an issue. I have opened a task. Probably it will be fixed in version 6.0 and patch version of 5.3. The issue is that My-Profile endpoint is updated when the user changes profile info, but the CurrentUser key of ApplicationConfiguration won't be updated. Until the logout, then re-login. I think the information is stored in the auth-token. but it should be invalidated or updated. (if we can)
Note: We have talked about the issue. The information of "CurrentUser" come from the Claims of Identity-Server/Openiddict. The only way to update this information is logout-login. There are tasks that releted to "implementing Refresh-Token feature" in identity-server and Openiddict. When Refresh-Token feature is implemented, Angular UI could have the feature that refreshes the claims without logout-login
