You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/07/14 11:07:18 UTC

[GitHub] [airflow] ad-m commented on issue #8111: Authentication in API

ad-m commented on issue #8111:
URL: https://github.com/apache/airflow/issues/8111#issuecomment-658118762


   @mik-laj , have you considered introducing a "token exchange" flow (similiar to RFC8693) instead of adding a new middleware? Then you can effectively support many forms of authentication, where each subsequent form has completely different requirements. I notice that when the scheduler communicates with the REST API, one internal form of authentication will be required. Users expect at least one external form of authentication. In the case of using "token exchange", basic communication would be carried out using own Airflow instance access tokens only.
   
   See also family of operation in AWS IAM `AssumeRole*`: https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRoleWithWebIdentity.html


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org