Go Client API

First, install the go-oso-cloud package:

Before going through this guide, make sure you follow the Oso Cloud Quickstart to get your Oso Cloud API Key properly set in your environment.

Instantiating an Oso Cloud client

The Oso Cloud client provides an oso.NewClient function that takes your Oso Cloud URL and API key:

Specifying an Oso Fallback host

If you have deployed Oso Fallback nodes to your infrastructure, you may specify the host when instantiating the Oso Cloud client.

Passing application entities into the client

Under the hood, Oso Cloud represents an entity in your application as a combination of a type and an ID, which together uniquely identify the entity. The Go client represents these entities as oso.Value structs with both Type and ID properties. For example:

For convenience, you may prefer to use the oso.NewValue helper function:

You will pass structs like these into nearly every function call you make to the Go client.

Wrapping primitive values

To construct facts whose arguments have primitive values, use the oso.String, oso.Boolean, and oso.Integer helpers. These helpers create Values that wrap Go's built-in string, bool, and int64 types, and which correspond to the built-in Polar String, Boolean, and Integer primitives.

Centralized Authorization Data API

Oso Cloud clients provide an API to manage authorization data stored directly in Oso Cloud.

Add fact: osoClient.Insert(fact)

Adds the given fact to Oso Cloud. Example:

osoClient.Insert(oso.NewFact(
  "has_role",
  oso.NewValue("User", "bob"),
  oso.String("owner"),
  oso.NewValue("Organization", "acme")
))

Delete fact: osoClient.Delete(pattern)

Deletes a fact, or all facts matching the given fact pattern. Does not return an error if no facts match the given fact or pattern.

Example:

You can delete many facts at once by passing in a FactPattern. The arguments in the pattern can be a Value (matching arguments of that exact value at the given position), a ValueOfType (matching arguments of the given type at the given position), or nil (matching any argument at the given position).

Example:

Transactionally delete and add facts: osoClient.Batch(fn)

Allows deleting and inserting many facts in one atomic transaction. Deletions and insertions are run in the order they appear in the callback. Example:

As in calls to Delete, you may pass FactPatterns with wildcards (nil) and type-constrained wildcards (ValueOfType) into calls to BatchTransaction.Delete.

List facts: osoClient.Get(pattern)

Lists facts that are stored in Oso Cloud. Can be used to check the existence of a particular fact, or used to fetch all facts that have a particular argument:

You can also use oso.ValueOfType to get facts with an argument of a certain type:

Check API

Context facts

The Check API lets you provide context facts with each request. When Oso Cloud performs a check, it considers the request's context facts in addition to any other centralized authorization data. Context facts are only used in the API call in which they're provided-- they do not persist across requests.

For more details, see Context Facts.

Check a permission: osoClient.Authorize(actor, action, resource)

Determines whether or not an action is allowed, based on a combination of authorization data and policy logic. Example:

You may use osoClient.AuthorizeWithContext to provide a slice of context facts. Example:

List authorized resources: osoClient.List(actor, action, resourceType)

Fetches a list of resource IDs on which an actor can perform a particular action. Example:

You may use osoClient.ListWithContext to provide a slice of context facts. Example:

List authorized actions: osoClient.Actions(actor, resource)

Fetches a list of actions which an actor can perform on a particular resource. Example:

You may use osoClient.ActionsWithContext to provide a slice of context facts. Example:

Query for any rule: osoClient.BuildQuery(queryFact)

Query Oso Cloud for any predicate and any combination of concrete and wildcard arguments. Unlike osoClient.Get, which only lists facts you've added, you can use osoClient.BuildQuery to list derived information about any rule in your policy. Example:

Query Builder API

The osoClient.BuildQuery() API is a builder-style API where you chain methods to construct a query and then execute it.

osoClient.BuildQuery(queryFact)

The osoClient.BuildQuery() function takes the name of the rule you want to query and a list of arguments. The arguments can be concrete values (e.g., oso.String("read") or oso.NewValue("User", "bob")) or type-constrained variables constructed via the TypedVar function:

