Wiki.Quizz.vn

keyword-vs-name

phong2018 (phong2018@undisclosed.example.com) — 2026-07-09T04:36:11+00:00

OpenFGA DSL Syntax: Keywords vs Names In the DSL there are two kinds of words: keywords you must type exactly, and names you make up (or point to). Symbols like : and [ ] are also fixed. Keywords (fixed — you cannot change them) Built-in words. Spell them exactly.

authorization-model - [See also]

phong2018 (phong2018@undisclosed.example.com) — 2026-07-09T04:17:30+00:00

OpenFGA Authorization Model An authorization model is the set of rules. It defines what types of things exist and what relations can hold between them. It is the schema for your permissions. It holds only the shape of the rules. It does not hold real users or real data — that is what relationship tuples are for.

keyword-vs-name - removed

phong2018 (phong2018@undisclosed.example.com) — 2026-07-09T04:14:59+00:00

check-api - created

phong2018 (phong2018@undisclosed.example.com) — 2026-07-09T03:58:56+00:00

OpenFGA Check API The Check API is the part that answers the core question: “Is this user allowed to do this thing?” Your app sends a question, and OpenFGA replies allowed: true or allowed: false. This is the piece your app calls the most. It uses the

relationship-tuples - created

phong2018 (phong2018@undisclosed.example.com) — 2026-07-09T03:50:21+00:00

OpenFGA Relationship Tuples A relationship tuple is one small fact about who is connected to what. It is the data in OpenFGA. The authorization model defines the shape of the rules; tuples fill in the real facts. * Model = the rules (the shape). * Tuples = the data (the facts).

store - created

phong2018 (phong2018@undisclosed.example.com) — 2026-07-09T03:41:15+00:00

OpenFGA Store A Store is the top-level container in OpenFGA. Think of it as one project or one workspace. Everything for one authorization setup lives inside it, and nothing leaks out to other stores. Why stores exist You need a boundary. Without one, all your rules and data would sit in a single shared pile. Stores give you clean separation.

store - removed

phong2018 (phong2018@undisclosed.example.com) — 2026-07-09T03:41:06+00:00

openfga - [The main parts]

phong2018 (phong2018@undisclosed.example.com) — 2026-07-09T03:40:54+00:00

OpenFGA OpenFGA is an open-source authorization engine. Its only job is to answer one question: “Is this user allowed to do this thing?” It does not run your app. It sits beside your app and says yes or no. Why it exists Permission logic gets messy. Rules like

kind-in-kubenetes.png - created

phong2018 (phong2018@undisclosed.example.com) — 2026-05-31T04:06:21+00:00