Transaction Logs
The Signing Service Transaction Logs page maintains a record of requests received by the ADSS Signing Service and the corresponding responses generated by the service. These transaction records are primarily used for auditing, troubleshooting, and monitoring purposes.
|
|
Note: The information available in the transaction log depends on the logging and document-storage configuration of the Signing Service. |

Each item in the screenshot is described below:
|
Items |
Description |
|
Clear Search |
Clears the currently applied search criteria and displays the complete set of transaction records. |
|
Search |
Opens the search window, where you can specify criteria based on the available transaction log fields. |
|
Customise Columns |
This opens a new window to configure which column need to be shown on the grid and which column need to be hidden. See below for details. |
|
Export Logs |
Exports the transaction logs as a ZIP file containing CSV data. The CSV file uses '~&~' as the column delimiter and can be opened in Microsoft Excel. To view and analyse archived transaction details in ADSS Server, import the exported file using the Import Archived option. |
|
Verify Integrity |
Verifies the integrity of transaction log records by checking their cryptographic HMAC values. The feature detects modified or tampered records and generates a verification report that can be exported to a physical location. When exporting an HMAC verification report, it is recommended to use the '.html' extension so that the report can be opened in a web browser. |
|
Pagination controls (\ |< , < , >, > \|) |
Navigate between the pages of transaction records. The number of records displayed per page can be configured from Global Settings. |
|
Verify Integrity |
Verifies the integrity of the certification service transaction log records. It detects tampered and deleted records and generates a report that can be exported to a physical drive. |
|
Show Archived |
Opens the archived transaction log interface, where previously archived or exported transaction log files can be imported and viewed. |
|
Log ID |
Displays the unique, system-generated serial number assigned to the transaction log record. The Log ID is not part of the original request or response message. |
|
Request Type |
Identifies the type of request received by the Signing Service. Supported request types include:
|
|
Response Status |
Displays the status of the response generated for the transaction. Possible values are:
|
|
Request Time |
Displays the date and time when the request was received by the Signing Service |
|
Response Time |
Displays the date and time when the response was sent by the Signing Service. |
|
Request/Response |
Provides a link to view the request and response messages associated with the transaction. The document to be signed or the signed document is not included in these messages by default |
|
Remote Server Request/Response |
Displays the request and response information exchanged with a remote Signing Server. This allows an administrator to review the information exchanged during communication with the remote server. |
|
Input Document |
Provides a View link to display the input document associated with the signing transaction. The link is available only when document storage is enabled for transaction logs. |
|
Output Document |
Provides a View link to display the output or signed document associated with the signing transaction. The link is available only when document storage is enabled for transaction logs. |
|
Client ID |
Displays the Client ID included in the request. The Signing Service verifies that the Client ID is registered in the Client Manager before granting access to the service. For more information, see Registering Business Applications. |
|
TLS Cert |
Provides a View link to display the TLS client authentication certificate used for the transaction. The link is available only when TLS client authentication was used to send the request |
|
Signing Cert |
Provides a View link to display the certificate used to sign the request. The link is available only when a signed request was submitted to the Signing Service. |
|
Error Code |
Provides a View link for transactions that contain an error. Hover over the link to view the corresponding error message, such as Signature computation failure or Signing Service Disabled. |
|
|
Note: The Input Document and Output Document links are displayed only when document storage has been enabled for transaction logs. For information about enabling document storage, see the Service Manager configuration. |
|
|
Note: Signed requests are supported only for X.509 certificate issuance. This functionality is not applicable to CV certificates used in ePassport. |
Transaction records can be sorted in ascending or descending order based on a selected column. Select the required column and sort order from the available drop-down options.
Importing Archived
To view previously archived transaction logs:
- Select Import Archived from the drop-down menu.
- Click Go.
- The Import Archived page is displayed.
The items in the above screen are described below:
|
Items |
Description |
|
Import archived transaction file |
Allows you to browse for and upload an archived transaction log ZIP file from the operator's machine. The file is uploaded to the ADSS Server before it is imported. This option can take longer for large files. The maximum supported file size for upload is 25 MB. For files larger than 25 MB, use the Archived transaction file path option |
|
Archived transaction file path |
Allows you to specify the path of an archived transaction log file that is larger than 25 MB. The file is not uploaded to the server. Instead, ADSS Server reads the file directly from the specified path before importing it. You can specify either a local file system path or a network path. |
|
|
Note: When specifying the archived transaction file path, include the file name in the path |
Archived File Format
Archived transaction files were stored in CSV format up to ADSS Server v4.7.5. Starting from ADSS Server v4.7.6, archived transaction logs are stored as ZIP files to reduce disk-space usage.
|
|
Important: If you are importing an archived transaction file created by an ADSS Server version earlier than v4.7.6 into ADSS Server v4.7.6 or later, first compress the CSV file into a ZIP file. ADSS Server does not recognise the uncompressed legacy file as a valid archived transaction file. |
Advanced Search
The Advanced Search option allows you to locate specific Signing Service transactions based on one or more search criteria.

You can search transaction records using the following criteria:
- Request ID
- Client ID
- Doc Signing Cert
- Request Type
- Response Status
- Request Time From
- Request Time To
- Response Time From
- Response Time To
Enter the required criteria and run the search to display the matching transaction records.
Customise Columns
The Customise Columns option allows you to control which fields are displayed in the transaction log grid.

By default, a predefined set of columns is displayed in the Selected Columns list.
To hide a column:
- Open Customise Columns.
- Select the required column from the Selected Columns list.
- Move the column to the Available Columns list.
- Save the column configuration
Similarly, columns can be moved from Available Columns to Selected Columns to display them in the transaction log.
Verify Integrity
Each transaction log record stored in the database is protected using a cryptographic HMAC checksum. The checksum helps detect intentional or accidental modification of transaction records.

The generated report identifies transaction records for which the integrity check has detected an issue.
Exporting the Verification Report
Click Export Logs to export the request/response information to a physical or network location.
|
|
Important: Transaction logs are exported as a complete ZIP file. The export operation does not use the currently applied search or filter criteria. Therefore, the exported file contains the complete set of transaction logs. |
Fixing HMAC Errors
The Fix HMAC Errors option recalculates and updates the HMAC values for transaction records where the HMAC is missing or incorrect.
|
|
Fix HMAC Errors does not detect or restore records that have been deleted without authorisation. It only addresses unauthorised modifications and records with missing or incorrect HMAC values |
|
|
The Verify Integrity feature is available for the transaction logs of all services within ADSS Server. |
Viewing Transaction Details
Click the Log ID of a transaction to open the detailed information for the selected transaction:

The transaction details page provides additional information about the selected request, response, certificates, documents, and other transaction-specific data.
Viewing XML Request and Response
For transactions received through the XML/SOAP interface, click the View link in the Request/Response column to view the request and response messages.
The XML request and response are displayed in separate tabs:

Select the Response tab to view the corresponding XML response:

You can export the XML request or response to a physical location by clicking the corresponding Export button.
Viewing HTTP Request and Response
The ADSS Signing Service also provides an optimised HTTP interface. This interface can be used by applications such as the ADSS Auto File Processor (AFP) to perform fast document signing from watched folders.
Because this interface uses HTTP directly, the transaction does not contain XML/SOAP encoding. Therefore, when you click the View link for an HTTP transaction, the request and response information is displayed in an HTTP-specific format.

Select the Response tab to view the response returned by the Signing Service for the selected HTTP transaction:

See also
Configuring the Signing Service
Alerts
Signing Service Interface URLs
Optimising ADSS Signing Server Performance
