Встроенный контроль доступа#
Примечание
Ниже приведена оригинальная документация Trino. Скоро мы ее переведем на русский язык и дополним полезными примерами.
A system access control enforces authorization at a global level, before any connector level authorization. You can use one of the built-in implementations in Trino, or provide your own by following the guidelines in Контроль доступа.
Multiple system access control implementations may be configured at once
using the access-control.config-files
configuration property. It should
contain a comma separated list of the access control property files to use
(rather than the default etc/access-control.properties
).
Trino offers the following built-in implementations:
System access control name |
Description |
---|---|
|
All operations are permitted, except for user impersonation. This is the default access control if none are configured. |
|
All operations are permitted. |
|
Operations that read data or metadata are permitted, but none of the operations that write data or metadata are allowed. |
|
Authorization rules are specified in a config file. See Контроль доступа с помощью файла. |
If you want to limit access on a system level in any other way than the ones listed above, you must implement a custom Контроль доступа.
Read only system access control#
This access control allows any operation that reads data or
metadata, such as SELECT
or SHOW
. Setting system level or catalog level
session properties is also permitted. However, any operation that writes data or
metadata, such as CREATE
, INSERT
or DELETE
, is prohibited.
To use this access control, add an etc/access-control.properties
file with the following contents:
access-control.name=read-only