Chapter 4. OVAL
4.1. List all OVALs
Abstract
Provides an index to all recent OVAL definitions with a summary of their contents, when no parameter is passed. Returns a convenience object as the response with minimal attributes.
It does not return an index of published RHSAs as not all RHSA errata have a corresponding OVAL definition.
JSON
GET /oval.json
XML
GET /oval.xml
HTML
GET /oval
4.2. Parameters
| Name | Description | Example |
|---|---|---|
| before | Index of OVAL definitions before the query date. [ISO 8601 is the expected format] | 2016-03-01 |
| after | Index of OVAL definitions after the query date. [ISO 8601 is the expected format] | 2016-02-01 |
| rhsa_ids | Index of OVAL definitions for RHSA_IDs separated by comma | RHSA-2018:2748,RHSA-2018:2791 |
| bug | Index of OVAL definitions for Bugzilla Ids | 1326598,1084875 |
| cve | Index of OVAL definitions for CVEs | CVE-2014-0160,CVE-2016-3990 |
| severity | Index of OVAL definitions for severity | low,moderate,important |
| page | Index of OVAL definitions for page number | Default: 1 |
| per_page | Number of index of OVAL definitions to return per page | Default: 1000 |
By default, search will return the first page of 1000 results, ordered by date. To change the page size use the 'per_page' param, and then iterate through pages using the 'page' param.
All the above query parameters can be used in combination with each other to retrieve the desired result.
4.3. Retrieve an OVAL
Abstract
OVAL details for the RHSA.
JSON
OVAL definitions are in XML format, the JSON view is a representation of the OVAL data in JSON format.
GET /oval/<RHSA_ID>.json
Example: /oval/RHSA-2016:0695.json
Returns a JSON representation of the OVAL data for RHSA-2016:0695.
XML
GET /oval/<RHSA_ID>.xml
For more information about the OVAL format see the FAQ.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.