Fetch Pending Updates (V2C) Using C2V

This web service returns pending updates based on the C2V. Multiple pending updates are combined into a package and returned in a new format (.V2CP). For using this web service, you do not need to login or logout.

If the server is unavailable or busy handling other requests, it is recommended to retry and poll the server after 60 minutes. This is a suggestion and can vary depending on the ISV’s dynamic business requirement.

When the Fetch Pending Updates (V2C) Using C2V web service returns a Success response, it also returns an added header that contains the value specified in the Client Polling Frequency (Web Services) parameter, located under the General Configuration tab in the Sentinel LDK-EMS Admin Console.

You can write a routine in your protected application that uses this value to set the polling frequency for calling the web service and checking for updates to the protection key. In this manner, you can centrally control the polling frequency for your application at all customer sites. You can also alter the polling frequency dynamically for all applications that call this web service by changing the value of the Client Polling Frequency (Web Services) parameter.

NOTE   For more information about the recommended polling frequency and retry interval, refer to the following tech note (requires login):
https://supportportal.thalesgroup.com/csm?id=kb_article&sys_id=75b9da0e4f0d1b0c102400818110c764

Prerequisites

Before calling this web service, you must ensure the following:

>RTE version 7.63 or later must be installed on the user's machine.

>The C2V that is passed must be for a non-SL-Legacy key.

Method Type	URI
POST	v90/ws/activation/target.ws

Sample Request

In the request body, pass the C2V of the key for which pending updates are expected.

Request Body:

<?xml version="1.0" encoding="UTF-8"?>
<hasp_info>
	<haspscope>
		<hasp id="12345678">
			<vendor id="37515"/>
			<update_counter>1</update_counter>
		</hasp>
	</haspscope>
	<c2v>
		.
		.
		.
		.
		.
		.
		.
	</c2v>
</hasp_info>

Sample Response

Success

The response contains the bundled pending updates. Save the response in a .V2CP file and apply it using Runtime API or Admin Control Center.

HTTP Status Code: 200

Response Body:

<?xml version="1.0" encoding="utf-8"?>
<hasp_info>
  <haspscope>
    <vendor id="37515">
      <hasp id="12345678"/>
    </vendor>
  </haspscope>
<!-- Base64 encoded ZIP file content will be part of v2cp element -->
<v2cp>
	.
	.
	.
	.
	.
	.
	.
</v2cp>
</hasp_info>

Failure

HTTP Status Code: 404.