[AIENG-545][Backend] OIDC Jenkins provider support + verify --oidc flow#1351
Open
gokul-cloudbees wants to merge 3 commits into
Open
[AIENG-545][Backend] OIDC Jenkins provider support + verify --oidc flow#1351gokul-cloudbees wants to merge 3 commits into
gokul-cloudbees wants to merge 3 commits into
Conversation
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.
Summary
Adds tokenless authentication to the CLI using any OIDC identity provider the CI can act as (Jenkins via the oidc-provider plugin, GitLab, custom IdPs). Instead of a static SMART_TESTS_TOKEN, the pipeline presents a short-lived, signed OIDC id-token that Intake verifies cryptographically. This is the CLI half of AIENG-545 Phase 2 (the Intake backend + WebApp changes ship separately).
Two new actions on the verify command:
smart-tests verify --oidcCredential-free bootstrap. Presents the id-token to /intake/oidc/verify, prints eval-able export lines for org/workspace/token so later commands authenticate with the same JWT.
smart-tests verify --oidc-fetch-issuerRun from inside a private network. Reads the issuer from the token, fetches its public JWKS via OIDC discovery, and prints an {issuer, jwks} block for an admin to paste into the WebApp. Authenticates nothing; contacts only the issuer.