feat(pam): clickhouse

[lb-vn]

Description 📣

Clickhouse

Type ✨

• Bug fix
• New feature
• Improvement
• Breaking change
• Documentation

Tests 🛠️

# Here's some code block to paste some code snippets

---

• I have read the contributing guide, agreed and acknowledged the code of conduct. 📝

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
37371931	Triggered	Base64 Basic Authentication	6865c3e	packages/pam/handlers/clickhouse/proxy_test.go	View secret
37371932	Triggered	Username Password	6865c3e	packages/pam/handlers/clickhouse/proxy_test.go	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[linear]

PAM-466

[veria-ai]

PR overview

All previously flagged issues have been addressed. No open security concerns remain on this pull request.

Security review

No open security issues remain on this pull request.

Fixed/addressed: 5 · PR risk: 0/10

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge, with no outstanding findings in the scoring set.

Summary

This PR adds ClickHouse PAM support over ClickHouse’s HTTP protocol and advertises supported PAM account types through gateway heartbeats.

• Adds ClickHouse request inspection, command blocking, credential replacement, database scoping, response auditing, and connection testing.
• Integrates ClickHouse routing, session upload metadata, and local connection guidance.
• Adds the supported_account_types heartbeat capability.
• Adds tests covering authentication replacement, policy enforcement, compressed requests, database scoping, and audit outcomes.

_{Reviews (3) · Last reviewed commit: "account type for heartbeat"}