OpenFGA
Fine-grained authorization component for Foundation access control.
Component Category
Access and security / authorization
Component Description
OpenFGA is a fine-grained authorization system designed to model and evaluate access relationships at scale.
Why It Is Used
In BullSequana AI Foundation, OpenFGA supports granular permission models beyond simple role checks. It helps enforce consistent authorization across services, resources, and platform operations.
Learn More
Deployment notes
OpenFGA deploys into the openfga namespace at sync wave 1 in the coreai tier. It uses the CNPG PostgreSQL cluster for persistence. A DatabaseRole CRD and a Database CRD provision the role and database at negative sync waves, and a permissions Job grants the required privileges before the application starts. The chart's own migration is turned off. The platform runs the openfga-migrate Job as an Argo CD Sync hook at sync wave -1, before OpenFGA starts.
What it authorizes
The BSQAI API stores its authorization model in OpenFGA and checks every tenant-scoped request against it. The model covers the platform and its organizations, custom roles, agents, skills, MLflow workspaces, experiments, prompts, and registered models, serving endpoints and their access rules, folders and files, MCP servers, data connections and ingestions, and service accounts. Tuples keeps the data-platform permissions in its own OpenFGA model, and Kubeflow records personal storage bucket ownership in another. See Roles and permissions for the permissions a role grants.
API authentication
The OpenFGA API rejects any request without a valid key, over both HTTP and gRPC. The health endpoints remain open for Kubernetes probes. Notebooks and other tenant workloads receive no key and cannot read or change authorization data.
Each platform caller has its own pre-shared key: the BullSequana AI API and its workers, Tuples, the Kubeflow profile controller, and Lakekeeper. The platform CLI generates the keys once during rendering, seals them, and delivers each key only to its caller's namespace. The OpenFGA playground is disabled.
To rotate or revoke a key, set its value in platform.env (OPENFGA_AUTHN_BACKEND_KEY, OPENFGA_AUTHN_TUPLES_KEY, OPENFGA_AUTHN_KUBEFLOW_KEY or OPENFGA_AUTHN_LAKEKEEPER_KEY), then render and sync. OpenFGA restarts automatically when its key list changes. Restart the affected caller as well so it picks up its new key, because its requests are rejected until it does.
Interacts With
BSQAI APIand its workers, which check and write tenant, role, and resource relationships.Tuples, which manages data-platform permissions.Kubeflow, whose profile controller records the ownership of each user's personal storage bucket.Lakekeeper, which authorizes catalog access.Keycloak, whose users and groups the BSQAI API's Keycloak sync workflow mirrors into OpenFGA relationships.PostgreSQL, which stores the OpenFGA authorization models and relationships.