Skip to content

feat(provider): add Amazon Bedrock IAM Identity Center SSO #3370

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.

Sign up for GitHub

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

Open
keyuchen21 wants to merge 5 commits into
base: main
Choose a base branch
from
Open

feat(provider): add Amazon Bedrock IAM Identity Center SSO #3370

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
e281e56
feat(provider): add Amazon Bedrock IAM Identity Center SSO
keyuchen21 Aug 21, 2026
3e22fb2
fix(runtime-host): harden Bedrock SSO lifecycle
keyuchen21 Aug 29, 2026
d4b68ce
fix(provider): integrate Bedrock SSO with current main
keyuchen21 Aug 29, 2026
a6cf3a0
fix(provider): close Bedrock SSO review blockers
keyuchen21 Aug 29, 2026
47fb809
fix(runtime): force SigV4 for Bedrock discovery
keyuchen21 Aug 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 14 additions & 2 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,6 +144,17 @@ selection rules are documented in
or token files are not imported; users with only those copies must
re-authenticate.
4. **Renderer process sandbox + preload IPC bridge.** The
2. **Credential-at-rest boundaries.** Runtime Policy writes
`credential-vault.json` as versioned plaintext JSON under the Runtime Host
State Root. Its load-bearing boundary is the OS user account plus filesystem
controls: directory mode 0o700, file mode 0o600, atomic writes, and no
symlink/traversal escape. Subscription OAuth tokens (Claude, Codex, GitHub
Copilot, and xAI) and Amazon Bedrock IAM Identity Center sessions live in
that same vault, which is the single authority every Runtime Host surface —
Desktop, TUI, CLI — uses. Electron safeStorage is not part of this boundary
anymore. Pre-existing safeStorage-encrypted credential or token files are
not imported; users with only those copies must re-authenticate.
3. **Renderer process sandbox + preload IPC bridge.** The
renderer cannot reach files, network, or shell directly. Every
IPC handler in `apps/desktop/src/main/main.ts` is the trust
boundary between renderer-controlled input and main-process
Expand Down Expand Up @@ -206,8 +217,9 @@ privacy commitments:
reports `incognitoActive: true`, the WebSearch tool fails
closed before any network call. Main composition and focused
consumer tests own the full enforcement inventory.
- **Token boundary.** Cleartext API keys / OAuth tokens / bot
tokens NEVER cross the main→renderer IPC boundary.
- **Token boundary.** Cleartext API keys / OAuth tokens / AWS SSO sessions /
bot tokens NEVER cross the main→renderer IPC boundary. Temporary Bedrock
role credentials are memory-only inside Runtime Host.
`apps/desktop/src/main/__tests__/web-search-boundary.test.ts` and
`claude-subscription-ipc-boundary.test.ts` enforce this for Tavily
and Claude subscription credentials.
Expand Down
Loading