[
https://issues.apache.org/jira/browse/AIRFLOW-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213880#comment-16213880
]
ASF subversion and git services commented on AIRFLOW-1743:
----------------------------------------------------------
Commit 27068450ab8d191c98ab087fb1ed816af6be908a in incubator-airflow's branch
refs/heads/v1-9-test from [~bolke]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=2706845 ]
[AIRFLOW-1743] Verify ldap filters correctly
The superuser and data profiler filter where set
by default
in the config template and could not be unset.
Closes #2712 from bolkedebruin/AIRFLOW-1743
(cherry picked from commit 16899a95b5cf08d1053892c532f4b494b2f7d0cc)
Signed-off-by: Bolke de Bruin <[email protected]>
> Default config template should not contain ldap filters
> -------------------------------------------------------
>
> Key: AIRFLOW-1743
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1743
> Project: Apache Airflow
> Issue Type: Bug
> Components: authentication
> Reporter: Bolke de Bruin
> Fix For: 1.9.0
>
>
> The config template functions as a template. In case a item is not in the
> airflow.cfg of the user it is used for default values.
> This should not be the case for filters for ldap users, as that can create
> unexpected results such as users not getting the right access levels.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)