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.

This bug was created for RHEL-8.1 Beta documentation purposes only. 

Description of problem:

On RHEL-8.1 Beta, KRB5 transport mode, ie. audit-remote logging using KRB5, is not working properly. Connection between server and client is not established and audit events are not sent from client to server.

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

audit-3.0-0.11.20190507gitf58ec40.el8

How reproducible:

100%

Steps to Reproduce:

1. Setup audit remote logging using KRB5 transport mode
2. Log from client.

Actual results:

Connection between server and client is not established. Client's audit events are not propagated to server.

Expected results:

Connection works, authentication is done using KRB5. Client's audit events are propagated to server.

Additional info:

 * There is no workaround. 
 * This bug was created for RHEL-8.1 Beta documentation purposes only. 
 * Described issue is already fixed in audit-3.0-0.12.20190507gitf58ec40.el8.

This bug should be left in NEW state and I will close it as CLOSED CURRENTRELEASE later.

The code was already fixed. Adding this to the errata.

(In reply to Ondrej Moriš from comment #0)
> This bug was created for RHEL-8.1 Beta documentation purposes only. 
>
> ...
>
> Additional info:
> 
>  * This bug was created for RHEL-8.1 Beta documentation purposes only. 
>  * Described issue is already fixed in audit-3.0-0.12.20190507gitf58ec40.el8.
> 
> This bug should be left in NEW state and I will close it as CLOSED
> CURRENTRELEASE later.

In the end we decided to add this bug to RHEL-8.1.0 errata for audit. Issue was fixed via rebase bug.

This bug is successfully verified on all supported architectures, see TC#553604 in TR#364923 for more detail. Please notice that there is a bug in selinux policy [1] causing AVC issues on remote logging server (workaround is to use permissive mode). 

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1740146

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-2019:3622