Skip to content
This repository has been archived by the owner on May 20, 2021. It is now read-only.

Latest commit

 

History

History
37 lines (29 loc) · 1.98 KB

USER_ACCOUNTS.md

File metadata and controls

37 lines (29 loc) · 1.98 KB

User Accounts

Airpal has the ability to restrict access to data based on the schema and table it is in. These restrictions also support limiting access to views, based on the view's fully qualified name. This functionality is mostly provided by Apache Shiro, and is configured by specifying an INI file in the Airpal configuration under shiro > iniConfigs. The Shiro docs provide information on configuring Shiro.

By default, Airpal is configured to use the provided allow all configuration file. This configuration allows all users to have access to all data available to Presto.

Airpal also ships with a provided config file with statically configured users. This INI file establishes one user account with a static username and password, and should not be used in a production setting. To enable this, simply modify reference.yml to use shiro_static_users.ini.

Airpal can be configured to provide authentication and authorization via any shiro supported realm or filter, however, the primary principle must be an instance of one of the following:

Internally, we have a custom realm and filter which will map a user from our internal auth system to an AirpalUser.

Note that there are very likely better ways of making this more general, and PRs are welcome.