Bug 1302230 - Hide default OSCAP profile
Summary: Hide default OSCAP profile
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SCAP Plugin
Version: 6.1.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Kedar Bidarkar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-27 09:12 UTC by Kedar Bidarkar
Modified: 2017-08-01 20:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 20:33:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Kedar Bidarkar 2016-01-27 09:12:52 UTC
Description of problem:

Questions) When selecting in SCAP Content - XCCDF - "Default XCCDF profile", the
result is not selected, when we change to another option, like PCI, the
result works fine. 

Explanation) This is expected behavior. The default profile may contain rules.
However stock policies (from scap-security-guide package) never have
meaningful content.

Satellite presents default profile as an option for customers that
create their own policies, that can bring meaningful default profile.

We can improve UX and hide default profile if that option is not
meaningful given the content file. 

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


How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:

No meaningful oscap default profile.

Expected results:

Should have a meaningful default profile.

Additional info:

Comment 2 Šimon Lukašík 2016-01-27 09:45:38 UTC
This should be fixed in Proxy::OpenSCAP::ContentParser.extract_policies.

At that point we can tell, whether the 'default' profile is useful or not. We should perhaps implement that function (to query usefulness) in rubygem-openscap.

Comment 4 Bryan Kearney 2016-07-26 15:25:24 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 5 Bryan Kearney 2016-07-26 15:36:49 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 7 Bryan Kearney 2017-08-01 20:33:23 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


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