fix(v1beta2): enable self signed jwt for grpc #191
Conversation
…s user scopes, so that the auth library does not use the self-signed JWT flow.
@busunkim96 Are there special Labels necessary to engage owlbot for this change? |
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
@nicain I'm not aware of any labels. I ran owlbot locally using these steps and pushed to this branch.
@googlebot I consent. |
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
@googlebot I consent. |
Remove Owlbot v1beta2 customization that passes default scopes as user scopes, so that the auth library does not use the self-signed JWT flow.
Fixes #174