Repository navigation
Harden backend: audit integrity, readiness probes, backup verification, and distributed tracing - #996
Merged
Conversation
|
@agbochenuv-bit Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
levoski1
added a commit
that referenced
this pull request
Oct 21, 2026
Harden backend auth: scoped rate limiting, trusted proxies, and API key scopes/expiry Merge conflict resolution: combined the #996 audit-chain/tracing work with the #998 API-key scope, rate-limit and trusted-proxy work; added auth::normalize_scopes/auth::issue_api_key helpers referenced by create_merchant_api_key but missing from the PR branch.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Harden backend: audit integrity, readiness probes, backup verification, and distributed tracing
What was solved
#975 — Make admin audit records tamper-evident
Add tamper-evident integrity protection for critical administrative audit records in the backend, defining a verification mechanism (e.g., hash-chained records) and covering audit writes, failure cases, and verification with tests.
Addressed:
#976 — Add dependency-specific readiness checks
Add dependency-specific readiness checks to the backend so MongoDB, Redis, and Soroban RPC are probed independently, with the readiness endpoint reporting each dependency's status and returning an unhealthy status when any required service is unavailable.
Addressed:
#977 — Automate backup and restore verification
Add an operator-run/scheduled backup restore verification for MongoDB and Redis that actually restores backups into a scratch environment, checks recovered data, and reports pass/fail. This is a new operational script plus a CI workflow (and possibly a Makefile target) rather than changes to application code.
Addressed:
#978 — Add distributed tracing across backend operations
Add distributed tracing to the backend so API requests are correlated with Soroban RPC calls, indexing, and webhook delivery via propagated trace context, while redacting secrets and sensitive payload data from traces.
Addressed:
Changes
backend/src/lib.rs(modify)backend/src/auth.rs(modify)backend/src/handlers.rs(modify)backend/src/main.rs(modify)backend/.env.example(modify)backend/src/handlers_readiness.rs(modify)Makefile(modify)backend/Cargo.toml(modify).github/workflows/ci-stack-smoke.yml(modify).github/workflows/ci-post-deploy-verify.yml(modify)Approach
Issues
Closes #975
Closes #976
Closes #977
Closes #978