Skip to content
This repository was archived by the owner on Mar 6, 2026. It is now read-only.
This repository was archived by the owner on Mar 6, 2026. It is now read-only.

Improve debug logging about the path that the authentication library is taking #472

Closed

Description

@hilts-vaughan

Thanks for stopping by to let us know something could be better!

PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.

Is your feature request related to a problem? Please describe.

When debugging what went wrong with the authentication library, it can be sometimes hard to track the path it took. For example, if it was issuing Compute Engine Metadata checks or (credential checks on a path) We've had cases in support sometimes where it would be good to understand the path that had been taken.

Describe the solution you'd like

I'm proposing (and will add a PR) to a bit more logging around:

  1. What checks you are taking during the auth checking process
  2. A bit more verbose output about the things that went well and what did not in those checkers

Describe alternatives you've considered

You can use the Python debugger, but this never helps after the fact. :)

Activity

  1. added
    type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.
    on Mar 26, 2020
  2. busunkim96 commented on Mar 26, 2020

    @busunkim96
    Contributor

    Hi @hilts-vaughan that sounds great! Please tag me once you've opened a PR.

  3. hilts-vaughan commented on Mar 26, 2020

    @hilts-vaughan
    ContributorAuthor

    I opened two:

    #474
    #473

    I tried to orchestrate the paths that I found would have been most valuables in some of the customer issues I had been debugging lately.

  4. westarle commented on Oct 16, 2023

    @westarle

    I see the two PRs merged so closing this issue fixed. Feel free to reopen if there is more work to do!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions