Java Client API

See the Oso Cloud Java client's Maven Central page (opens in a new tab) for instructions on how to add it to your project.

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 class that takes your 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 Java client represents these entities as Value objects with both type and id fields. For example:

You will pass objects like these into nearly every method call you make to the Java client.

Centralized Authorization Data API

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

Add fact: oso.insert(Fact)

Adds a single fact. Example:

Delete fact: oso.delete(Fact) / oso.delete(FactPattern)

Deletes facts. Does not throw an error if the fact(s) are not found.

To delete a single, specific fact, pass a Fact object:

To delete multiple facts matching a pattern, pass a FactPattern using ValuePattern.ANY or ValuePattern.ValueOfType as wildcards:

Transactionally delete and add facts: oso.batch(Consumer<BatchTransaction>)

Allows deleting and inserting many facts in one atomic transaction. Operations are performed in the order they appear in the consumer lambda. Example:

Get facts: oso.get(FactPattern)

Lists facts stored in Oso Cloud that match the provided FactPattern. Use ValuePattern.ANY or ValuePattern.ValueOfType as wildcards in the pattern. Returns a Fact[] array.

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: oso.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 provide a list of context facts as an optional fourth argument to this method. Example:

List authorized resources: oso.list(actor, action, resourceType)

Fetches a list of resource IDs (String[]) on which an actor can perform a particular action. Example:

You may provide a list of context facts as an optional fourth argument to this method. Example:

List authorized actions: oso.actions(actor, resource)

Fetches a list of actions (String[]) which an actor can perform on a particular resource. Example:

You may provide a list of context facts as an optional third argument to this method. Example:

Query for any rule: oso.buildQuery(predicate, ...args)

Query Oso Cloud for any predicate and any combination of concrete values and typed variables. Unlike oso.get, which only lists facts you've added, you can use oso.buildQuery to list derived information about any rule in your policy. Example:

Query Builder API

The oso.buildQuery() API returns a builder-style API where you chain methods to construct a query and then execute it.

oso.buildQuery(predicate, ...args)

The oso.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., new Value("read") or new Value("User", "bob")) or type-constrained variables constructed via the TypedVar class:

Note: Once you've finished building up your query, you must call evaluate to run it and get the results.

QueryBuilder.and(predicate, ...args)

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 evaluate 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 (List<String>). 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 evaluate to run it and get the results.

QueryBuilder.withContextFacts(contextFacts)

This function adds the given context facts (List<Fact>) 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 evaluate to run it and get the results.

QueryBuilder.evaluate(EvaluateArg)

This function evaluates the built query, fetching the results from Oso Cloud. The shape of the return value is determined by the EvaluateArg you provide. Use the static factory methods in EvaluateArgs to construct the desired argument structure.

• EvaluateArgs.exists(): Returns a Boolean indicating if the query is satisfiable.

  
  

  import com.osohq.oso_cloud.Oso;

  import com.osohq.oso_cloud.Value;

  import com.osohq.oso_cloud.QueryBuilder.EvaluateArgs;

  // ...

  Oso oso = new Oso(YOUR_API_KEY);

  Value actor = new Value("User", "bob");

  Value action = new Value("read");

  Value resource = new Value("Repository", "acme");

  Boolean allowed = oso

  .buildQuery("allow", actor, action, resource)

  .evaluate(EvaluateArgs.exists());

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

  
  

• EvaluateArgs.values(TypedVar variable): Returns a List<String> of values for that variable.

  
  

  import com.osohq.oso_cloud.Oso;

  import com.osohq.oso_cloud.Value;

  import com.osohq.oso_cloud.TypedVar;

  import com.osohq.oso_cloud.QueryBuilder.EvaluateArgs;

  import java.util.List;

  // ...

  Oso oso = new Oso(YOUR_API_KEY);

  Value actor = new Value("User", "bob");

  Value resource = new Value("Repository", "acme");

  TypedVar actionVar = new TypedVar("String");

  List<String> actions = oso

  .buildQuery("allow", actor, actionVar, resource)

  .evaluate(EvaluateArgs.values(actionVar));

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

  
  

