Repository navigation
[RDE-534] Document OIDC cloud authentication for RDE sessions - #382
Draft
gaborszakacs wants to merge 4 commits into
Draft
gaborszakacs wants to merge 4 commits into
gaborszakacs wants to merge 4 commits into
Conversation
New page under RDE > Configuration covering the session subject and claims, requesting a token with the rde-id-token helper, and AWS and GCP template recipes. The OIDC overview, AWS and GCP pages point to it; their provider-side steps stay the single source for both builds and sessions. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This branch has not been deployed
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
1 participant
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.
RDE-534
Draft until the RDE backend and the session helper ship. The helper name (
rde-id-token) and its one flag are the proposed design from the RFC and must be re-checked against the implementation before this merges.TLDR
static/llms.txtTokens are requested on demand, not refreshed
The helper is one-shot: it prints a token and exits. The recipes have the cloud SDKs call it whenever they need a credential, AWS through
credential_processand GCP through an executable-sourced credential, and cache the exchanged credential until it expires. No background refresher and no token file on the machine. This is the same pull model as the git credential helper the GitHub integration uses, and it came out of the review thread on the RFC: https://bitrise.atlassian.net/wiki/spaces/ENGI/pages/5293735999The provider-side setup (IAM identity provider, trust policy, workload identity pool) is identical for builds and sessions, so it stays on the existing AWS and GCP pages rather than being duplicated.
No changelog entry yet; it gets added when this merges so the date is right.
Testing
npm ci && npm run build: passes for both locales; the only broken-anchor warnings are pre-existing ones on four/ja/pages this PR does not touch🤖 Generated with Claude Code