[
https://issues.apache.org/jira/browse/AIRFLOW-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225789#comment-16225789
]
Ash Berlin-Taylor commented on AIRFLOW-1765:
--------------------------------------------
Fair points.
I think the surprising thing to me was that it defaults to allow/isn't
mentioned in https://airflow.apache.org/security.html -- and I think from the
code there's no way to not make it open by default other than maybe to
mis-configure an api auth backend? I don't have the code in front of me and
it's late so I might be way off on this.
My plan will be to create 2, or 3 auth api backends. A "denyAll" (and make this
the default now), a "allowAll" to get the old behaviour back. It might also be
worth creating a "sessionAuth" wich just needs a valid login using whatever
mechanism the front end allows. (#3 is probably optional for closing this hole)
Suitable doc updates to go with this.
Sound reasonable?
> Default API auth backed should deny all.
> ----------------------------------------
>
> Key: AIRFLOW-1765
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1765
> Project: Apache Airflow
> Issue Type: Improvement
> Components: api, authentication
> Affects Versions: 1.8.2
> Reporter: Ash Berlin-Taylor
> Labels: security
> Fix For: 1.9.0
>
>
> It has been discovered that the experimental API in the default configuration
> is not protected behind any authentication.
> This means that out of the box the Airflow webserver's /api/experimental/ can
> be requested by anyone, meaning pools can be updated/deleted and task
> instance variables can be read.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
