Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1480503 - Wrong path displayed for SCAP API
Summary: Wrong path displayed for SCAP API
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SCAP Plugin
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-11 09:33 UTC by Sanket Jagtap
Modified: 2018-01-04 05:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-11 14:12:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1530876 0 medium CLOSED API are not forwarded to API v2 automatically when no version mentioned. 2021-02-22 00:41:40 UTC

Internal Links: 1530876

Description Sanket Jagtap 2017-08-11 09:33:23 UTC
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 14:12:50 UTC
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.