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 12252200C2B for ; Thu, 2 Mar 2017 18:31:52 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 10C32160B6F; Thu, 2 Mar 2017 17:31:52 +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 58367160B6A for ; Thu, 2 Mar 2017 18:31:51 +0100 (CET) Received: (qmail 47130 invoked by uid 500); 2 Mar 2017 17:31:50 -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 47121 invoked by uid 99); 2 Mar 2017 17:31:50 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Mar 2017 17:31:50 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 238C4C2051 for ; Thu, 2 Mar 2017 17:31:50 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.452 X-Spam-Level: * X-Spam-Status: No, score=1.452 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id CzcPcjX2fZIn for ; Thu, 2 Mar 2017 17:31:49 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id E72085F1C2 for ; Thu, 2 Mar 2017 17:31:48 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 8BF1FE05F7 for ; Thu, 2 Mar 2017 17:31:45 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 47C872415E for ; Thu, 2 Mar 2017 17:31:45 +0000 (UTC) Date: Thu, 2 Mar 2017 17:31:45 +0000 (UTC) From: "Marcelo G. Almiron (JIRA)" To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AIRFLOW-927) LDAP authtorization: ldap3 doesn't understand anything coming from configuration file MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 02 Mar 2017 17:31:52 -0000 [ https://issues.apache.org/jira/browse/AIRFLOW-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo G. Almiron updated AIRFLOW-927: --------------------------------------- Affects Version/s: Airflow 1.8 > LDAP authtorization: ldap3 doesn't understand anything coming from configuration file > ------------------------------------------------------------------------------------- > > Key: AIRFLOW-927 > URL: https://issues.apache.org/jira/browse/AIRFLOW-927 > Project: Apache Airflow > Issue Type: Bug > Components: contrib > Affects Versions: Airflow 1.8, Airflow 1.7.1.3 > Reporter: Marcelo G. Almiron > > Function `get_ldap_connection` on airflow/contrib/auth/backends/ldap_auth.py does not understand 'future.types.newstr.newstr' objects coming from `configuration.get("ldap", "bind_user")` and `configuration.get("ldap", "bind_password")`. > The same can be observed in the `group_contains_user` function. Here the `search` function does not consider the arguments `configuration.get("ldap", "basedn")`, `configuration.get("ldap", "superuser_filter")`, not `configuration.get("ldap", "user_name_attr")` as expected. > A quick fix would be to convert all these values to `str` as soon as they are read from the configuration file, but this is not a definitive fix. -- This message was sent by Atlassian JIRA (v6.3.15#6346)