• EvaluateArgs.map(TypedVar keyVariable, EvaluateArg valueArg): Returns a Map<String, SubT> where keys are unique values of the key variable, and values are the results of recursively evaluating the nested value argument (SubT). This allows arbitrarily nested structures.

  
  

  import com.osohq.oso_cloud.Oso;

  import com.osohq.oso_cloud.Value;

  import com.osohq.oso_cloud.TypedVar;

  import com.osohq.oso_cloud.QueryBuilder.EvaluateArgs;

  import java.util.List;

  import java.util.Map;

  // ...

  Oso oso = new Oso(YOUR_API_KEY);

  Value actor = new Value("User", "bob");

  TypedVar actionVar = new TypedVar("String");

  TypedVar repositoryVar = new TypedVar("Repository");

  Map<String, List<String>> repoToActions = oso

  .buildQuery("allow", actor, actionVar, repositoryVar)

  .evaluate(EvaluateArgs.map(repositoryVar, EvaluateArgs.values(actionVar)));

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

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

  // Example of deeply nested map: User -> Repo -> List<Action>

  TypedVar userVar = new TypedVar("User");

  Map<String, Map<String, List<String>>> userRepoActions = oso

  .buildQuery("allow", userVar, actionVar, repositoryVar)

  .evaluate(EvaluateArgs.map(userVar, EvaluateArgs.map(repositoryVar, EvaluateArgs.values(actionVar))));

  // => {"alice"={"acme"=["read"]}, "bob"={"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 a list containing the ID of every repository, evaluate will return a list 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 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: oso.listLocal(actor, action, resourceType, column)

Fetches a SQL query fragment (String) that can be applied to a database query's WHERE clause to return just the resources on which an actor can perform an action. Example with JPA:

You may provide a list of context facts as an optional fifth argument to this method. Example:

Check a permission with local data: oso.authorizeLocal(actor, action, resource)

Fetches a complete SQL query (String) that can be run against your database to determine whether an actor can perform an action on a resource. The query returns a single row with a single boolean column named allowed. Example with JPA:

You may provide a list of context facts as an optional fourth argument to this method. Example:

List authorized actions with local data: oso.actionsLocal(actor, resource)

Fetches a complete SQL query (String) that can be run against your database to fetch the actions (List<String>) an actor can perform on a resource. The query returns multiple rows, each with a single string column named action. Example with JPA:

You may provide a list of context facts as an optional third argument to this method. 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 (String) 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<String, TypedVar> where keys are the desired column names that will appear in the SELECT clause of the SQL query, and values are the Query Builder variables whose values should be selected. For example, query.evaluateLocalSelect(Map.of("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 or call the no-argument overload evaluateLocalSelect(), 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.of("user_id", userVar, "another_user_id", userVar)) will throw an IllegalArgumentException, because userVar appears twice in the mapping parameter.

Note that column names will be double-quoted and are thus case-sensitive in the generated SQL.

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);

  
  
  
  

  import com.osohq.oso_cloud.Oso;

  import com.osohq.oso_cloud.Value;

  import com.osohq.oso_cloud.TypedVar;

  import com.osohq.oso_cloud.ApiException;

  import java.util.Map;

  // ...

  Oso oso = new Oso(/*...*/);

  // Assume alice is a global admin, and can read *any* repo

  oso.insert(new Fact("is_global_admin", new Value("User", "alice")));

  // UNSUPPORTED: Attempt to query for each authorized user / repo pair

  TypedVar userVar = new TypedVar("User");

  TypedVar repoVar = new TypedVar("Repo");

  try {

  String sql = oso

  .buildQuery("allow", userVar, new Value("read"), repoVar)

  .evaluateLocalSelect(Map.of("user_id", userVar, "repo_id", repoVar));

  // => throws ApiException, because alice can read any repo, so this query would return

  // a wildcard for the repos alice can read

  } catch (ApiException e) {

  // Handle error

  }

  
  

QueryBuilder.evaluateLocalFilter(columnName, queryVar)

Fetches a SQL query fragment (String) 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 in the generated SQL.

Local query examples

These examples all use JPA's createNativeQuery 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: oso.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, an exception will be thrown and your policy will not be updated.

Get policy metadata: oso.policyMetadata()

Returns metadata about the currently active policy. Example:

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 →