feat: enable self signed jwt for service account credentials#1553
Merged
Conversation
Contributor
|
@arithmetic1728 I vaguely remember being told this was only implemented for GAPICs as self-signed JWT isn't guaranteed to work for all the APIs listed in the directory. Is that a non-issue now? |
busunkim96
approved these changes
Oct 7, 2021
|
Hi! This breaks (at least) the drive/v3 files list API (server starts throwing 500s). Manually disabling this with |
Contributor
Author
|
@vriesk Thank you for bringing it up. I tested with the following sample, it did break. Will investigate more. |
Contributor
Author
|
Created PR #1566 to disable self signed jwt. |
|
Thanks for the quick fix. :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enable self signed jwt if google-auth service account credentials are used.
Tested with Storage, Compute and PubSub APIs: