feat: OpenClaw SecretRef exec provider with audit metadata hints (v0.15.2)#14
Merged
Conversation
- Mint unsealed sessions when the home directory cannot be determined and no PHOENIX_SEAL_KEY is set, instead of failing session mint. - Short-circuit empty ids in the exec provider without a resolve call. - Reject trailing non-whitespace data after the stdin JSON request. - Strip Unicode format/bidi control characters (Cf) from OpenClaw audit metadata values. - Add tests for sealed-envelope decrypt, non-200 responses, trailing data, empty ids, missing-HOME mint, and Cf sanitization. - Bump version to 0.15.2 and add release notes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Restructure exec-provider auth guidance into three explicit modes (bootstrap token + role, mTLS + role, pre-minted session token) and call out the invalid PHOENIX_ROLE + phxs_ combination. - Add HOME to the recommended passEnv example for per-role seal keys. - Document the audit-only X-OpenClaw-* metadata headers and the deliberate exclusion of X-OpenClaw-Session-Key. - Note signed resolve is unsupported in the exec-provider path and document phoenix openclaw-exec-provider as the canonical command. - Update stale roadmap shipped-version heading. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ack TLS requirement Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…dit helper, escaped Unicode test literals Co-Authored-By: Claude Fable 5 <noreply@anthropic.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
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.
Adds
phoenix openclaw-exec-provider(aliases:secret-provider openclaw,resolve --stdin-json) implementing OpenClaw's exec SecretRef protocol v1 — stdin JSON request, stdoutvalues/errorskeyed by original ids, reusing existing bearer/mTLS/role-session/sealed-response auth paths.The server captures five allowlisted
X-OpenClaw-*headers as sanitized, audit-only metadata, with tests proving zero authorization effect (X-OpenClaw-Session-Keyis never captured).Also included:
/*vs/**glob semantics (with examples corrected across all docs), example listener defaulted to loopback with non-loopback TLS guidancetests/e2e/: 18-scenario end-to-end suite (auto-discovered scenarios, JSONL/TAP output) covering lifecycle, ACL, attestation/mTLS, sealed responses, step-up, audit metadata, the OpenClaw exec protocol, 1Password backend, and in-place upgradeValidation: full unit suite, 18/18 e2e scenarios including a 0.13.5→0.15.2 upgrade test, and a live OpenClaw gateway exercising both integration paths (exec provider bootstrap + runtime plugin) under a least-privilege token with a real model-mediated agent turn.
🤖 Generated with Claude Code