Note: once you've finished building up your query, you must call an Evaluate* method to run it and get the results.

QueryBuilder.And(queryFact)

This function adds another condition that must be true of the query results.

For example:

Note: once you've finished building up your query, you must call an Evaluate* method to run it and get the results.

QueryBuilder.In(variable, values)

This function requires a given TypedVar query variable to be included in a given set of values. You can only call In once per variable per query. Calling In a second time with the same variable on the same query builder will throw an error.

For example:

Note: once you've finished building up your query, you must call an Evaluate* method to run it and get the results.

QueryBuilder.WithContextFacts(contextFacts)

This function adds the given context facts to the query. For example:

For more information on context facts, see this section.

Note: once you've finished building up your query, you must call an Evaluate* method to run it and get the results.

QueryBuilder.EvaluateExists()

This function evaluates the built query, fetching the results from Oso.

Returns a boolean representing if the given conditions in the query were satisfied.

QueryBuilder.EvaluateValues(variable)

This function evaluates the built query, fetching the results from Oso.

Returns a slice of values for the given variable. For example:

QueryBuilder.EvaluateCombinations(variables)

This function evaluates the built query, fetching the results from Oso.

Returns a slice of tuples of values for the given variables. For example:

QueryBuilder.Evaluate(&result, shape)

This function evaluates the built query, fetching the results from Oso.

The returned value is written into the passed &result argument. The type of this result varies based on the type of the shape argument you pass in.

• If you pass nil, this function writes a boolean. For example:

  
  

  var allowed bool

  err := osoClient.

  BuildQuery(oso.NewQueryFact("allow", actor, action, resource)).

  Evaluate(&allowed, nil)

  // => true if the given actor can perform the given action on the given resource

  
  

• If you pass a single TypedVar query variable, this function writes a slice of values for that variable. For example:

  
  

  action := oso.TypedVar("String")

  var actions []string

  actions := osoClient.

  BuildQuery(oso.NewQueryFact("allow", actor, action, resource)).

  Evaluate(&actions, action)

  // => all the actions the actor can perform on the given resource- eg. ["read", "write"]

  
  

• If you pass a slice of TypedVar query variables, this function writes a slice of tuples of values for those variables. For example:

  
  

  action := oso.TypedVar("String")

  repository := oso.TypedVar("Repository")

  var pairs [][]string

  err := osoClient.

  BuildQuery(oso.NewQueryFact("allow", actor, action, repository))

  Evaluate(&pairs, []oso.Variable {action, repository})

  // => a slice of pairs of allowed actions and repo IDs-

  // eg. [["read", "acme"], ["read", "anvil"], ["write", "anvil"]]

  
  

• If you pass a dict mapping one TypedVar query variable (call it K) to another (call it V), this function writes a map grouping unique values of K to unique values of V for each value of K. For example:

  
  

  action := oso.TypedVar("String")

  repository := oso.TypedVar("Repository")

  var repoActions map[string][]string

  err := osoClient.

  BuildQuery(oso.NewQueryFact("allow", actor, action, repository))

  Evaluate(&repoActions, map[Variable]Variable{repository: action})

  // => a mapping of repo IDs to allowed actions-

  // eg. { "acme": ["read"], "anvil": ["read", "write"]}

  
  

Some queries have unconstrained results. For instance, maybe users with the admin role can read all Repository entities in your application. In this case, rather than returning an array containing the ID of every repository, Evaluate will write an array containing the string "*". For example:

Query Builder examples

Field-level access control

Checking a global permission

Fetching authorized actions for a collection of resources

Filtering out unauthorized resources from a collection

Filtering an authorize() query based on a relation

Learn more about how to query Oso Cloud.

Local Check API

The local check API lets you perform authorization using data that's distributed across Oso Cloud and your own database.

After creating your Local Authorization configuration, provide the path to the YAML file that specifies how to resolve facts in your database.

For more information, see Local Authorization.

List authorized resources with local data: osoClient.ListLocal(actor, action, resourceType, column)

Fetches a filter that can be applied to a database query to return just the resources on which an actor can perform an action. Example with GORM (opens in a new tab):

