Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v23.3.x] kafka: Fixed segfault issue with auditing and mTLS #23289

Conversation

vbotbuildovich
Copy link
Collaborator

Backport of PR #23245

The audit log system requires that at the Redpanda cluster is configured
to use SASL/SCRAM authentication.  This is due to permissions applied to
the audit log topic (only permitting the audit log system to produce to
the audit log topic).  When the internal k/client attempts to connect
the the node and it reports "illegal_sasl_state", the audit system flags
that the audit system is misconfigured. This prevents audit messages
from being enqueued into the audit system and in turn ensures that the
unaudited action is not performed (that's important).

Originally, if the next error message seen is not "illegal_sasl_state"
then the flag is unset.  However, after reconnect the client may see
"broker_not_available" and then "illegal_sasl_state".  This commit
changes the behavior to wait for neither "illegal_sasl_state" nor
"broker_not_available" to be seen before unsetting the flag.

Signed-off-by: Michael Boquard <michael@redpanda.com>
(cherry picked from commit 51de7bb)
@vbotbuildovich vbotbuildovich added this to the v23.3.x-next milestone Sep 12, 2024
@vbotbuildovich vbotbuildovich added the kind/backport PRs targeting a stable branch label Sep 12, 2024
@michael-redpanda
Copy link
Contributor

Force push 964c8ff:

  • REmoved ok_to_fail_fips

The connection_context::start method enqueues the connect_context
instance into the list of connections.  If connection_context::stop is
called before the item is inserted, then a segfault will happen.

Fixes: CORE-7245

Signed-off-by: Michael Boquard <michael@redpanda.com>
(cherry picked from commit a5f56c3)
@michael-redpanda
Copy link
Contributor

Force push b048d27:

  • Actually removed it this time

@michael-redpanda michael-redpanda self-assigned this Sep 13, 2024
@michael-redpanda
Copy link
Contributor

@michael-redpanda michael-redpanda merged commit f702470 into redpanda-data:v23.3.x Sep 13, 2024
13 of 17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/redpanda kind/backport PRs targeting a stable branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants