Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airflow.incubator.apache.org
Date: Fri, 14 Jul 2017 20:50:00 +0000 (UTC)
From: "Chris Riccomini (JIRA)" <jira@apache.org>
To: commits@airflow.incubator.apache.org
Message-ID: <JIRA.12966467.1462832682000.252133.1500065400229@Atlassian.JIRA>
In-Reply-To: <JIRA.12966467.1462832682000@Atlassian.JIRA>
References: <JIRA.12966467.1462832682000@Atlassian.JIRA> <JIRA.12966467.1462832682000@jira-lw-us.apache.org>
Subject: [jira] [Commented] (AIRFLOW-85) Create DAGs UI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 14 Jul 2017 20:50:05 -0000


    [ https://issues.apache.org/jira/browse/AIRFLOW-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088037#comment-16088037 ] 

Chris Riccomini commented on AIRFLOW-85:
----------------------------------------

Latest proposal on this is here:

https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+RBAC+proposal

Pre-req to doing this work is to convert Airflow to Flask app builder, per discussion here:

https://www.mail-archive.com/dev@airflow.incubator.apache.org/msg02946.html

> Create DAGs UI
> --------------
>
>                 Key: AIRFLOW-85
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-85
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: security, ui
>            Reporter: Chris Riccomini
>
> Airflow currently provides only an {{/admin}} UI interface for the webapp. This UI provides three distinct roles:
> * Admin
> * Data profiler
> * None
> In addition, Airflow currently provides the ability to log in, either via a secure proxy front-end, or via LDAP/Kerberos, within the webapp.
> We run Airflow with LDAP authentication enabled. This helps us control access to the UI. However, there is insufficient granularity within the UI. We would like to be able to grant users the ability to:
> # View their DAGs, but no one else's.
> # Control their DAGs, but no one else's.
> This is not possible right now. You can take away the ability to access the connections and data profiling tabs, but users can still see all DAGs, as well as control the state of the DB by clearing any DAG status, etc.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)