The current behavior for the Identity Service is to execute and resolve user data synchronously. The decision was made to now have both synchronous and asynchronous executions for the Identity Service. This will enhance performance when the Identity Service executes after a user’s information has expired.
Currently when the Identity Service executes, the execution and resolving of user data happens synchronously. This means that when for example a user logs in on Workspace to retrieve Worklist items, the Identity Service will only return data as soon as all the user information has resolved and properties for the user loaded successfully. Then only will the Worklist open. The same occurs after the user information expired.
The new behavior for the Identity Service will be as follows:
- The first time a request is made to the Identity Service to resolve and return data for a user, the Identity Service will still execute synchronously.
- Thereafter, when a user’s information has expired and another request is made, the Identity Service will execute asynchronously and data will be returned that is already available. The rest of the data will still be resolved but the user doesn’t have to wait for all data to resolve anymore.
- After the asynchronous execution is done and all data is resolved, all data will return upon the next request.
- This functionality is not configurable.
||Note: For more information on the Identity Service, refer to this topic
This Hotfix is contained within the latest K2 Update. Install the update package to enable the new behavior for the Identity Service execution.
For more information on Identity Service refer to the following topic Installation and Configuration > Installation > Post installation common tasks > K2 Server > K2 Performance > Tweaking identity cache performance for the K2 Server.