No, please do voice out if you have any concern or suggestion ;-)

XD

> On 31 Jan 2019, at 9:45 PM, Shah Altaf <mend...@gmail.com> wrote:
> 
> My mistake, yes it's just for UI.  Not for API.  I'll be quiet now :-)
> 
> 
> 
> On Thu, Jan 31, 2019 at 1:42 PM Deng Xiaodong <xd.den...@gmail.com> wrote:
> 
>> Hi Shah,
>> 
>> Thanks for your reply.
>> 
>> May I confirm that you mean that you’re using it for the UI or for the API
>> authentication? What we discuss here is only the API authentication.
>> 
>> If you meant UI authentication, actually the non-RBAC UI is already
>> deprecated in master branch, as I shared (meaning from one of the future
>> release, only FAB-based RBAC UI will be supported).
>> 
>> 
>> XD
>> 
>>> On 31 Jan 2019, at 9:37 PM, Shah Altaf <mend...@gmail.com> wrote:
>>> 
>>> Hello, yes we are using password_auth for all of our Airflow
>>> installations.  We specifically use it to automate creation of many
>> users.
>>> 
>>> 
>>> 
>>> On Thu, Jan 31, 2019 at 1:08 PM Deng Xiaodong <xd.den...@gmail.com>
>> wrote:
>>> 
>>>> Hi folks,
>>>> 
>>>> As you may have noticed, the Flask-Admin based UI (non-RBAC) was already
>>>> deprecated in the master branch. Some works are going on to further
>> clean
>>>> the codebase.
>>>> 
>>>> In the process, we found that there are some “legacy" modules in
>>>> “airflow/contrib/auth/backends/ <
>>>> 
>> https://github.com/apache/airflow/pull/4612/files#diff-fa19b36f43ec33307cd3ffe32f8b5397
>>> “.
>>>> Most of them should be removed directly, as they’re no longer applicable
>>>> for the new UI. But there is one module,
>>>> “airflow/contrib/auth/backends/password_auth.py <
>>>> 
>> https://github.com/apache/airflow/pull/4612/files#diff-fa19b36f43ec33307cd3ffe32f8b5397
>>> ”,
>>>> is used for API authentication as well.
>>>> 
>>>> We would like to understand from the community, if anyone is using
>>>> airflow/contrib/auth/backends/password_auth.py <
>>>> 
>> https://github.com/apache/airflow/pull/4612/files#diff-fa19b36f43ec33307cd3ffe32f8b5397
>>> 
>>>> for API authentication? This will help estimate & decide whether we
>> remove
>>>> it directly or spend some effort to refactor it.
>>>> 
>>>> Thanks for your inputs in advance.
>>>> 
>>>> 
>>>> XD
>>>> 
>>>> Reference: https://github.com/apache/airflow/pull/4612 <
>>>> https://github.com/apache/airflow/pull/4612>
>> 
>> 

Reply via email to