You may use the GORM query interface (opens in a new tab) to combine this authorization filter with other things such as ordering and pagination.

You may use osoClient.ListLocalWithContext to provide a slice of context facts. Example:

Check a permission with local data: osoClient.AuthorizeLocal(actor, action, resource)

Fetches a query that can be run against your database to determine whether an actor can perform an action on a resource. Example with GORM (opens in a new tab):

You may use osoClient.AuthorizeLocalWithContext to provide a slice of context facts. Example:

List authorized actions with local data: osoClient.ActionsLocal(actor, resource)

Fetches a query that can be run against your database to fetch the actions an actor can perform on a resource. Example with GORM (opens in a new tab):

You may use osoClient.ActionsLocalWithContext to provide a slice of context facts. Example:

Query for any rule with local data: QueryBuilder

You can use the Query Builder to construct SQL queries that you can run against your database to answer arbitrary questions about authorization.

See the Query Builder API documentation for information on how to construct queries. Once you've built your query, instead of calling Evaluate (which would evaluate your query exclusively against data stored in Oso Cloud), call either EvaluateLocalSelect or EvaluateLocalFilter to construct a SQL query which you can run against your database.

Local Query API

QueryBuilder.EvaluateLocalSelect(columnNamesToQueryVars)

Fetches a complete SQL query representing the given Query Builder query. (See the Query Builder API documentation for information on how to construct queries.)

The argument to this function is a map, mapping the column names that will appear in the SELECT clause of the SQL query to the Query Builder variables whose values should be selected. For example, query.EvaluateLocalSelect(map[string]oso.Variable{"user_id": userVar}) will select all the authorized values of userVar (that is, all the values of userVar that satisfy the Query Builder query) into a column called "user_id".

If you pass in an empty map, the SQL query will return a single row selecting a boolean column called result. This column will be true when there's some combination of data in your database that can satisfy the given Query Builder query and false otherwise.

Note that each query variable can appear at most once in the columnNamesToQueryVars mapping. For example, query.EvaluateLocalSelect(map[string]oso.Variable{"user_id": userVar, "another_user_id": userVar}) will return an error, because userVar appears twice in the mapping parameter.

Note that column names will be double-quoted and are thus case-sensitive.

Limitations

EvaluateLocalSelect has the following limitations:

• Queries that would return a wildcard for one of the selected query variables are currently unsupported.

  Example:

  policy.polar

  
  

  has_permission(user: User, "read", _: Repo) if is_global_admin(user);

  
  

QueryBuilder.EvaluateLocalFilter(columnName, queryVar)

Fetches a SQL fragment representing the given Query Builder query that you can embed in the WHERE clause of some other SQL query. Use this to filter out unauthorized results from your SQL query.

(See the Query Builder API documentation for information on how to construct queries.)

columnName is the name of the column you want to filter in your SQL query, and queryVar is the query variable to filter against. For example, query.EvaluateLocalFilter("user_id", userVar) will return a SQL fragment of the form "user_id" IN (...), constraining the column "user_id" to the authorized values of userVar.

Note that the column name will be double-quoted and is thus case-sensitive.

Local Query Examples

These examples all use GORM (opens in a new tab) to execute the returned SQL queries, but you can use any database client you prefer.

Field-level access control

Checking a global permission

Fetching authorized actions for a paginated collection of resources

Filtering an authorize() query based on a relation

Filtering on users who can read a certain resource

Policy API

Update the active policy: osoClient.Policy(policy)

Updates the policy in Oso Cloud. The string passed into this method should be written in Polar. Example:

This command will run any tests defined in your policy. If one or more of these tests fail, your policy will not be updated.

Get policy metadata: osoClient.GetPolicyMetadata()

Returns metadata about the currently active policy. Example:

returns:

See the Policy Metadata guide for more information on use cases.

Talk to an Oso engineer

If you'd like to learn more about using Oso Cloud in your app or have any questions about this guide, schedule a 1x1 with an Oso engineer. We're happy to help.

Get started with Oso Cloud →