Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: googleapis/google-auth-library-python
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.1.0
Choose a base ref
...
head repository: googleapis/google-auth-library-python
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.2.0
Choose a head ref
  • 5 commits
  • 10 files changed
  • 5 contributors

Commits on Sep 21, 2021

  1. chore: relocate owl bot post processor (#869)

    chore: relocate owl bot post processor
    SurferJeffAtGoogle authored Sep 21, 2021
    Configuration menu
    Copy the full SHA
    d994a5a View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    afd05a6 View commit details
    Browse the repository at this point in the history
  3. feat: add support for workforce pool credentials (#868)

    Workforce pools (external account credentials for non-Google users) are
    organization-level resources which means that issued workforce pool tokens
    will not have any client project ID on token exchange as currently designed.
    
    "To use a Google API, the client must identify the application to the server.
    If the API requires authentication, the client must also identify the principal
    running the application."
    
    The application here is the client project. The token will identify the user
    principal but not the application. This will result in APIs rejecting requests
    authenticated with these tokens.
    
    Note that passing a `x-goog-user-project` override header on API request is
    still not sufficient. The token is still expected to have a client project.
    
    As a result, we have extended the spec to support an additional
    `workforce_pool_user_project` for these credentials (workforce pools) which will
    be passed when exchanging an external token for a Google Access token. After the
    exchange, the issued access token will use the supplied project as the client
    project. The underlying principal must still have `serviceusage.services.use`
    IAM permission to use the project for billing/quota.
    
    This field is not needed for flows with basic client authentication (e.g. client
    ID is supplied). The client ID is sufficient to determine the client project and
    any additionally supplied `workforce_pool_user_project` value will be ignored.
    
    Note that this feature is not usable yet publicly.
    
    The additional field has been added to the abstract external account credentials
    `google.auth.external_account.Credentials` and the subclass
    `google.auth.identity_pool.Credentials`.
    bojeil-google authored Sep 21, 2021
    Configuration menu
    Copy the full SHA
    993bab2 View commit details
    Browse the repository at this point in the history
  4. chore: remove 'six' (#871)

    tseaver authored Sep 21, 2021
    Configuration menu
    Copy the full SHA
    435be09 View commit details
    Browse the repository at this point in the history

Commits on Sep 27, 2021

  1. Configuration menu
    Copy the full SHA
    a53bd0c View commit details
    Browse the repository at this point in the history
Loading