You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Maxime Bugeia (JIRA)" <ji...@apache.org> on 2017/03/10 23:29:04 UTC

[jira] [Commented] (AIRFLOW-927) LDAP authtorization: ldap3 doesn't understand anything coming from configuration file

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

Maxime Bugeia commented on AIRFLOW-927:
---------------------------------------

I confirm this issue. LDAP is unusable in 1.8. Converting the configuration value with str(value) fix the issue.

> 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)