The user is not updated in another instance in real time (need reload instance)
User info is only fetched if it's not already in the current session's cached user list. So a reboot of kM App is needed for the info to be updated.
This is not a big issue but with the ability to edit your own profile from KM Server, this could very well happen to someone.
What we need is to get a profile_last_modified field on KM Server and KM App to know if we need to fetch user info all over again or use the cache.
Depends on #759 (closed) for a proper implementation.
Edited by Leon