Skip to content

Suppress ldappool INVALID_CREDENTIALS tracebacks#49

Open
bbobrov wants to merge 1 commit intostable/2025.1-m3from
boris-ldappool-trace
Open

Suppress ldappool INVALID_CREDENTIALS tracebacks#49
bbobrov wants to merge 1 commit intostable/2025.1-m3from
boris-ldappool-trace

Conversation

@bbobrov
Copy link
Copy Markdown
Collaborator

@bbobrov bbobrov commented Mar 14, 2026

The ldappool library logs ldap.INVALID_CREDENTIALS at ERROR level with a full traceback in _create_connector() every time a user provides wrong credentials. This is not a server error but a normal operational event. The ERROR tracebacks create log noise and make it harder to spot real problems.

Install a logging.Filter on the 'ldappool' logger that drops ERROR records containing 'Invalid credentials'. Keystone already logs failed authentication at WARNING level in _handle_keystone_exception(), so no information is lost.

Generated-By: claude-opus-4-6 (OpenCode)

Change-Id: I943c0f3b4f50e64fab1da85367b25a00b3e9b1bd

The ldappool library logs ldap.INVALID_CREDENTIALS at ERROR
level with a full traceback in _create_connector() every time
a user provides wrong credentials. This is not a server error
but a normal operational event. The ERROR tracebacks create
log noise and make it harder to spot real problems.

Install a logging.Filter on the 'ldappool' logger that drops
ERROR records containing 'Invalid credentials'. Keystone
already logs failed authentication at WARNING level in
_handle_keystone_exception(), so no information is lost.

Generated-By: claude-opus-4-6 (OpenCode)
Signed-off-by: Boris Bobrov <b.bobrov@sap.com>
Change-Id: I943c0f3b4f50e64fab1da85367b25a00b3e9b1bd
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