You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Bob Rumsby (JIRA)" <ji...@apache.org> on 2015/10/27 23:00:28 UTC

[jira] [Updated] (DRILL-3984) DOCS: configuring-user-authentication page should reference configuring-web-ui-and-rest-api-security

     [ https://issues.apache.org/jira/browse/DRILL-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bob Rumsby updated DRILL-3984:
------------------------------
    Assignee: Bridget Bevens

> DOCS: configuring-user-authentication page should reference configuring-web-ui-and-rest-api-security
> ----------------------------------------------------------------------------------------------------
>
>                 Key: DRILL-3984
>                 URL: https://issues.apache.org/jira/browse/DRILL-3984
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 1.2.0
>         Environment: N/a
>            Reporter: Andy Pernsteiner
>            Assignee: Bridget Bevens
>            Priority: Trivial
>
> 1.2 seems to have some new capabilities, namely the ability to restrict administrative (alter system, etc) functions to specific users/groups, as well as to restrict the UI/REST interface .
> In the page http://drill.apache.org/docs/configuring-user-authentication/ , there is the following section:
> <snip>
> Administrator Privileges
> When authentication is enabled, only Drill users who are assigned Drill cluster administrator privileges can perform the following tasks:
> Change a system-level option by issuing an ALTER SYSTEM command
> Update a storage plugin configuration through the REST API or Web Console
> View profiles of all queries that all users have run or are currently running in a cluster
> Cancel running queries that were launched by any user in the cluster
> </snip>
> The issue is that there is no further explanation on how to:
> 1) set the appropriate system variables to assign users/groups to have admin privileges
> 2) secure the UI (along w/ pre-req's/etc)
> Simple fix is to refer people to the appropriate page within the 'administrator privileges' section



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)