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.

Description of problem:
[RFE] support for running foreman_scap_client without Satellite server. 

Version-Release number of selected component (if applicable):
- Satellite 6.9.0 snap 8

Additional info:

Feature request is for host to be able to use foreman_scap_client without Satellite server.

The scap client always generates report and uploads it via https, there is currently no option to disable ssl and have just http request or not do upload at all and keep the generated report locally on the client.

Created redmine issue https://projects.theforeman.org/issues/31604 from this bug

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31604 has been resolved.

Verified:

Verified with:
- Satellite 6.10.0 snap 14
- ansiblerole-foreman_scap_client-0.2.0-1.el7sat.noarch
- tfm-rubygem-foreman_openscap-4.3.3-1.el7sat.noarch
- tfm-rubygem-smart_proxy_openscap-0.9.1-1.el7sat.noarch
- rubygem-foreman_scap_client-0.5.0-1.el8sat.noarch

Test steps:
- Configure Openscap on content host.
- Run "foreman_scap_client ds 1 --skip-upload" on content host.

Observation:
- If skip-upload option of foreman_scap_client command is used then then 
scap report won't be uploaded to satellite.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.10 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:4702