Fetch Latest Data from CipherTrust Manager
Application Data Protection supports many types of connectors. For connectors like DPG, there exists an application policy. Using the application policy, the Application Data Protection gets to know about the what all resources (protection policy, access policy, user set) are used by the clients. Whenever a client sends heartbeat request, the Application Data Protection sends the latest version of resources in the heartbeat response.
There are some connectors like CRDP for which an application policy doesn't exist. For these connectors, Application Data Protection can't check what all resources are used by the clients. To handle such scenarios, Application Data Protection provides the /api/v1/data-protection/clients/get-updates?updated_after=
API using which clients can get the updated resources.
While calling the /api/v1/data-protection/clients/get-updates?updated_after=
API, specify the names of the resources for which you want to fetch the latest versions. You must also specify the time after which you want to get the updated resources.
Use Cases
- How will client know whether the requested resources exist on the CipherTrust Manager?
In response to the /api/v1/data-protection/clients/get-updates?updated_after=
API, Application Data Protection sends a parameter, count_mismatch
. If the value of count_mismatch
is false
, the resources requested by the client exist on the CipherTrust Manager. The Application Data Protection sends the latest versions of the resources to the client and the same gets updated in the cache. If the value of count_mismatch
is true
, the resources requested by client do not exist on the CipherTrust Manager. In such cases, the Application Data Protection sends the updated resources and the non-existent resources are deleted from the client's cache.
- What happens if the
updated_after
time is not specified in the API request?
If the updated_after
time is not provide, the Application Data Protection will return the details of all the resources and count mismatch.
- What should be the format of the
updated_after
time?
The updated_after
time should be provided in UTC format.