-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
We recently removed the identity sync cache from C8SaaS environments, instead no relying on the access token to fetch organisation members on demand, and performing the filtering in Java. While this request is performant and removes the delayed results from collection users not being available in Optimize, there is also the risk that these requests are repeated too frequently over the network. Given that the results are the same for each request unless an organisational change happens, it would make sense for Optimize to add a lightweight and short lived cache for these results.
ATs:
- Optimize has a cache for organisation members
- The ttl of the cache is configurable
- The default ttl is 10 minutes
- (Optional) if appropriate, the updated members list could be fetched on cache miss and the cache updated
Testing notes:
- The cache size and refresh interval can be configured in the config file
- The cache size and refresh interval can be configured using environment variables
- A user not in the cache can still access Optimize
- Users added to auth0 are populated into the cache when the next interval happens