[jira] [Issue Comment Deleted] (AIRFLOW-331) correct the airflow online documentation on "Security / Web Authentication / LDAP " section

["peter pang (JIRA)" <ji...@apache.org>]

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

peter pang updated AIRFLOW-331:
-------------------------------
    Comment: was deleted

(was: I'm new from github, and I'm still studying to config the superuser and data_profiler users. It seems there are some bugs in the WebUI when use LDAP user filter.  I'll send a pull request later. Thanks for response.)

> correct the airflow online documentation on "Security / Web Authentication / LDAP " section
> -------------------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-331
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-331
>             Project: Apache Airflow
>          Issue Type: Wish
>          Components: docs
>    Affects Versions: Airflow 1.7.1.3
>            Reporter: peter pang
>            Assignee: peter pang
>            Priority: Minor
>              Labels: documentation
>
> I'm trying to setup LDAP authentication for airflow 1.7.1.3 
> I added the simple [ldap] config example showing onling to my airflow.cfg file, and the ldap login couldn't work. 
> After debug the auth_ldap.py I found "user_name_attr" and "search_scope"  are not the setting value.  
> in the auth_ldap.py , configuration.get("ldap", "user_name_attr") return value is the whole line strings " uid # in case of Active Directory you would use" , include "#..." !!
> ====================
> [ldap]
> .....
> user_name_attr = uid # in case of Active Directory you would use 
> ....
> search_scope = LEVEL # Set this to SUBTREE if using Active Directory, and not specifying an Organizational Unit
> =====================
> so the comment lines shouldn't be there, they must be in a new line with no space or tab char before the '#'
> ====================
> [ldap]
> ........
> "#" in case of Active Directory you would use 
> user_name_attr = uid
> .......
> "#" Set this to SUBTREE if using Active Directory, and not specifying an Organizational Unit
> search_scope = LEVEL
> =====================
> then ldap could work. 



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