One Identity Safeguard for Privileged Sessions 8.0 LTS - REST API Reference Guide

List of endpoints for configuring reporting, and accessing the generated reports.

URL

GET https://<IP-address-of-SPS>/api/configuration/reporting

Sample request

The following command lists the available endpoints.

curl --cookie cookies.txt https://<IP-address-of-SPS>/api/configuration/reporting

Response

The following is a sample response received when listing the available endpoints.

For more information on the meta object, see Message format.

{
    "items": [
        {
            "key": "_available_search_fields",
            "meta": {
                "href": "/api/configuration/reporting/_available_search_fields"
            }
        },
        {
            "key": "_available_subchapters",
            "meta": {
                "href": "/api/configuration/reporting/_available_subchapters"
            }
        },
        {
            "key": "content_subchapters",
            "meta": {
                "href": "/api/configuration/reporting/content_subchapters"
            }
        },
        {
            "key": "predefined_reports",
            "meta": {
                "href": "/api/configuration/reporting/predefined_reports"
            }
        },
        {
            "key": "reports",
            "meta": {
                "href": "/api/configuration/reporting/reports"
            }
        },
        {
            "key": "restbased_subchapters",
            "meta": {
                "href": "/api/configuration/reporting/restbased_subchapters"
            }
        }
    ],
    "meta": {
        "first": "/api/configuration/aaa",
        "href": "/api/configuration/reporting",
        "last": "/api/configuration/x509",
        "next": "/api/configuration/ssh",
        "parent": "/api/configuration",
        "previous": "/api/configuration/rdp",
        "transaction": "/api/transaction"
    }
}

Status and error codes

The following table lists the typical status and error codes for this request. For a complete list of error codes, see Application level error codes.

URL

GET https://<IP-address-of-SPS>/api/configuration/reporting/reports

Sample request

The following command lists the configured reports.

curl --cookie cookies.txt https://<IP-address-of-SPS>/api/configuration/reporting/reports

The following command retrieves the properties of a specific report.

curl --cookie cookies.txt https://<IP-address-of-SPS>/api/configuration/reporting/reports/<key_value>

Response

The following is a sample response received when listing reports.

For more information on the meta object, see Message format.

{
  "meta": {
    "first": "/api/configuration/reporting/content_subchapters",
    "href": "/api/configuration/reporting/reports",
    "last": "/api/configuration/reporting/restbased_subchapters",
    "next": "/api/configuration/reporting/restbased_subchapters",
    "parent": "/api/configuration/reporting",
    "previous": "/api/configuration/reporting/predefined_reports",
    "transaction": "/api/transaction"
  },
  "items": [
    {
      "key": "7798770004e472c8576912",
      "meta": {
        "href": "/api/configuration/reporting/reports/7798770004e472c8576912"
      }
    },
    {
      "key": "8292675195707f19d932af",
      "meta": {
        "href": "/api/configuration/reporting/reports/8292675195707f19d932af"
      }
    }
  ]
}

When retrieving the endpoint of a specific report, the response is the following.

{
  "body": {
    "access": [
      "report"
    ],
    "chapters": [
      {
        "name": "System health",
        "subchapters": [
          {
            "name": "system_health_network_connections",
            "selection": "builtin"
          },
          {
            "name": "system_health_load_average",
            "selection": "builtin"
          }
        ]
      },
      {
        "name": "All connections",
        "subchapters": [
          {
            "name": "connection_each_scb_top10_channel_types_each",
            "selection": "builtin"
          },
          {
            "name": "connection_each_scb_top10_portforward_targets_each",
            "selection": "builtin"
          }
        ]
      },
      {
        "name": "Search statistics",
        "subchapters": [
          {
            "reference": "21111736175707f1df8bea1",
            "selection": "custom"
          }
        ]
      },
      {
        "name": "Misc",
        "subchapters": [
          {
            "reference": "13869311625707e0a3e0892",
            "selection": "custom"
          }
        ]
      },
    ],
    "email_recipients": {
      "recipients": [
        "admin@company.com"
      ],
      "selection": "other"
    },
    "frequency": {
      "day": false,
      "month": true,
      "week": false
    },
    "logo_id": "logoC890jH",
    "name": "all-options",
    "send_report_in_email": true
  },
  "key": "8292675195707f19d932af",
  "meta": {
    "first": "/api/configuration/reporting/reports/7798770004e472c8576912",
    "href": "/api/configuration/reporting/reports/8292675195707f19d932af",
    "last": "/api/configuration/reporting/reports/8292675195707f19d932af",
    "next": null,
    "parent": "/api/configuration/reporting/reports",
    "previous": "/api/configuration/reporting/reports/12046247915707e5d6a5c59",
    "transaction": "/api/transaction"
  }
}

