ashb opened a new pull request, #46981:
URL: https://github.com/apache/airflow/pull/46981

   Since requests to Task Execution API can originate  out-of-"cluser" so to
   speak, this PR re-works the JWTSigner class so that it is possible to use
   public/private keys (vs just a simple pre-shared secret). This is useful in
   many cloud environments where many companies have security requirements that
   ingress gateways must validate the JWT tokens on the way in, and the only way
   of doing this is with public keys
   
   So that we don't have two different ways of generating JWT tokens I have
   totally replaced the old "JWTSigner" class (which it turns out didn't have 
any
   unit test of its own, it was only tested indirectly through test_serve_logs
   etc).
   
   As part of this change I have also changed the JWT that was generated by the
   SimpleAuthManager and the AwsAuthManager (the only two we have that use JWT)
   to use the offical `sub` (subject) clain to place the user identifer rather
   than a custom claim name.
   
   And although it might seem slightly strange at first, I have made the
   JWTValidator an async class internally. (Hence `avalidated_claims` -- the `a`
   prefix signifies async, much like `aclose` or `aread` on HTTPX async
   responses). This allows us to periodically refresh the JWK document if
   configured in the background, and using asgiref's async_to_sync means we only
   have one version.
   
   And also conviently, this is the same tech that FastAPI uses, which means 
when
   this is called from within a FastAPI app, rather than creating a new/nested
   event loop it will "bubble out" to the main async loop that FastAPI is using.
   
   <!--
    Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file
    distributed with this work for additional information
    regarding copyright ownership.  The ASF licenses this file
    to you under the Apache License, Version 2.0 (the
    "License"); you may not use this file except in compliance
    with the License.  You may obtain a copy of the License at
   
      http://www.apache.org/licenses/LICENSE-2.0
   
    Unless required by applicable law or agreed to in writing,
    software distributed under the License is distributed on an
    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
    KIND, either express or implied.  See the License for the
    specific language governing permissions and limitations
    under the License.
    -->
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of an existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   
   
   <!-- Please keep an empty line above the dashes. -->
   ---
   **^ Add meaningful description above**
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in a 
newsfragment file, named `{pr_number}.significant.rst` or 
`{issue_number}.significant.rst`, in 
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to