-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
1
-
M
When implementing cloud users in Optimize Cloud, we reused the caching mechanism that existed for engine users, i.e. periodic user synchronization to allow quick search within Optimize. However, that means we also inherit the limitations that come with this solution, such as the cache being outdated, and possibly some bugs around collection roles like we've seen in the past.
The accounts service offers a performant users endpoint, meaning we might have the potential to always request user information on demand rather than have any cache exist, and still get this information in a performant way. We should investigate migrating to this implementation.
AT:
- organisation users are retrieved on demand from the accounts service using the users access token
- user search is implemented on the user list retrieved from accounts service, rather than in a local search cache
Hints:
- There is also a user task cache, could this also be replaced? => no, this one is only relevant and populated for Camunda 7, there is no assignee data for C8
Justification:
Removes potentially buggy user experience (and possibly security issue) whereby deleted cloud users could still have access to user collections in Optimize. We can now retrieve users in a performant way, so should utilise this.
This is the controller panel for Smart Panels app
- mentioned in
-
Page Loading...