Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id BE840200B44 for ; Thu, 30 Jun 2016 04:40:15 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id BD11C160A6E; Thu, 30 Jun 2016 02:40:15 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 11D16160A57 for ; Thu, 30 Jun 2016 04:40:14 +0200 (CEST) Received: (qmail 53733 invoked by uid 500); 30 Jun 2016 02:40:14 -0000 Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airflow.incubator.apache.org Delivered-To: mailing list commits@airflow.incubator.apache.org Received: (qmail 53724 invoked by uid 99); 30 Jun 2016 02:40:14 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jun 2016 02:40:14 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id DEF491A7617 for ; Thu, 30 Jun 2016 02:40:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.646 X-Spam-Level: X-Spam-Status: No, score=-4.646 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id LvLenu13kUyF for ; Thu, 30 Jun 2016 02:40:13 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with SMTP id EC5E65F47C for ; Thu, 30 Jun 2016 02:40:12 +0000 (UTC) Received: (qmail 53374 invoked by uid 99); 30 Jun 2016 02:40:12 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jun 2016 02:40:12 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 448212C02A0 for ; Thu, 30 Jun 2016 02:40:12 +0000 (UTC) Date: Thu, 30 Jun 2016 02:40:12 +0000 (UTC) From: "Vineet Goel (JIRA)" To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AIRFLOW-294) Add support for creating users with password (password_auth backend) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 30 Jun 2016 02:40:15 -0000 [ https://issues.apache.org/jira/browse/AIRFLOW-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Goel updated AIRFLOW-294: -------------------------------- Description: Currently the workflow to add new users through the UI is to create a new user. This form takes the username and the email id of the user but there seems to be no place to provide the password (unless I am mistaken) or for that matter to specify if the user is a super user. This makes the scope of this auth backend limited as new users need to be creating using db commands instead of the UI. Could one of the maintainers shed some light to this? > Add support for creating users with password (password_auth backend) > -------------------------------------------------------------------- > > Key: AIRFLOW-294 > URL: https://issues.apache.org/jira/browse/AIRFLOW-294 > Project: Apache Airflow > Issue Type: Improvement > Reporter: Vineet Goel > Priority: Minor > > Currently the workflow to add new users through the UI is to create a new user. This form takes the username and the email id of the user but there seems to be no place to provide the password (unless I am mistaken) or for that matter to specify if the user is a super user. This makes the scope of this auth backend limited as new users need to be creating using db commands instead of the UI. Could one of the maintainers shed some light to this? -- This message was sent by Atlassian JIRA (v6.3.4#6332)