Bug 1480503 - Wrong path displayed for SCAP API
Wrong path displayed for SCAP API
Status: CLOSED NOTABUG
Product: Red Hat Satellite 6
Classification: Red Hat
Component: SCAP Plugin (Show other bugs)
6.3.0
Unspecified Unspecified
unspecified Severity unspecified (vote)
: Unspecified
: --
Assigned To: satellite6-bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-11 05:33 EDT by Sanket Jagtap
Modified: 2018-01-04 00:08 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-11 10:12:50 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sanket Jagtap 2017-08-11 05:33:23 EDT
Description of problem:


Version-Release number of selected component (if applicable):
Satellite 6.3.0 snap10

How reproducible:
Always

Steps to Reproduce:
1.Go to sat.com/api/ 
2.
3.

Actual results:
/api/compliance/arf_reports
/api/compliance/scap_contents
/api/compliance/policies
/api/compliance/tailoring_files

Expected results:
/api/v2/compliance/arf_reports
/api/v2/compliance/scap_contents
/api/v2/compliance/policies
/api/v2/compliance/tailoring_files

Additional info:
Comment 2 Marek Hulan 2017-08-11 10:12:50 EDT
The /v2/ is optional way to specify the API version, you can use the header and then the /v2/ is not required. This is not specific to openscap, that's how Satellite 6 API works.

An example of curl arguemtn to specify format and version of API -H "Accept: version=2,application/json"

Closing this and NOTABUG, please reopen if I misunderstood or if it does not work for SCAP API endpoints.

Note You need to log in before you can comment on or make changes to this bug.