Skip to content

Emit journal alert about ldap_sudo_search_base only if sudo provider is enabled - #9079

Open
scabrero wants to merge 2 commits into
SSSD:masterfrom
scabrero:scabrero-journal-alert
Open

Emit journal alert about ldap_sudo_search_base only if sudo provider is enabled#9079
scabrero wants to merge 2 commits into
SSSD:masterfrom
scabrero:scabrero-journal-alert

Conversation

@scabrero

Copy link
Copy Markdown
Contributor

The recent patch for CVE-2026-14474 introduced a syslog alert that is emitted whenever ldap_sudo_search_base is not configured. The problem is that this alert triggers even when the sudo provider is not being used at all and is explicitly disabled via sudo_provider = none. This creates unnecessary noise in monitoring systems.

This PR fixes the issue by checking if the sudo provider has been explicitly disabled in order to skip emitting the alert. The domain log message will continue to be recorded in all cases.

Signed-off-by: Samuel Cabrero <scabrero@suse.com>
When ldap_sudo_search_base falls back to the root DN, a log alert is
always raised, even if the sudo provider is explicitly disabled by
setting sudo_provider to 'none'. This produces unnecessary noise in
monitoring systems.

Until now, the only way to avoid the alert was to point
ldap_sudo_search_base at some subtree, which makes little sense when
sudo is not used at all. Setting sudo_provider to 'none' is the more
natural way to silence the alert, and it has the added benefit of
fully disabling the sudo data provider.

Only emit the alert when the sudo target is actually enabled.

Signed-off-by: Samuel Cabrero <scabrero@suse.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant