4
4
Authorization is finding out if the person, once identified, is permitted to
5
have the resource. [1]_ Drizzle authorization is handled by plugins; there
6
are no grant or privilege tables.
5
have the resource. [1]_
7
Drizzle authorization is handled by plugins. There is no single
8
source where users or access rights are defined, such as a system user table,
9
but each auhtorization plugin will use different sources to define or store
10
access rights. By default no authorization plugin is loaded, this means that
11
any logged in user is authorized to access all database objects and do anything
12
he wants (everyone is super user).
8
14
The following authorization plugins are included with Drizzle:
10
* :doc:`/plugins/regex_policy/index`
11
* :doc:`/plugins/simple_user_policy/index`
16
* :doc:`/plugins/regex_policy/index` - ALLOW or REJECT access by matching a regular expression against the table name.
17
* :doc:`/plugins/simple_user_policy/index` - Allow a user to only access a schema that matches their username.
22
At the moment there doesn't exist a plugin which would implement anything
23
resembling the traditional SQL standard GRANT and REVOKE type of authorization.
24
You are invited to share your opinion on whether that level of authorization
25
control is necessary in a modern database.
27
Note that at the moment there also is no plugin that would distinguish between
28
read and write operations, rather access is always granted to schemas and tables
29
in an all or nothing fashion.
13
31
-------------------------------------------------------------------------------
added
removed
docs/administration/authorization.rst
