-
Notifications
You must be signed in to change notification settings - Fork 265
feat: idtoken user credential #469
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
guillaumeblaquiere
wants to merge
11
commits into
googleapis:master
from
guillaumeblaquiere:468/idtokenUserCredential
Closed
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
6ed60bf
Merge pull request #1 from googleapis/master
guillaumeblaquiere 397694b
Feat: add signed id token capability on UserCredentials class.
guillaumeblaquiere 6e4a757
Add fully qualified package.
guillaumeblaquiere d3a50ef
Add comment
guillaumeblaquiere c94a0ce
Remove useless scopes.
guillaumeblaquiere 9d1b142
Too many cleaning on scope. oups!
guillaumeblaquiere 2eda5b4
fix: Too many cleaning on scope. oups!
guillaumeblaquiere a679f63
Merge remote-tracking branch 'origin/468/idtokenUserCredential' into …
guillaumeblaquiere c1d3f5d
fix: clean unused import
guillaumeblaquiere 195eba5
fix: clean unused import.
guillaumeblaquiere d430710
chore: make the commit comment working
guillaumeblaquiere File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's arguable how secret these are when they ship in binaries, but in the past security team has advised me in other projects not to put these values in github but to bundle them in at build time.
Please file a ticket for an internal security review on this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, Google Client_id and secret (Yes, Google, because it's not my secrets, but Google secrets!) are clear and it can seem not safe. But, I don't think that is a real "secret".
I'm not sure to catch what change if you add only these values at build time? The library will be ship with the secret in plain text and a simple IDE allow you to easily find them..
Here how I found the Google secrets
You can see the request body in clear with this client_id and client_secret
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@elharo I created the issue #472. I let you forwarding it internally.
If required, I will be happy to participate to discussion (I'm a GDE and thus already under NDA)