Method for Working with CryptoPro DSS

Platform server requests data from back end and sends it for signing. The server saves the signed data in its database until th next mobile client request about sending data to back end. To sign data in CryptoPro DSS, set up CryptoPro parameters in the administrator interface, add the CryptoPro DSS login to user settings, and set up a data source, to which signed data will be sent.

Requests

Method: POST.
URL: /api/v1/dss/get_certificates/.

Specify DSS user password in the request body.

To send a document to signing, execute the request:

curl -s -v -X POST -H "Content-Type: application/json" -H "Authorization: Bearer <user token>" -d '{
   "certificate_id": "<certificate identifier>",
    "certificate_pin": "<PIN code for certificate>",
    "request_params": "<input parameters>",
    "column_name": "<column name>",
    "dss_password": "<DSS user password>",
    "resource_name": "<resource name>",
    "row_id": "<row number>",
    "table_name": "<table name>"
}' "<IP address or DNS server name>/api/v1/dss/sign/"

The request contains certificate identifier, PIN code if required, DSS user password, and coordinate of cache cell with data that must be signed: resource, table, column, row number.

The example of response:

{
"signature_id":35
}

This request is identical to a standard request on sending data to data source:

Method: POST.
URL: api/v1/rpc/resource_name/.

Specify signature ID in the request body.

Method: GET.
URL: /api/v1/dss/get_signatures_list/.

The response contains the list of signatures created by this user.

Method: DELETE.
URL: /api/v1/dss/signature_delete/.

Specify ID of the signature to be deleted in the request URL.

If the signature is successfully deleted, the response will be empty. If the signature was absent, the response contains "Not Found".