Reporting File Access Information
Reports file access records to the trusted status system.
Item |
Description |
|---|---|
API path |
/rest/kdc_agent/v1/proxy |
Request method |
POST |
Content description |
This interface is implemented by the network management system (NMS). {PREFIX} is defined by the NMS and configured for TrustRuntime through customization (e.g., {PREFIX}/v1). |
Request Header
Parameter |
Value |
|---|---|
Content-Type |
application/json |
Accept |
application/json |
Request Body
Parameter |
Type |
Specification |
Required (Yes/No) |
Description |
|---|---|---|---|---|
taskId |
String |
64 |
Yes |
Task ID. Each request must use a unique ID. |
version |
String |
8 |
Yes |
Payload format version in VR format, initially set to 26.0. |
msgType |
Int |
32 |
Yes |
Service message type, with a value of 34. |
data |
Object |
- |
Yes |
Service message entity in key:value format. |
data.filename |
String |
256 |
Yes |
File name. |
data.timestamp |
UInt64 |
64 |
No |
File access timestamp (ms) |
Request Body Example
{
"taskId": "SDFMOASDMNFIOASMD",
"version": "26.0",
"msgType": 34,
"data": {
"filename": "file1",
"timestamp": 1774615888000
}
}
Response Header
Parameter |
Value |
|---|---|
Content-Type |
application/json |
Response Body
Parameter |
Type |
Specification |
Required (Yes/No) |
Description |
|---|---|---|---|---|
retCode |
Int |
32 |
Yes |
Error code |
retMsg |
String |
64 |
Yes |
Error message |
data |
Object |
- |
No |
Custom service data |
Response Body Example
{
"retCode": 0,
"retMsg": "Success"
}
Error Code
Error Code |
Description |
|---|---|
0 |
Success. |
200 |
Invalid anchor. |
201 |
File count exceeds the limit. |
202 |
Database operation failed. |
203 |
Data tampered. |
204 |
Database not found. |
205 |
Rollback detected. |