feat(docs): add Authorization REST API integration guide#285
feat(docs): add Authorization REST API integration guide#285marythought merged 7 commits intomainfrom
Conversation
There was a problem hiding this comment.
Code Review
This pull request introduces a comprehensive guide for the Authorization REST API, covering authentication, health checks, and core service endpoints with examples in multiple languages. The review feedback identifies a technical inaccuracy regarding the JSON structure for JWT-based entity identifiers and suggests using versioned REST paths for legacy v1 endpoints to maintain consistency with the OpenAPI specification.
|
❌ Surge preview build failed — no preview was deployed. Check the workflow logs for details. Once the build passes, the preview will be at: https://opentdf-docs-pr-285.surge.sh Common cause: If the build failed on vendored YAML validation, run the following locally and commit the result: |
|
❌ Surge preview build failed — no preview was deployed. Check the workflow logs for details. Once the build passes, the preview will be at: https://opentdf-docs-pr-285.surge.sh Common cause: If the build failed on vendored YAML validation, run the following locally and commit the result: |
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Fix token entity identifier structure (top-level alternative to entityChain, not a field within it) - Use versioned REST path /v1/authorization for legacy GetDecisions endpoint - Add audience configuration warning for OIDC tokens - Document DECISION_UNSPECIFIED alongside PERMIT and DENY - Note 200-request hard limit on GetDecisionBulk - Document index-matched bulk responses with no entity info - Update vendored OpenAPI specs (authorization, kasregistry) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
… fence Wrap GetDecision, GetDecisionBulk, and GetEntitlements tab examples in <details>/<summary> blocks so the page is easier to scan. Also wrap the batching strategy TypeScript snippet and remove a stray ``` after the index-matching caution admonition. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Link each endpoint section and the endpoint reference table to the corresponding auto-generated OpenAPI schema pages under /OpenAPI-clients/authorization/v2/. Also add a top-level link to the OpenAPI reference in the intro paragraph. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…es link Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
23ba3a4 to
ed01b18
Compare
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
jakedoublev
left a comment
There was a problem hiding this comment.
These enhancements are really great. I have a couple pieces of feedback before we merge.
Replace incorrect gRPC-Gateway reference with ConnectRPC (HTTP/1.1 and HTTP/2 supported natively, no gateway needed). Add JWT validation warning for integrator PEPs passing tokens to the authorization service. Also includes previously staged v1-to-v2 migration details section. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Summary
/guides/authorization-rest-apishowing how to call the OpenTDF Authorization Service directly over HTTP, without an SDKContext
Rocket.Chat PR #39845 built a full Virtru PDP integration by hand-rolling ~200 lines of HTTP calls. The existing authorization docs cover SDK usage only — this guide fills the gap for server-side REST API consumers.
Test plan
/guides/authorization-rest-api/sdks/authorization,/sdks/obligations,/guides/authentication-guideresolve🤖 Generated with Claude Code