Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
When using ospp kickstart shipped with scap-security-guide-0.1.30-3, remediation is actually so strict it makes the installed machine not usable. The only user created is the root, and ospp prevents root from logging in directly.

Version-Release number of selected component (if applicable):
scap-security-guide-0.1.30-3

How reproducible:
reliably

Steps to Reproduce:
1. install machine with /usr/share/scap-security-guide/kickstart/ssg-rhel7-ospp-ks.cfg

Actual results:
Root cannot be logged in with password "server", specified in the KS, no other user created

Expected results:
Some other user is created to be used to log into the machine.

Additional info:
Origins in Bug 1351751

Shawn, could you please confirm that this is a bug?

Upstream fix: https://github.com/OpenSCAP/scap-security-guide/pull/1969

Verified manually that kickstart

ssg-rhel7-ospp-ks.cfg

in ssg version

scap-security-guide-0.1.33-4.el7.noarch

creates user admin, is in wheel group [thus sudo-able] and has password admin123.

There are two issues though:
firewall is set to drop, thus SSG connection is not possible, and PAM hardening related to smartcard enablement prevets any user from login from console.

Issue with the PAM hardening is tracked separately in Bug 1461330

Apart from this issue, kickstart is working (see Comment 7).

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, 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/RHBA-2017:2064