fix: bug authentication errors hard to investigate without extra data in logs

[VladimirFilonov]

Closes #5026

📑 Description

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• All the tests have passed

ℹ Additional Information

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
keep	⬜️ Ignored (Inspect)	Visit Preview		Jun 17, 2025 8:45am

[shahargl]

lgtm

[cursor-com]

Bug: Sensitive Data Exposed in Authentication Logs

The request body is logged in authentication error cases, exposing sensitive data (e.g., passwords, API keys, tokens) to log files. This creates a security vulnerability by storing confidential information in an insecure location.

keep/identitymanager/authverifierbase.py#L192-L199

keep/keep/identitymanager/authverifierbase.py

Lines 192 to 199 in 6c7b270

	)
	self.logger.error(
	"No valid authentication method found",
	extra={
	"headers": request.headers,
	"body": body,
	}
	)

Fix in Cursor

---

Was this report helpful? Give feedback by reacting with 👍 or 👎

[shahargl]

lgtm