IBEX Harness
DocsBenchmarksBlogChangelogRoadmap
GitHub
IBEX Harness

Documentation

Architecture Decision RecordsADR-0002: Repository foundation bootstrapADR-0003: Branch protection and merge policyADR-0004: Protobuf and code generation policyADR-0005: Postgres migration strategyADR-0006: Auth protobuf contract (`ibex.auth.v1`)ADR-0007: Auth token validation implementationADR-0008: Security scanning and CI quality gatesADR-0009: Permission bitmap layoutADR-0010: Cryptography policyADR-0011: Proxy auth gRPC client and middlewareADR-0012: Proxy request normalization (OpenAI chat)ADR-0013: Proxy input validation and stable error envelopeADR-0014: Core domain migration sequencingADR-0015: Proxy rate limit skeleton (Phase 1)ADR-0016: Proxy agent identity verification (Phase 1)ADR-0017: Request ID and trace context strategy (Phase 1)ADR-0018: Graceful shutdown contract (Phase 1)ADR-0019: OpenTelemetry provider configuration (Phase 1)ADR-0020: Shared package boundaries — `packages/config` and `packages/apierror`ADR-0021: Prometheus Metric Catalog (Phase 1)ADR-0022: Health check contract (Phase 1)ADR-0023: Docs site architecture (Phase 1.5)ADR-0024: Benchmark data publishing modelADR-0025: LLM provider abstractionADR-0026: OpenAI client designADR-0027: Streaming dual-write strategyADR-0028: Auth cache designADR-0029: Token revocation propagation via Redis pub/subADR-0030: Directive versioning strategyADR-0031: System prompt injection strategyADR-0032: Session data model and retentionADR-0033: ClickHouse llm_traces schema and retentionADR-0034: Proxy overhead performance measurement methodologyADR-0035: Chat Idempotency-Key Redis dedupeADR-0038: Context assembly service design and gRPC contractADR-0039: Proxy Postgres ownership for session and directive storesADR-0040: Anthropic provider adapterADR-0041: Model capability registryADR-0042: Self-hosted OpenAI-compatible LLM adapterADR-0043: Tokenizer registry architectureADR-0044: Non-streaming response pipelineADR-0045: Streaming response transformationADR-0046: Embedder interface and profile registryADR-0047: Memory temporal validity foundationADR-0048: Memory multi-label categoriesADR-0049: Memory relationship graph readinessADR-0050: MCP server skeleton (transport, auth, audit)ADR-0051: Local LGTM observability stack (Phase 2.5 exit pull-forward)ADR-0052: Memory schema v2 expand (HNSW, quality columns)ADR-0053: Vector store abstraction and composite scoring v2ADR-0054: In-process Presidio PII detection in memoryADR-0055: Memory write-path exact and near-duplicate dedupADR-0056: Temporal-interval-aware conflict detectionADR-0057: Memory write-path persistence and orchestrationADR-0058: Semantic search FTS fallback triggerADR-0059: Hot cache read pathADR-0060: Memory service tenant isolation architectureADR-0061: Retrieval-quality benchmark methodologyADR-0062: Worker task observability and dead-letter handlingADR-0063: Extraction output schema v2ADR-0064: Extraction provider registry and batch executionADR-0065: Extraction batch idempotency and turn pointer orderingADR-0066: Extraction quality evaluation harnessADR-0067: Context capability catalog generate-and-diff for token budgetsADR-0068: Composite scoring-time relevance gateADR-0069: Context packer bounded DP knapsackADR-0070: Context formatting locked ordering and session nonceADR-0071: Context assembly gRPC degradation ladder and retrieval deadlineADR-0072: Extraction enqueue via worker HTTP (not Celery Redis wire format)ADR-0073: Organization Lifecycle and Cascading SuspensionADR-0074 Provider Credential StorageADR-0075 Per-Org Model Routing PolicyADR-0076: Circuit Breaker per ProviderADR-0077: Provider Fallback RoutingADR-0078: Operator runtime topology & environment contract (4.P.0)ADR-0079: Operator session RS256 dual-verify and TOTP step-upIBEX Console service rename and boundaryADR-0081: Fail-closed Proxy runtime controlsD2 metadata-only trace read contractD2 publication, identity, query, and lifecycle contract
ADRs›ADR-0074 Provider Credential Storage
ADRs

ADR-0074 Provider Credential Storage

Org-scoped provider API keys sealed with AES-256-GCM envelope encryption in Auth

ADR-0074 — Provider Credential Storage and Proxy Retrieval Path

Status

Accepted (Milestone 4.A.5)

Context

Platform LLM keys are process env vars on the proxy. Multi-tenant BYO keys need org-scoped storage, encryption at rest, validate-before-store, and a fail-closed retrieval path that does not mutate shared provider clients.

Discovery found no in-repo AES/envelope helper (ADR-0010 deferred crypto) and no KMS/Vault application integration. Sketch ADR-0046 was already assigned to the embedder.

Decision

  1. Stdlib AES-256-GCM envelope in packages/crypto only (Go). KEK from IBEX_CREDENTIALS_MASTER_KEY (base64 32 bytes), Auth-only.
  2. Column layout: ciphertext, wrapped_dek, encryption_key_id, key_hint (each sealed blob is nonce||GCM ciphertext+tag).
  3. Auth owns plaintext at rest: Create/Get/List/Delete gRPC; Management API never persists ciphertext or returns secrets.
  4. Validate-before-store in Management API (Python httpx probe) → INVALID_CREDENTIAL (422).
  5. Proxy: per-request GetProviderCredential + 30s cache; optional provider.Request.APIKeyOverride; no-row → platform default; row + Auth error → fail closed.
  6. Separate POST .../validate deferred to a follow-up.

Consequences

  • Production Auth requires IBEX_CREDENTIALS_MASTER_KEY.
  • Proxy boot path for platform keys unchanged when no credential rows exist.
  • Multi-key rotation / Vault / Bedrock IAM remain out of scope.

Was this page helpful?

Edit on GitHub

Last updated on

PreviousADR-0073: Organization Lifecycle and Cascading SuspensionNextADR-0075 Per-Org Model Routing Policy

On this page

  • Status
  • Context
  • Decision
  • Consequences
0%