auth: introduce JWT signing with JWK for CI systems#1214
Merged
Conversation
matheuscscp
added
enhancement
Signed-off-by: Matheus Pimenta <matheuscscp@gmail.com>
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
2 participants
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.
Also move
auth/utils/cioidctoauth/utils/cijwt.This will be useful for
flux-mirror syncandflux push artifact.Similar to how the transport injects OIDC tokens retrieved from CI platforms like GitHub, GitLab and Forgejo (which are JWT tokens by the definition of OIDC), this PR introduces support for "bring your own key" JWT authentication in the
auth/jwtpackage.WithHostJWK()accepts a target host, a private JWK, and theiss,audandsubclaims. The transport will issue one JWT per request. This adds minimal overhead per request since the parameters are all in memory and no network calls are made for issuing a token (as opposed for example toactionsoidc). Because it's much cheaper to issue tokens like this, we make them 60sec-lived, which is awesome!I have specific plans to use
flux-mirror syncwith this feature in my company.