Apache
/
druid
mirror of https://github.com/apache/druid.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix docs to explain that WRITE permissions do not include READ (#11785) 

* Fix docs to explain that WRITE and READ are exclusive

* Fix indentation

* Use suggested doc style
This commit is contained in:
Kashif Faraz 2021-10-09 02:40:20 +05:30 committed by GitHub
parent 989297edc3
commit c2c724c065
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/operations/security-user-auth.md
View File

@ -50,6 +50,8 @@ In practice, most deployments will only need to define two classes of users:
It is important to note that WRITE access to DATASOURCE grants a user broad access. For instance, such users will have access to the Druid file system, S3 buckets, and credentials, among other things. As such, the ability to add and manage datasources should be allocated selectively to administrators. It is important to note that WRITE access to DATASOURCE grants a user broad access. For instance, such users will have access to the Druid file system, S3 buckets, and credentials, among other things. As such, the ability to add and manage datasources should be allocated selectively to administrators.
`WRITE` permission on a resource does not include `READ` permission. If a user requires both `READ` and `WRITE` permissions on a resource, you must grant them both explicitly. For instance, a user with only `DATASOURCE READ` permission
might have access to an API or a system schema record that a user with `DATASOURCE WRITE` permission would not have access to.
## Default user accounts ## Default user accounts