Attribute-based access control (ABAC)
This tutorial assumes that you have completed the Quick Start with FaunaDB tutorial. |
Attribute-based access control (ABAC) is an alternative to an all-or-nothing security model, and is commonly used in applications to restrict access to specific data based on the user’s role. ABAC is an extension of role-based access control (RBAC), where users are assigned roles that grant them specific privileges. The benefit of ABAC is that privileges can be dynamically determined based on attributes of the user, the documents to be accessed or modified, or context during a transaction (e.g. time of day).
In this tutorial, we introduce FaunaDB’s Attribute-Based Access Control (rBAC) feature by simulating an employee hierarchy, and employing a "smart" role that permits users to see their own salary, and managers to see their own salary and the salaries of users that report to them.
-
Create a new database
Open a terminal and run:
fauna create-database abac creating database abac created database 'abac' To start a shell with your new database, run: fauna shell 'abac' Or, to create an application key for your database, run: fauna create-key 'abac'
-
Connect to the new database using FaunaDB Shell
Start a FaunaDB Shell session:
fauna shell abac Starting shell for database abac Connected to http://faunadb:8443 Type Ctrl+D or .exit to exit the shell
-
Create three separate collections (classes)
CreateCollection({ name: "users" }) CreateCollection({ name: "salary" }) CreateCollection({ name: "user_subordinate" })
The
users
collection is used to store the user details, while thesalary
collection is used to collect the salary information. Theuser_subordinate
collection is used to store the information of managers and their subordinates. -
Create three indexes
In FaunaDB, indexes are required for pagination or searching. Here, we create collection indexes on the
users
andsalary
collections, and a specific index to retrieve users by name.CreateIndex({ name: "all_users", source: Collection("users"), })
CreateIndex({ name: "user_by_name", source: Collection("users"), terms: [{ field: ["data", "name"] }], })
CreateIndex({ name: "all_salaries", source: Collection("salary"), })
-
Create user and salary data
Here, we create some
users
andsalary
data. Thesalary
collection stores the user reference as a foreign key. Theuser
collection also stores the user’s credentials, which is just a simple password for this tutorial.Map([ ["Bob", 95000], ["Joe", 60000], ["John", 70000], ["Peter", 97000], ["Mary", 120000], ["Carol", 150000] ], Lambda("data", Let( { user: Create(Collection("users"), { data: { name: Select(0, Var("data")) }, credentials: { password: "123" } }), salary: Select(1, Var("data")) }, Create(Collection("salary"), { data: { user: Select("ref", Var("user")), salary: Var("salary") }}) )))
-
Verify that the data is correct
Now that the data is created, let us query the two collections to check out the usernames and salaries.
Map( Paginate(Match(Index("all_salaries"))), Lambda("salaryRef", Let({ salary: Get(Var("salaryRef")), user: Get(Select(["data", "user"], Var("salary"))) }, { user: Select(["data", "name"], Var("user")), salary: Select(["data", "salary"], Var("salary")) } ) ) )
The above query should display the users and their salaries (the order of the results can vary):
{ data: [ { user: 'Carol', salary: 150000 }, { user: 'Peter', salary: 97000 }, { user: 'Joe', salary: 60000 }, { user: 'Bob', salary: 95000 }, { user: 'Mary', salary: 120000 }, { user: 'John', salary: 70000 } ] }
-
Create manager→user relationship data
Now that the basic data is created, we create a similar sample data associating managers and their subordinates
Map([ ["Bob", "Mary"], ["John", "Mary"], ["Peter", "Joe"] ], Lambda("data", Let( { user: Get(Match(Index("user_by_name"), Select(0, Var("data")))), manager: Get(Match(Index("user_by_name"), Select(1, Var("data")))) }, Create(Collection("user_subordinate"), { data: { user: Select("ref", Var("user")), reports_to: Select("ref", Var("manager")) }}) )))
Here, we see that Bob and John work for Mary, while Peter works for Joe. Once our access controls are in place, Bob should only be able to see his salary, but Mary should be able to see her salary as well as the salary for Bob and John.
-
Create an index for the
user_subordinate
collectionCreateIndex({ name: "is_subordinate", source: Collection("user_subordinate"), terms: [ { field: ["data", "user"] }, { field: ["data", "reports_to"] } ] })
-
Create a role that provides the appropriate privileges
CreateRole({ name: "normal_user", membership: { resource: Collection("users") }, privileges: [ { resource: Collection("users"), actions: { read: true } }, { resource: Index("all_users"), actions: { read: true } }, { resource: Index("all_salaries"), actions: { read: true } }, { resource: Collection("salary"), actions: { read: Query( Lambda("salaryRef", Let( { salary: Get(Var("salaryRef")), userRef: Select( ["data", "user"], Var("salary")) }, Or( Equals(Var("userRef"), Identity()), Exists( Match(Index("is_subordinate"), [Var("userRef"), Identity()]) ) )) ) ) } } ] })
This role employs a Lambda function that permits access to a user’s salary, and to the salaries of subordinates.
-
Verify salary access for a user
Now we can log in to the database as Bob and run the salary listing query. First we have to create a token for Bob:
Login(Match(Index("user_by_name"), "Bob"), { password: "123" })
The output should look similar to:
{ ref: Ref(Tokens(), "231651464569684480"), ts: 1557178902130000, instance: Ref(Collection("users"), "231651384582210048"), secret: 'fnEDNv3HmWACAAM2_aC3wAIAGOysa8knR3F3ZzvUkc0sq_O6chQ' }
Using the secret, we can log in to the database and run the user listing query. In a separate terminal, start a new FaunaDB Shell session, and be sure to copy the value of the
secret
field as the value of the--secret
argument in the following command:fauna shell --secret="fnEDNv3HmWACAAM2_aC3wAIAGOysa8knR3F3ZzvUkc0sq_O6chQ" Warning: You didn't specify a database. Starting the shell in the global scope. Connected to http://faunadb:8443 Type Ctrl+D or .exit to exit the shell
Then run this query:
Map( Paginate(Match(Index("all_salaries"))), Lambda("salaryRef", Let({ salary: Get(Var("salaryRef")), user: Get(Select(["data", "user"], Var("salary"))) }, { user: Select(["data", "name"], Var("user")), salary: Select(["data", "salary"], Var("salary")) }) ))
You should see the following output:
{ data: [ { user: 'Bob', salary: 95000 } ] }
So, we can see that Bob can only query his own salary.
-
Verify salary access for a manager
In the original FaunaDB Shell session, create a login token for Mary:
Login(Match(Index("user_by_name"), "Mary"), { password: "123" })
You should see output similar to the following:
{ ref: Ref(Tokens(), "231573285766169088"), ts: 1557104345000000, instance: Ref(Collection("users"), "231573095978109440"), secret: 'fnEDNv4fcEACAAM2_aC3wAIANL6untGn8nhY-NK2O90oHyIeWuY' }
In a new terminal, start a new FaunaDB Shell session, and be sure to copy the value of the
secret
field as the value of the--secret
argument in the following command:fauna shell --secret="fnEDNv4fcEACAAM2_aC3wAIANL6untGn8nhY-NK2O90oHyIeWuY" Warning: You didn't specify a database. Starting the shell in the global scope. Connected to http://faunadb:8443 Type Ctrl+D or .exit to exit the shell
Then run the salary lookup query:
Map( Paginate(Match(Index("all_salaries"))), Lambda("salaryRef", Let({ salary: Get(Var("salaryRef")), user: Get(Select(["data", "user"], Var("salary"))) }, { user: Select(["data", "name"], Var("user")), salary: Select(["data", "salary"], Var("salary")) }) ))
You should see the following output (the order may vary):
{ data: [ { user: 'Bob', salary: 95000 }, { user: 'Mary', salary: 120000 }, { user: 'John', salary: 70000 } ] }
Mary can see the salaries for herself, Bob, and John.
Was this article helpful?
We're sorry to hear that.
Tell us how we can improve!
documentation@fauna.com
Thank you for your feedback!