Exchange per-replica token cache #18

Closed
opened 2026-09-14 17:04:59 +00:00 by ginjiruu · 0 comments
Owner

Parent

#11 — Spec: The flow-serving bridge (gRPC ext_authz Check + OIDC/Exchange flows + callback/logout listener)

What to build

The Exchange Flow's per-replica token cache: repeated machine requests with the same subject token don't hammer the IdP token endpoint — the exchanged token is cached per-replica for its lifetime.

Acceptance criteria

  • A per-replica, TTL-bounded (≤ the access token's exp) LRU cache keyed by (subject_token, scopes, audience).
  • Two identical Exchange Checks result in the token-endpoint double being hit only once (a cache hit).
  • A miss/eviction (a different key, or TTL expiry) re-exchanges; a cache miss has no correctness impact.

Blocked by

  • #15 — Exchange Check
## Parent #11 — Spec: The flow-serving bridge (gRPC ext_authz Check + OIDC/Exchange flows + callback/logout listener) ## What to build The Exchange Flow's per-replica token cache: repeated machine requests with the same subject token don't hammer the IdP token endpoint — the exchanged token is cached per-replica for its lifetime. ## Acceptance criteria - [ ] A per-replica, TTL-bounded (≤ the access token's exp) LRU cache keyed by `(subject_token, scopes, audience)`. - [ ] Two identical Exchange `Check`s result in the token-endpoint double being hit only once (a cache hit). - [ ] A miss/eviction (a different key, or TTL expiry) re-exchanges; a cache miss has no correctness impact. ## Blocked by - #15 — Exchange Check
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lab/authz-bridge#18
No description provided.