feat: new authentication scheme and upstream server whitlisting

[Prajna1999]

Summary

Target issue is #140

• Change kaapi-guardrails to be internal-only, accepting requests solely from kaapi-backend.
  Each request should include a bearer token plus X-ORGANIZATION-ID/X-PROJECT-ID headers (set upstream).
• Limit requests to IPs within ALLOWED_IPS.
• Implement a check order: IP → token → tenant headers (respond with 403 → 401 → 422).

Checklist

Before submitting a pull request, please ensure that you mark these task.

• Ran fastapi run --reload app/main.py or docker compose up in the repository root and test.
• If you've fixed a bug or added code that is tested and has test cases.

Notes

• Coordinate deployment to ensure kaapi-backend sends new headers and removes X-API-KEY/body-tenant before or with guardrails deploy.
• No support for X-Forwarded-For, token-rotation overlap window, or per-route permissions/CIDR/mTLS at this time.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: cd1bdd8f-cccc-4358-b948-1d7d69f9a80f

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/auth-authz-with-backend

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Prajna1999]

correct for today's direct-connection deployment, and the doc explicitly flags this breaks the moment a load balancer/reverse proxy sits in front (every request would then appear to come from the LB's IP, silently defeating the allowlist rather than failing loudly). [follow-up] Worth a monitoring/alert plan for "is this still a direct connection" before any infra change, since the failure mode . Note for self @Prajna1999

[Prajna1999]

For CI failure https://github.com/guardrails-ai/guardrails/blob/main/HUB_UPDATE.md and tl;dr: Guardrails validators are moving to standard PyPI packages you install directly with pip, and Guardrails is discontinuing its hosted remote inferencing. Fixed in stacked PR #152 to fix CI.

[AkhileshNegi]

do we need this?

[Prajna1999]

Removed this

[AkhileshNegi]

can we fail at bootup if IP list is invalid instead of returning error

[Prajna1999]

if ENV=production and ALLOWED_IPS="", guardrails will fail at boot up.