Examples:

Set the e-mail recipients to the default (as configured in the reporting_address element of the /api/configuration/management/email endpoint):

"email_recipients": {
  "selection": "default"
}

Create a custom set of e-mail recipients:

"email_recipients": {
  "recipients": [
    "<email-1>",
    "<email-2>"
  ],
  "selection": "other"
}

Add a reporting chapter with built-in subchapters:

"chapters": [
  {
    "name": "<custom-name>",
    "subchapters": [
      {
        "name": "system_health_filesystem_usage",
        "selection": "builtin"
      },
      {
        "name": "system_health_network_connections",
        "selection": "builtin"
      },
      {
        "name": "system_health_load_average",
        "selection": "builtin"
      }
    ]
  }

Add a reporting chapter with content subchapters:

"chapters": [
  {
    "name": "<custom-name>",
    "subchapters": [
      {
        "reference": "<key-of-subchapter>",
        "selection": "custom"
      },
      {
        "reference": "<key-of-subchapter>",
        "selection": "custom"
      }
    ]
  }
    

Status and error codes

The following table lists the typical status and error codes for this request. For a complete list of error codes, see Application level error codes.

Add a report

To add a report, you have to:

1. Open a transaction.

   For more information, see Open a transaction.

2. Create the JSON object for the new report.

   POST the JSON object to the https://<IP-address-of-SPS>/api/configuration/reporting/reports endpoint. You can find a detailed description of the available parameters listed in Element .

   If the POST request is successful, the response includes the key of the new report.

   {
     "key": "26ddf648-9a21-4a7f-af56-9cea575785a9",
     "meta": {
       "href": "/api/configuration/reporting/reports/26ddf648-9a21-4a7f-af56-9cea575785a9",
       "parent": "/api/configuration/reporting/reports",
       "transaction": "/api/transaction"
     }
   }

3. Commit your changes.

   For more information, see Commit a transaction.

Modify a report

To modify a report, you have to:

1. Open a transaction.

   For more information, see Open a transaction.

2. Modify the JSON object of the report.

   PUT the modified JSON object to the https://<IP-address-of-SPS>/api/configuration/reporting/reports/<key-of-the-report> endpoint. You can find a detailed description of the available parameters listed in Element .

3. Commit your changes.

   For more information, see Commit a transaction.

Generate a report for a custom time period

To generate a report for a custom time period, you have to:

1. Define the custom time period for the report.

   GET https://<IP-address-of-SPS>/api/configuration/reporting/reports. Search for the name of the report that you want to run on a custom time period. Copy the value of key.

2. POST the parameters to the https://<IP-address-of-SPS>/api/reports endpoint. The following parameter is required:

   • configuration_id

   The following parameters are optional.

   • start: start timestamp in the format of either YYYY-MM-DD or YYYY-MM-DDTHH:MM.

   • end: end timestamp in the format of either YYYY-MM-DD or YYYY-MM-DDTHH:MM.

   • force: By default: False. If you set it to True, you can regenerate a report that has already been generated before.

   If you do not enter the optional parameters, the start timestamp defaults to 1970.01.01 and the end timestamp defaults to the timestamp of when the report was generated.

   NOTE: Timestamps are according to UTC.

   This means that for example, if you are located in an UTC+1 region, a report that has the end parameter configured as 2020-01-18 will actually have an end date/time of 2020-01-18 01:00.

   Example: Generate a report for a custom time period

   https://198.51.100.0/api/reports?configuration_id=8292675195707f19d932af&start=2020-02-01&end=2020-02-18

3. You will receive a response similar to the following:

   {
     "message": "Report generation started.",
     "meta": {
       "href": "/api/reports",
       "parent": "/api"
     }
   }