Before You Start
To follow this guide, familiarize yourself with the following OpenFGA Concepts:- A Relation: is a string defined in the type definition of an authorization model that defines the possibility of a relationship between an object of the same type as the type definition and a user in the system.
- A Check Request: is a call to the OpenFGA check endpoint that returns whether the user has a certain relationship with an object.
- A Relationship Tuple: a grouping consisting of a user, a relation and an object stored in OpenFGA
User Directories, Identity Tokens, And Relationships
User directories store user information that’s accessed when making authorization decisions, like the group the user belongs to, their roles, or their department. The natural way to use those relationships in a Relationship-Based Access Control system like OpenFGA is to create tuples for each relation. However, implementing a synchronization mechanism to keep the user directory data up to date with tuples in the store can be challenging. When applications implement authentication using an OIDC authorization service, they receive an ID Token or an Access token, with certain claims that can be customized based on the application’s needs. Instead of writing tuples to the OpenFGA, you can use the content of the token in Contextual Tuples to make authorization checks, understanding that, if those relationships change while the token has not expired, users will still get access to the resources the content of the token entitled them to.Example
In this example, the application uses the following authorization model, in which documents can be viewed by members of a group: When a group is added as a viewer of a document, the application writes tuples like those below: Let’s assume that the Access Token the application receives has a list of the groups the user belongs to:groups claim in the token and adds contextual tuple for each group, indicating that the user is a member of that group:
The authorization check returns allowed = true, as there’s a stored tuple saying that members of the marketing group are viewers of the product-launch document, and there’s a contextual tuple indicating that the user is a member of the marketing group.
Related Sections
Check the following sections for more on how user contextual tuples can be used.Contextual and Time-Based Authorization
Learn how to authorize access that depends on dynamic or contextual criteria.
Authorization Through Organization Context
Learn to model and authorize when a user belongs to multiple organizations.
Conditions
Learn to model requiring dynamic attributes.
OpenFGA API
Details on the Check API in the OpenFGA reference guide.