Bug 1480503

Summary:	Wrong path displayed for SCAP API
Product:	Red Hat Satellite	Reporter:	Sanket Jagtap <sjagtap>
Component:	SCAP Plugin	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	mhulan, oprazak
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-11 14:12:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.