Project: OpenFGA (Provisioning / Security & Compliance)
File: CHANGELOG.md

All notable changes to this project will be documented in this file. The format is based on , and this project adheres to . Try to keep listed changes to a concise bulleted list of simple explanations of changes. Aim for the amount of information needed so that readers can understand where they would look in the codebase to investigate the changes' implementation, or where they would look in the documentation to understand how to make use of the change in practice - better yet, link directly to the docs and provide detailed information there. Only elaborate if doing so is required to avoid breaking changes or experimental features from ruining someone's day. Apply tags to requests that have been intentionally throttled (https://github.com/openfga/openfga/pull/1531). This will add a new log field titled "throttled" to such requests. Panic that occurred on Check API with some authorization models and tuples (https://github.com/openfga/openfga/pull/1517) support is enabled by default and the experimental flag for it has been dropped (https://github.com/openfga/openfga/pull/1520) Bumped to Go 1.21.9 (https://github.com/openfga/openfga/pull/1523) Patch - a critical issue where Check and ListObjects APIs returns incorrect results for some models and tuples. See the CVE report for more details. Fix the count of datastore reads in the Check API () Fix the correct default used for dispatch throttling () Bumped up the `grpc-health-probe` dependency in the published Docker image to the latest release which fixes some vulnerabilities () Add homebrew release job by @chenrui333 () Include calls to ListObjects and StreamedListObjects methods in the `dispatch_count` histogram () Added `requestdurationms` histogram which has `datastorequerycount` and `dispatch_count` as dimensions () Added new flag `OPENFGAAUTHNOIDCISSUERALIASES` to specify oidc issuer aliases () - Thanks @le-yams! Added experimental support for modular models via `OPENFGA_EXPERIMENTALS=enable-modular-models` (). This will enable writing models that are split across multiple files. Added support for throttling dispatches (). This will throttle Check requests that are overly complex. You can turn on this feature via OPENFGADISPATCHTHROTTLINGENABLED and configured via OPENFGADISPATCHTHROTTLINGTHRESHOLD and OPENFGADISPATCHTHROTTLING_FREQUENCY Throw HTTP 400 when tuple condition is invalid instead of HTTP 500 () Fix model validation which threw error "no entrypoints defined" () Histogram `requestdurationbyquerycountms` will be removed in the next release, in favour of `requestduration_ms` () Thanks @lekaf974 for enhancing NewLogger with builder pattern options () Override option for timestamp in JSON logs () - thank you, @raj-saxena! OpenTelemetry tracing and attributes to check algorithm (, ) Dispatch count to check response metadata as a query complexity heuristic () Cycles detected during check now deterministically return with `{allowed:false}` (, ) Fix incorrect path for gPRC health check () The `AuthorizationModelReadBackend` interface method `FindLatestAuthorizationModelID` has changed to `FindLatestAuthorizationModel` for performance improvements. If you implement your own data store, you will need to make the following change: <table> <tr> <th>Before</th> <th>After</th> </tr> <tr> <td> ```go func (...) FindLatestAuthorizationModelID(ctx context.Context, storeID string) (string, error) { //...get model ID return modelID, nil } ``` </td> <td> ```go func (...) FindLatestAuthorizationModel(ctx context.Context, storeID string) (*openfgav1.AuthorizationModel, error) { //...get model return model.(*openfgav1.AuthorizationModel), nil } ``` </td> </tr> </table> Add ability to close all server resources through `server.Stop()` () Increase performance by removing redundant

calls in model validation () Fix the sorting of contextual tuples when generating a cache key during check () Patch - a critical issue where issuing many `ListObjects` API calls that hit the `--listObjects-deadline` setting can lead to an out of memory error. See the CVE report for more details Goroutine leak in ListObjects because of a leak in ReverseExpand () Reduce goroutine overhead in ListObjects () Added `openfga` prefix to custom exported Prometheus metrics > This change may impact existing deployments of OpenFGA if you're integrating with the metrics reported by OpenFGA. Custom metrics reported by the OpenFGA server are now prefixed with `openfga`. For example, `requestdurationbyquerycountms ` is now exported as `openfgarequestdurationbyquerycountms`. Support for cancellation/timeouts when evaluating Conditions () Tracing span info for Condition evaluation () Resolve rewrites involving exclusion (e.g. `but not`) more deterministically in Check () Record span errors correctly in Check, ListObjects, and StreamedListObjects () Log request validation errors correctly () Enable support for Conditional Relationship Tuples by default. () Added stricter gRPC server max message size constraints () We changed the default gRPC max message size (4MB) to a stricter 512KB to protect the server from excessively large request `context` fields. This shouldn't impact existing clients since our calculated max message size should be much smaller than 512KB given our other input constraints. Bumped up to Go 1.21.5 () Reorder protobuf fields for persisted Assertions () Assertions written on or after v1.3.8 should be re-written to resolve some binary encoding issues that were introduced. Handle floating point conversion errors in conditions () Avoid panic when processing a nil set of writes () - thanks @stgraber! Decoding of null conditions in SQL storage implementations () Experimental support for ABAC Conditional Relationships. To enable experimental support for ABAC Conditional Relationships you can pass the `enable-conditions` experimental flag. For example, `openfga run --experimentals=enable-conditions`. The upcoming `v1.4.0` release will introduce official support for this new feature. For more information please see our . The `v1.4.0` release will have more official documentation on . > If you enable experimental support for ABAC and introduce models and/or relationship tuples into the system and then choose to rollback to a prior release, then you may experience unintended side-effects. Care should be taken! > > Read on for more information. If you introduce a model with a condition defined in a relation's type restriction(s) and then rollback to a prior OpenFGA release, then the model will be treated as though the conditioned type restriction did not exist. ``` model schema 1.1 type user type document relations define viewer: [user with somecondition] condition somecondition(x: int) { x < 100 } ``` and then you rollback to `v1.3.7` or earlier, then the model above will be treated equivalently to ``` model schema 1.1 type user type document relations define viewer: [user] ``` Likewise, if you write a relationship tuple with a condition and then rollback to a prior release, then the tuple will be treated as an unconditioned tuple. ``` document:1#viewer@user:jon, {condition: "somecondition"} ``` will be treated equivalently to `document:1#viewer@user:jon` in `v1.3.7` or earlier. That is, `Check(document:1#viewer@user:jon)` would return `{allowed: true}` even though at the tuple was introduced it was conditioned. Minimum datastore schema revision check in the server's health check () Each OpenFGA release from here forward will explicitly reference a minimum datastore schema version that is required to run that specific release of

If OpenFGA operators have not migrated up to that revision then the server's health checks will fail. Username/password configuration overrides for the `openfga migrate` entrypoint (). Thanks for the contribution @martin31821! Similar to the server's main entrypoint `openfga run`, you can now override the datastore username and password with environment variables. when running the `openfga migrate` utility. Healthcheck definitions in Dockerfile (). Thanks @Siddhant-K-code! Database iterators yielded by the RelationshipTupleReader storage interface now accept a `context` parameter which allows iteration to be promptly terminated () We have noticed improvements in query performance by adding this because once a resolution path has been found we more quickly cancel any further evaluation by terminating the iterators promptly. Improved tuple validation peformance with precomputation of TTUs () Refactored the commands in the `pkg/server/commands` package to uniformly use the Options builder pattern (). Thanks for the contribution @ilaleksin! Upgraded to Go `1.21.4` (). Thanks @tranngoclam! If two requests were made with the same request body and contextual tuples but the order of the contextual tuples differed, then the cache key that is produced is now the same.() Use `NoOp` TracerProvider if tracing is disabled ( and ) Bumped up the `grpc-health-probe` dependency to the latest release which fixed some vulnerabilities. Provenance manifests generation (`openfga.intoto.jsonl``) for verification of release artifacts with SLSA attestations. Removed the experimental flag `check-query-cache`. If you wish to enable the Check query cache you no longer need the experimental flag. Export metrics from MySQL and Postgres () To export datastore metrics, set `OPENFGAMETRICSENABLED=true` and `OPENFGADATASTOREMETRICS_ENABLED=true`. Return all results when `OPENFGALISTOBJECTSMAXRESULTS=0` () Promptly return if max results are met before deadline in ListObjects () Fix sort order on ReadChanges () Write Authorization Models in a single database row () :warning: In order to avoid downtime, we recommend upgrading to at least v1.3.3 before upgrading to v1.3.5. This is the second of a series of releases that will progressively introduce changes via code and database migrations that will allow authorization models to be stored in a single database row. See . Incorrect string in model validation error message () Incorrect results can be returned by Check API when passing in contextual tuples and the `check-query-cache` experimental flag is turned on () Bumped up to Go 1.21.3 () Patches . See the CVE for more details Configurable size limit for Authorization Models () We've introduced a new size limit for authorization models, provided a consistent behavior across datastores, which defaults to `256KB`. This can be configured by using the `--max-authorization-model-size-in-bytes` flag. Reduce use of GOB in encoded cache key () Move standalone server config defaults () Persist Authorization Models serialized protobuf in the database () In the next series of releases will progressively introduce changes via code and database migrations that will allow authorization models to be stored in a single database row. See . Support TLS for OTLP trace endpoint () - thanks @matoous Configurable limits to database reads per ListObjects query () Datastore query count labels to traces and query latency histogram in ListObjects () GitHub workflow to check Markdown links () - thanks @sanketrai1 Change response code to internal error for concurrency conflicts () Use slices and maps packages from

() - thanks @tranngoclam Moved request validations to RPC handlers so library integrations benefit (, ) Refactored internal usages of ConnectedObjects to ReverseExpand () Expose validation middleware () Upgrade grpc validator middleware to the latest v2 package () - thanks @tranngoclam Patches - see the CVE for more details [BREAKING] If your model contained cycles or a relation definition that has the relation itself in its evaluation path, then Checks and queries that require evaluation will no longer be evaluated on v1.3.2+ and will return errors instead. You will need to update your models to remove the cycles. Count datastore queries involved in Check resolution metadata () OpenFGA request logs and traces will now include a field `datastorequerycount` that shows how many queries were involved in a single Check resolution. Histogram metric to report the `datastorequerycount` per Check () This new metric can be used to report percentiles of the number of database queries required to resolve Check requests. Check request duration histogram labeled by method and datastore query count () The `requestdurationbyquerycountms` metric reports the total request duration (in ms) labelled by the RPC method and ranges of observations for the `datastorequery_count`. This metrics allows operators of an OpenFGA server to report request duration percentiles for Check requests based on the number of database queries that were required to resolve the query. Optimize Check to avoid database lookups in some scenarios () CachedCheckResolver for caching Check subproblems () This experimental feature adds new caching capabilities to the OpenFGA server. It is an "opt-in" feature and thus must be enabled. To enable this feature you must specify the experimental flag `check-query-cache` and set the `--check-query-cache-enabled=true` flag. ```shell openfga run --experimentals check-query-cache --check-query-cache-enabled=true ``` Server request logs now include the `user-agent` () Default Check and ListObjects concurrency read limits () In our last release we modified the default behavior of Check and ListObjects such that it limits/restricts the degree of concurrency that is allowed for a single request. This change was unintended. This release reverts the default behavior back to unbounded concurrency limits (the prior default). The change mostly affects those using OpenFGA as a library. Bumped up to Go 1.21 () Patches - see the CVE for more details Bounded concurrency limiter for Check and ListObjects queries (, ) New server configurations can be provided to limit/bound the amount of concurrency that is allowed during query evaluation. These settings can help reduce the impact/burden that a single query (e.g. Check, ListObjects, etc..) can have on the underlying database and OpenFGA server. `--maxConcurrentReadsForListObjects` - The maximum allowed number of concurrent reads in a single ListObjects query. `--maxConcurrentReadsForCheck` - The maximum allowed number of concurrent reads in a single Check query. `--resolveNodeBreadthLimit` - Defines how many nodes on a given level can be evaluated concurrently in a Check resolution tree. Jaeger persistent storage for traces in `docker-compose.yaml` () - thanks @Azanul Disable default debug level-logging in `retryablehttp` client () - thanks @KlausVii ) Problem* - Previously we depended on , but they recently deprecated protobuf imports served from the `go.buf.build` domain (see ). OpenFGA builds are currently broken as a result of this. Change* - We switched our protobuf API dependency from `go.buf.build/openfga/go/openfga/api/openfga/v1` to

So we no longer use Buf remote generated packages in favor of packages we managed in the repository. This fixes existing build issues. Impact* - Developers using the OpenFGA as a library or the gRPC API must change their protobuf dependency from `go.buf.build/openfga/go/openfga/api/openfga/v1` to `github.com/openfga/api/proto/openfga/v1`. A global find/replace and package dependency update should fix it. Here's a diff demonstrating the changes for a Go app, for example: ```go import ( ... openfgav1 "go.buf.build/openfga/go/openfga/api/openfga/v1" openfgav1 "github.com/openfga/api/proto/openfga/v1" ) ``` Refactor the `Server` constructor to use the options builder pattern () ```go import ( openfga "github.com/openfga/openfga/pkg/server" ) s := openfga.New( &server.Dependencies{...}, &server.Config{...}, ) ``` becomes ```go import ( openfga "github.com/openfga/openfga/pkg/server" ) var opts []openfga.OpenFGAServiceV1Option s := openfga.MustNewServerWithOpts(opts...) ``` Optimizations for and for models involving intersection (`and`) and exclusion (`but not`) () Cache model validation results on first model load () Cache inflight requests when looking up any authorization model () Update postgres max connections in docker compose file () Official Homebrew installation instructions () - thanks @chenrui333 The `--verbose` flag has been added to the `openfga migrate` command () The `openfga validate-models` CLI command has been introduced to validate all models across all stores () Updated the version of the `grpc-health-probe` binary included in OpenFGA builds () Cache inflight requests when looking up the latest authorization model () Validation of models with non-zero entrypoints () Remove unintended newlines in model validation error messages () - thanks @Galzzly Patches - additional model validations are now applied to models that can lead to the vulnerability. See the CVE report for more details, and don't hesitate to reach out if you have questions. Streaming ListObjects has no limit in number of results returned () Add Homebrew release stage to goreleaser's release process () Avoid DB connection churning in unoptimized ListObjects () Ensure ListObjects respects configurable ListObjectsDeadline () In Write, throw 400 instead of 500 error if auth model ID not found () Performance improvements when loading the authorization model () Ensure Check evaluates deterministically on the eval boundary case () ) Correct permission and location for gRPC health probe in Docker image (#697) OpenFGA with Postgres is now considered stable and ready for production usage. MySQL migration script errors during downgrade (#664) Release artifacts are now signed and include a Software Bill of Materials (SBOM) () The SBOM (Software Bill of Materials) is included in each GitHub release using and is exported in format. Developers will be able to verify the signature of the release artifacts with the following workflow(s): ```shell wget https://github.com/openfga/openfga/releases/download/<tag>/checksums.txt cosign verify-blob \ --certificate-identity 'https://github.com/openfga/openfga/.github/workflows/release.yml@refs/tags/<tag>' \ --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \ --cert https://github.com/openfga/openfga/releases/download/<tag>/checksums.txt.pem \ --signature https://github.com/openfga/openfga/releases/download/<tag>/checksums.txt.sig \ ./checksums.txt ``` If the `checksums.txt` validation succeeds, it means the checksums included in the release were not tampered with, so we can use it to verify the hashes of other files using the `sha256sum` utility. You can then download any file you want from the release, and verify it with, for example: ```shell wget https://github.com/openfga/openfga/releases/download/<tag>/openfga<version>linux_amd64.tar.gz.sbom wget https://github.com/openfga/openfga/releases/download/<tag>/openfga<version>linux_amd64.tar.gz sha256sum --ignore-missing -c checksums.txt ``` And both should say "OK". You can then inspect the .sbom file to see the entire dependency tree of the binary. Developers can also verify the Docker image

Cosign actually embeds the signature in the image manifest, so we only need the public key used to sign it in order to verify its authenticity: ```shell cosign verify -key cosign.pub openfga/openfga:<tag> ``` `openfga migrate` now accepts reading configuration from a config file and environment variables like the `openfga run` command () - thanks @suttod! The `--trace-service-name` command-line flag has been added to allow for customizing the service name in traces () - thanks @jmiettinen Postgres and MySQL implementations have been fixed to avoid ordering relationship tuple queries by `ulid` when it is not needed. This can improve read query performance on larger OpenFGA stores () Synchronize concurrent access to in-memory storage iterators () Improve error logging in the `openfga migrate` command () Fix middleware ordering so that `requestid` middleware is registered earlier () Bumped up to Go version 1.20 () Default model schema versions to 1.1 () In preparation for sunsetting support for models with schema version 1.0, the will now interpret any model provided to it as a 1.1 model if the `schema_version` field is omitted in the request. This shouldn't affect default behavior since 1.0 model support is enabled by default. Correct migration path for mysql in `openfga migrate` () The `v0.4.1` release includes everything in `v0.4.0` which includes breaking changes, please read the for more details. Fix ListObjects not returning objects a user has access to in some cases (openfga/openfga#637) Note: the 0.4.0 release was held due to issues discovered after the release was cut. [BREAKING] Disable schema 1.0 support, except if appropriate flags are set (openfga/openfga#613) As of this release, OpenFGA no longer allows writing or evaluating schema `v1.0` models by default. If you need support for it for now, you can use the: `OPENFGAALLOWWRITING10_MODELS`: set to `true` to allow `WriteAuthorizationModel` to accept schema `v1.0` models. `OPENFGAALLOWEVALUATING10_MODELS`: set to `true` to allow `Check`, `Expand`, `ListObjects`, `Write` and `WriteAssertions` that target schema `v1.0` models. `ReadAuthorizationModel`, `ReadAuthorizationModels` and `ReadAssertions` are unaffected and will continue to work regardless of the target model schema version. Note that these flags will be removed and support fully dropped in a future release. Read the for more details. Add OpenFGA version command to the CLI () Add `timeout` flag to `migrate` command () Improve the speed of Check for 1.1 models by using type restrictions ((, () Various important fixes to the experimental ListObjects endpoint Improve readUsersets query by dropping unnecessary sorting (,() Fix null pointer exception if computed userset does not exist () Fix race condition in memory store () Ensure no objects returned that would not have been allowed in Checks () Reverse expansion with indirect computed userset relationship () Improved tests (, , , ) Tuning of OTEL parameters () Fix tracing in Check API () Use chainguard images in Dockerfile () Contextual tuple propagation in the unoptimized ListObjects implementation () Re-release of `v0.3.5` because the go module proxy cached a prior commit of the `v0.3.5` tag. for Health Checks () OpenFGA containers now include an embedded `grpchealthprobe` binary that can be used to probe the Health Check endpoints of OpenFGA servers. Take a look at the file for an example. Improvements to telemetry: logging, tracing, and metrics (, , , ) We have added Prometheus as the standard metrics provided for OpenFGA and provide a way to launch Grafana to view the metrics locally. See for more

We've improved the attributes of various trace spans and made sure that trace span names align with the functions they decorate. Our logging has been enhanced with more logged fields including request level logging which includes a `requestid` and `storeid` field in the log message. These features will allow operators of OpenFGA to improve their monitoring and observability processes. Nightly releases () - thanks @Siddhant-K-code! You should now be able to run nightly releases of OpenFGA using `docker pull openfga/openfga:nightly` Undefined computed relations on tuplesets now behave properly () If you had a model involving two different computed relations on the same tupleset, then it's possible you may have received an internal server error if one of the computed relations was undefined. For example, ``` type document relations define parent as self define viewer as x from parent or y from parent type folder relations define x as self type org relations define y as self ``` Given the tuple `{ user: "org:contoso", relation: "parent", object: "document:1" }`, then `Check({ user: "jon", relation: "viewer", object: "document:1" })` would return an error prior to this fix because the `x` computed relation on the `document#parent` tupleset relation is not defined for the `org` object type. Eliminate duplicate objects in ListObjects response () Fixed the environment variable mapping (). For the full list of environment variables see . Fix for stack overflow error in ListObjects (). Thank you for reporting the issue @wonderbeyond! Added OpenTelemetry tracing () The ReadTuples endpoint has been removed (). Please use with no tuple key instead (e.g. `POST /stores/<store_id>/read` with `{}` as the body). Environment variable names have been updated (). For example, `OPENFGAMAXTUPLESPERWRITE` instead of `OPENFGA_MAXTUPLESPERWRITE`. For the full list please see . The old form still works but is considered deprecated and should not be used anymore. Optimized ListObjects is now on by default () (`--experimentals="list-objects-optimized"` is no longer needed) Avoid connection churn in our datastore implementations () The default values for `OPENFGADATASTOREMAXOPENCONNS` and `OPENFGADATASTOREMAXIDLECONNS` have been set to 30 and 10 respectively () ListObjects should no longer return duplicates () OpenTelemetry metrics integration with an `otlp` exporter () - thanks @AlexandreBrg! To export OpenTelemetry metrics from an OpenFGA instance you can now provide the `otel-metrics` experimental flag along with the `--otel-telemetry-endpoint` and `--otel-telemetry-protocol` flags. For example, ``` ./openfga run --experimentals=otel-metrics --otel-telemetry-endpoint=127.0.0.1:4317 --otel-telemetry-protocol=http ``` For more information see the official documentation on and . Type-bound public access support in the optimized ListObjects implementation (when the `list-objects-optimized` experimental feature is enabled) () Tuple validations for models with schema version 1.1 (, ) Evaluate rewrites on nested usersets in the optimized ListObjects implementation () Datastore configuration flags to control connection pool settings `--datastore-max-open-conns` `--datastore-max-idle-conns` `--datastore-conn-max-idle-time` `--datastore-conn-max-lifetime` These flags can be used to fine-tune database connections for your specific deployment of OpenFGA. Log level configuration flags `--log-level` (can be one of ['none', 'debug', 'info', 'warn', 'error', 'panic', 'fatal']) Support for Experimental Feature flags A new flag `--experimentals` has been added to enable certain experimental features in OpenFGA. For more information see . Patches - relationship reads now respect type restrictions from prior models (). This release comes with a few big changes: You can now write your models in the which the Playground and the can convert to the JSON syntax. Schema

allows for adding type restrictions to each assignable relation, and it can be used to indicate cases such as "The folder's parent must be a folder" (and so not a user or a document). This change also comes with breaking changes to how `` and `<type>:` are treated: `<type>:*` is interpreted differently according to the model version. v1.0 will interpret it as a object of type `<type>` and id `*`, whereas v1.1 will interpret is as all objects of type `<type>`. `*` is still supported in v1.0 models, but not supported in v1.1 models. A validation error will be thrown when used in checks or writes and it will be ignored when evaluating. Additionally, the change to v1.1 models allows us to provide more consistent validation when writing the model instead of when issuing checks. :warning: Note that with this release models with schema version 1.0 are now considered deprecated, with the plan to drop support for them over the next couple of months, please migrate to version 1.1 when you can. Read more about . The response has changed to include the object type, for example: ```json { "object_ids": [ "a", "b", "c" ] } ``` to ```json { "objects": [ "document:a", "document:b", "document:c" ] } ``` We have also improved validation and fixed support for Contextual Tuples that were causing inaccurate responses to be returned. :warning:This endpoint is now marked as deprecated, and support for it will be dropped shortly. Please use Read with no tuple key instead. Patches Multi-platform container build manifests to releases () Read RPC returns correct error when authorization model id is not found () Throw error if `http.upstreamTimeout` config is less than `listObjectsDeadline` () Patches , , and TLS certificate config path mappings () Error message when a `user` field is invalid () host:port mapping with unspecified host () Wait for connection to postgres before starting () Update Go to 1.19 Support for MySQL storage backend (). Thank you @MidasLamb! Allow specification of type restrictions in authorization models (). Note: Type restriction is not enforced yet, this just allows storing them. Tuple validation against type restrictions in Write API () Upgraded the Postgres storage backend to use pgx v5 () Close database connections after migration () Race condition in streaming ListObjects (, ) Reject direct writes if only indirect relationship allowed (). Thanks @dblclik! Log internal errors at the grpc layer () Authorization model validation () Bug in `migrate` command () Skip malformed tuples involving tuple to userset definitions () Support Check API calls on userset types of users () Add backoff when connecting to Postgres () Improve logging of internal server errors () Use Postgres in the sample Docker Compose file () Emit authorization errors () Telemetry in Check and ListObjects APIs () ListObjects API: respect the value of ListObjectsMaxResults () The ListObjects API provides a way to list all of the objects (of a particular type) that a user has a relationship with. It provides a solution to the use case for access-aware filtering on smaller object collections. It implements the . This addition brings with it two new server configuration options `--listObjects-deadline` and `--listObjects-max-results`. These configurations help protect the server from excessively long lived and large

> If `--listObjects-deadline` or `--listObjects-max-results` are provided, the endpoint may only return a subset of the data. If you provide the deadline but returning all of the results would take longer than the deadline, then you may not get all of the results. If you limit the max results to 1, then you'll get at most 1 result. Support for presharedkey authentication in the Playground () The embedded Playground now works if you run OpenFGA using one or more preshared keys for authentication. OIDC authentication remains unsupported for the Playground at this time. `migrate` CLI command () The `migrate` command has been added to the OpenFGA CLI to assist with bootstrapping and managing database schema migrations. See the usage for more info. ``` openfga migrate -h The migrate command is used to migrate the database schema needed for OpenFGA. Usage: openfga migrate [flags] Flags: --datastore-engine string (required) the database engine to run the migrations for --datastore-uri string (required) the connection uri of the database to run the migrations against (e.g. 'postgres://postgres:password@localhost:5432/postgres') -h, --help help for migrate --version uint the version to migrate to (if omitted the latest schema will be used) ``` Issue with embedded Playground assets found in the `v0.1.5` released docker image () Support for defining server configuration in `config.yaml`, CLI flags, or env variables (, , ) `v0.1.5` introduces multiple ways to support a variety of server configuration strategies. You can configure the server with CLI flags, env variables, or a `config.yaml` file. Server config will be loaded in the following order of precedence: CLI flags (e.g. `--datastore-engine`) env variables (e.g. `OPENFGADATASTOREENGINE`) `config.yaml` If a `config.yaml` file is provided, the OpenFGA server will look for it in `"/etc/openfga"`, `"$HOME/.openfga"`, or `"."` (the current working directory), in that order. Support for grpc health checks () `v0.1.5` introduces support for the . The server's health can be checked with the grpc or HTTP health check endpoints (the `/healthz` endpoint is just a proxy to the grpc health check RPC). For example, ``` grpcurl -plaintext \ -d '{"service":"openfga.v1.OpenFGAService"}' \ localhost:8081 grpc.health.v1.Health/Check ``` or, if the HTTP server is enabled, with the `/healthz` endpoint: ``` curl --request GET -d '{"service":"openfga.v1.OpenFGAService"}' http://localhost:8080/healthz ``` Profiling support (pprof) () You can now profile the OpenFGA server while it's running using the profiler. To enable the pprof profiler set `profiler.enabled=true`. It is served on the `/debug/pprof` endpoint and port `3001` by default. Configuration to enable/disable the HTTP server () You can now enable/disable the HTTP server by setting `http.enabled=true/false`. It is enabled by default. Env variables have a new mappings. Please refer to the file for a description of the new configurations or `openfga run -h` for the CLI flags. Env variables are mapped by prefixing `OPENFGA` and converting dot notation into underscores (e.g. `datastore.uri` becomes `OPENFGADATASTOREURI`). goroutine leaks in Check resolution. () OpenFGA Playground support () CORS policy configuration () Request validation middleware Postgres startup script TLS support for both the grpc and HTTP servers Configurable logging formats including `text` and `json` formats OpenFGA CLI with a preliminary `run` command to run the server Initial working implementation of OpenFGA APIs (Check, Expand, Write, Read, Authorization Models, etc..) Postgres storage adapter implementation Memory storage adapter implementation Early support for preshared key or OIDC authentication methods