Integrating Trino and Apache Ranger | by Aakash Nand | Towards Data Science

As demand for data grows day by day, the requirement for data security in an enterprise setup is increasing as well. In the Hadoop ecosystem, Apache Ranger has been a promising framework for data security with extensive plugins such as HDFS, Solr, Yarn, Kafka, Hive and many more. Apache Ranger added a plugin for prestosql in version 2.1.0 but recently PrestoSQL was rebranded as Trino and that broke the working prestosql plugin for Apache Ranger.
I have submitted a patch for this issue and there is already an open JIRA issue here but that will not stop us from integrating Trino with Apache Ranger. For this tutorial, I have built the Apache Ranger 2.1.0 with the Trino plugin. If you want to build the Apache Ranger from source code including the trino plugin you can refer to this GitHub repository on the branch ranger-2.1.0-trino and for this tutorial purpose, we will this Github repository.
Apache Ranger has three key components ranger-admin , ranger-usersync and ranger-audit . Let us get introduced to these components.
Note: Configuring ranger-usersync is out of scope for this tutorial and we will not use any usersync component for this tutorial.
Ranger Admin component is a UI component using which we can create policies for the different access levels. Ranger Admin requires a backend database, in our case we are using Postgres as the backend database for Ranger Admin UI.
Ranger Audit component collects and shows logs for each access event of the resource. Ranger supports two audit methods, solr and elasticsearch . We will use elasticsearch to store ranger audit logs which will be then displayed in the Ranger Audit UI as well.
Trino is a fast distributed query engine. It can connect to several data sources such as hive , postgres , oracle and so on. You can read more about Trino and Trino connectors in the official documentation here. For this tutorial, we will use the default catalog tpch which comes with dummy data.
Apache Ranger supports many plugins such as HDFS, Hive, Yarn, Trino etc. Each of these plugins needs to be configured on the host which is running that process. Trino-Ranger-Plugin is one component that will communicate with Ranger Admin to check and download the access policies which will be then synced with Trino Server. The downloaded policies are stored as JSON files on the Trino server and can be found under the path /etc/ranger/<service-name>/policycache so in this case the policy path is /etc/ranger/trino/policycache
The communication between the above components is explained in the following diagram.
The docker-compose file connects all of the above components.
Important points about docker-compose.yml
We have used named-docker-volumes ex: ranger-es-data , ranger-pg-datato persist data of the services such as elasticsearch and postgres even after a container restartThe pre-built tar files of Ranger-Admin and Ranger-Trino Plugin are available as release assets on this demo repository here.The ranger-Admin process requires a minimum of 1.5 GB of memory. The Ranger-Admin tar file contains install.properties and setup.sh . The setup.sh the script reads the configuration from install.properties . The following patch file describes configuration changes made to install.properties compared to the default version of install.propertiesfor Ranger-Admin component.
We have used named-docker-volumes ex: ranger-es-data , ranger-pg-datato persist data of the services such as elasticsearch and postgres even after a container restart
The pre-built tar files of Ranger-Admin and Ranger-Trino Plugin are available as release assets on this demo repository here.
The ranger-Admin process requires a minimum of 1.5 GB of memory. The Ranger-Admin tar file contains install.properties and setup.sh . The setup.sh the script reads the configuration from install.properties . The following patch file describes configuration changes made to install.properties compared to the default version of install.propertiesfor Ranger-Admin component.
4. Ranger-Trino-Plugin tar file also contains install.properties and enable-trino-plugin.sh script. One important point to note about the trino docker environment is that the configuration files and plugin directory are configured to different directory locations. The configuration is read from /etc/trino whereas plugins are loaded from /usr/lib/trino/plugins These two directories are important when configuring install.properties for Trino-Ranger-Plugin and hence some extra customization is required to the default script enable-trino-plugin.sh that comes with the Trino-Ranger-Plugin tar file to make it work with dockerized Trino. These changes are highlighted in the following patch file. Basically, these changes introduce two new custom variables INSTALL_ENV and COMPONENT_PLUGIN_DIR_NAME which can be configured in install.properties
5. install.properties file for Trino Ranger Plugin needs to be configured as shown in the following patch file. Please note that we are using two newly introduced custom variables to inform enable-plugin-script that Trino is deployed in the docker environment.
6. Finally, putting it all together in the docker-compose.yml as shown below. This file is also available in Github Repository here.
In this part, we will deploy docker-compose services and confirm the status of each component.
git clone https://github.com/aakashnand/trino-ranger-demo.git
$ cd trino-ranger-demo$ docker-compose up -d
Once we deploy services using docker-compose, we should be able to see four running services. We can confirm this by docker-compose ps
Let’s confirm that Trino and Ranger-Admin services are accessible on the following URLs
Ranger Admin: http://localhost:6080
Trino: http://localhost:8080
Elasticsearch: http://localhost:9200
Let's access Ranger-Admin UI and log in as admin user. We configured our admin user password rangeradmin1 in the above ranger-admin-install.properties file. As we can see in the following screenshot, by default, there is no trinoservice. Therefore, let's create a service with the name trino . The service name should match with the name defined in install.properties for Ranger-Admin
Please note the hostname in the JDBC string. From ranger-admin container trino is reachable at my-localhost-trino hence hostname is configured as my-localhost-trino
If we click on Test Connection we will get a Connection Failed error as shown below. This is because the Ranger-Admin process is already running and is still looking for a service with the nametrino which we have not created yet. It will be created once we click Add .
So let's add trino service and then click Test Connection again
Now Ranger-Admin is successfully connected to Trino 🎉
To check audit logs, navigate to audit from the top navigation bar and click Audit . We can see that audit logs are displayed 🎉 . Ranger-Admin and Elasticsearch are working correctly.
Now that we have finished the setup, it is time to create actual access policies and see it in action
When creating the trino service we used ranger-admin as username in the connection information. This creates default policies with this username and thus the ranger-adminuser will have super privileges
To understand the access scenario and create an access policy we need to create a test user. The Ranger usersync service syncs users, groups, and group memberships from various sources, such as Unix, File, or AD/LDAP into Ranger. Ranger usersync provides a set of rich and flexible configuration properties to sync users, groups, and group memberships from AD/LDAP supporting a wide variety of use cases. In this tutorial, we will manually create a test user from Ranger-Admin UI.
To create a user, let’s navigate to Settings → Users/Groups/Roles → Add New User
When creating a user we can choose different roles.
user role is the normal user
Admin role can create and manage policies from Ranger Admin UI.
Auditor role is read-only user role.
For the time being, let’s create a user with Admin role.
Let's confirm access for the user ranger-admin
As we can see ranger-admin user can access all the tables under schema tpch.sf10
Since we have not configured any policy for test-user if we try to access any catalog or execute any query, we should see an access denied message. Let's confirm this by executing queries from Trino CLI
Let’s create a policy that allows test-user access to tpch.sf10 to all tables.
We can also assign specific permissions on each policy, but for the time being let's create a policy with all permissions. After creating this policy, we have the following active policies.
Now let’s confirm the access again.
We are still getting access denied message. This is because Trino ranger policies need to be configured for each object level. For example, catalog level policy, catalog+schema level policy, catalog+schema+table level policy and information_schema policy. Let's add policy for the catalog level.
Let's confirm again with Trino CLI
We are still getting the error but the error message is different. Let's navigate to Ranger Audit Section to understand more about this.
We can see an entry that denied permission to a resource called tpch.information_schema.tables.table_schema . In Trino, information_schema is the schema which contains metadata about table and table columns. So it is necessary to add policy for information_schema as well. Access to information_schema is required for any user to execute the query in Trino, therefore, we can use the {USER} variable in Ranger policy that gives access to all users.
Let us confirm the access from Trino CLI again.
We still get access denied if we try to execute any SQL function. In the default policies section, all-functionspolicy (ID:3) is the policy that allows access to execute any SQL function. Since executing SQL function is a requirement for all users, Let’s edit the all-functionspolicy (ID:3) and add all users using the {USER}variable to give access to functions
So to summarize, to give access to test-user to ALL tables under sf10 we added three new policies and edited the default all-function policy.
Now we can access and execute queries for all tables for sf10 schema.
In the next step, let’s understand how to give access to test-user for a specific table under schema sf10
In the previous step, we configured policies to give access to ALL tables under sf10 schema and therefore, schema-level the policy was not necessary. To give access to a specific schema we need to add schema-level policy and then we can configure table-level the policy. So let us add schema-level a policy for tpch.sf10
Now let us edit sf10-all-tables-policy from all tables to specific table. We will configure a policy that will allow access to onlynation table
So finally we have the following active policies
Now let's execute queries from Trino CLI again for test-user.
test-user can now access the onlynation table from tpch.sf10 schema as desired.
If you have followed all the steps and reached this end, Congratulations 祝️, now you have understood how to configure Trino and Apache Ranger.
After the rebranding from PrestoSQL to Trino, the default plugin from Apache Ranger’s GitHub repository will NOT work with the new Trino as it is still referencing old io.prestosql packages. You can track this issue on JIRA here
Rebranded Trino plugin will not be made available in the new Ranger version 2.2.0. So meanwhile, please feel free to use this GitHub repository for building Apache Ranger from source code and this GitHub repository for getting started with Trino-Ranger integration.
Configuring Ranger policies for Trino is not so intuitive because we need to configure access policies for each level. There is an open issue regarding this on Trino’s repository here.
Nonetheless, it is recommended to configure some basic policies such as information_schema and all-functions with {USER} variable as these policies are necessary for any user to execute queries.
Due to the lack of good documentation and not so intuitive nature of the integration process, integrating Apache Ranger and Trino can be painful, but I hope this article makes it a bit easier. If you are using Trino, I highly recommend you to join Trino Community Slack for more detailed discussions. Thank you for reading.