GitHubAppCredentials on remote side to use SlaveToMasterCallable#330
Closed
jglick wants to merge 7 commits intojenkinsci:masterfrom
Closed
GitHubAppCredentials on remote side to use SlaveToMasterCallable#330jglick wants to merge 7 commits intojenkinsci:masterfrom
jglick wants to merge 7 commits intojenkinsci:masterfrom
Conversation
jglick
commented
Aug 20, 2020
Member
Author
seems to be a flake. |
bitwiseman
approved these changes
Aug 20, 2020
Contributor
bitwiseman
left a comment
There was a problem hiding this comment.
This looks great to me. Do you mind if I add the caching back into this PR?
Member
Author
Sure, feel free to use this as a starting point for something more polished. |
8 tasks
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.
More verbose but probably safer version of #329. Untested.
The idea here is that the agent never sees the private key in plaintext, nor does it have the opportunity to create a spoofed API endpoint or whatever. It just gets an opaque, encrypted cookie, and any time it wants to look up the app token, it must ask the controller. Compared to #329 this is stateless.
Rather than
Secret, which can be constructed in other ways, I would rather useCryptoConfidentialKey. Unfortunately that has IV-related methods which are still not available for use from plugins. There does not seem to any easy-to-use and safe way of constructing an encrypted cookie in Jenkins, much less one from structured data like this.