vulns.co
/
GKData.io MCP and API Buy me a coffee

OpenFGA

OpenFGA query consistency: authorization decisions need sufficiently fresh state

A permission check can miss a recent relationship update when OpenFGA caching is enabled. The official documentation describes a low-latency mode that can reuse cached results and a higher-consistency mode that bypasses the cache. Correct access decisions therefore depend on how recent the relationship data is.

Open the referenceImplementation GuideReviewed 2026-10-03

How to use this reference

Editorial lesson: specify when permission changes must become observable and align decision freshness with that requirement. Review cache invalidation and performance assumptions together; a newly issued request does not necessarily use newly changed authorization state.

Before reading

  • Relationship-based authorization and cache consistency concepts

Context and limits

  • The documentation says caching is disabled by default. Do not assume every deployment returns cached authorization decisions.
  • Its illustrative timestamp branch appears inconsistent with the prose; this record does not reproduce or endorse that example.
  • Consistency tokens are described as future work. This guidance establishes neither a deployment-specific freshness guarantee nor evidence of an incident.

Sources

  1. Query Consistency ModesOpenFGA · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software