Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Public Description:
3. What is the nature and description of the request?
Find unsuccessful login attempts to the Satellite application and list these attempts on satellite WebUI as well as capture the same information in the logs.
4. Need:
Should be able to audit failed login attempts against Satellite 6 via the audit feature within the webui as well as logs for foreman.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
Upstream, yes: http://projects.theforeman.org/issues/22891
This upstream issue will meet the request of logging the failed attempt, but not for audit via WebUI due to the wait audit has been developed.
Comment 2Satellite Program
2018-04-06 18:15:56 UTC
Upstream bug assigned to mhulan
Comment 3Satellite Program
2018-04-06 18:15:59 UTC
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/RHSA-2018:2927