- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
In some troubleshooting scenarios it is necessary to force SCIM to rebuild it's internal cache. Under normal SCIM functionality, manually refreshing the SCIM Cache isn't typically necessary.
This process does require a service restart, and thus a service interruption. The cache rebuild itself take a variable amount of time depending on the size of your environment.
While the rebuild is running, performance may be impacted, and Swagger may be unavailable.
- Log into the SCIM Server as an administrative user
- Navigate to the Windows Service Panel, find the Idira SCIM Service
- Stop the Idira SCIM Service.
- Use Task Manager and verify that no PACLI or JAVA processes are still running. Stop the tasks directly if necessary.
- Navigate to the <install directory>\CyberArk-SCIM\Cache folder
- Delete all contents of the \Cache\ folder. You may receive an Administrative/UAC notice depending on your security, make sure you choose to 'continue' and not 'skip'.
- Wait for deletion to complete - this can take a moment depending on the amount of cached data. The folder should be empty.
- Reboot SCIM server.
- Start the Idira SCIM Service
After the service starts, within the next few moments, data should begin generating in the cache folder.
The status of the refresh can be observed through the 'CAScimScheduler' log (located in .\CyberArk-SCIM\logs\), or by waiting for data to stop generating in the cache folder.