Bug #11744
closedOpenSCAP content is not associated with any organization
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1261408
Description of problem: When setting up OpenSCAP, the RPM installation adds in the default content from the scap-security-guide. However, as it is not associated with any organization, the end user has to switch to 'Any Context' to see it, which is confusing.
Version-Release number of selected component (if applicable):
openscap-1.2.4-1.el7sat.x86_64
openscap-scanner-1.2.4-1.el7sat.x86_64
puppet-foreman_scap_client-0.3.3-9.el7sat.noarch
ruby193-rubygem-foreman_openscap-0.3.2.10-1.el7sat.noarch
ruby193-rubygem-openscap-0.4.2-2.el7sat.noarch
ruby193-rubygem-scaptimony-0.3.0.1-1.el7sat.noarch
rubygem-smart_proxy_openscap-0.3.0.9-1.el7sat.noarch
scap-security-guide-0.1.19-2.el7.noarch
How reproducible:
100%
Steps to Reproduce:
1.Install the SCAP components;
yum install ruby193-rubygem-foreman_openscap -y
2. Restart Apache
service httpd restart
3. Go to hosts->SCAP Contents
Actual results:
SCAP content is not shown if your context is not 'Any Context.
Expected results:
It is the end-users expectation that if they installed the SCAP components, they'd want to use them. As such, this BZ requests that the SCAP content is associated with all organizations that are present on the Satellite at the time the SCAP plugin is enabled.
Additional info:
Updated by Shlomi Zadok over 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman_openscap/pull/127 added
- Pull request deleted (
)
Updated by Marek Hulán over 8 years ago
- Status changed from Ready For Testing to Closed
- Assignee set to Shlomi Zadok
- % Done changed from 0 to 100