feat(export): extend --redact-secrets coverage for application keys#46
Merged
Conversation
Add provider_verification_key, client_id, and app_id redaction; strip embedded credentials from OIDC issuer URLs while keeping host/path visible; fail export when cleartext remains after redaction. Preserve auth_* proxy flags and document the contract in README and TC-EXP-003. Co-authored-by: Cursor <cursoragent@cursor.com>
fmenesesg
approved these changes
Jun 15, 2026
fmenesesg
left a comment
Collaborator
There was a problem hiding this comment.
Review summary
Solid extension of --redact-secrets — closes realistic gaps for shared exports without changing the opt-in default.
What works well
- Redacts
provider_verification_key,client_id, andapp_idin JSON/YAML artifacts - Strips embedded credentials from
issuer_endpoint/oidc_issuer_endpointwhile preserving host/path - Preserves auth-mode proxy flags (
auth_user_key,auth_app_id,auth_app_key) - Post-redaction gate (
VerifyNoCleartextSecrets) fails export with a path-qualified error beforemanifest.jsonis written - Good test coverage: opt-in default preserved, end-to-end export path, unit tests for JSON/YAML, README + TC-EXP-003 updated
Verified locally: go test ./... — 165 tests pass.
Nit (non-blocking): YAML issuer URLs wrapped in quotes are not stripped by stripURLUserinfo (quotes break url.Parse), but the verify gate still detects userinfo and fails the export — safe fail-closed behavior. Consider trimming quotes in a follow-up if toolbox YAML commonly uses quoted issuers.
Behavior note for team: exports with --redact-secrets may now fail where they previously completed with residual cleartext — intentional and desirable for shared artifacts.
Approve — ready to merge.
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.
Proposed change
Extend
--redact-secretsto close credential gaps in shared exports: redactprovider_verification_key,client_id, andapp_id; strip embedded credentials from OIDC issuer URLs while keeping host/path visible; fail export when cleartext remains after redaction.Type of change
RHCL checklist
go test ./...)-DskipTestswithout justificationTest plan
go test ./internal/export/...go test ./...(coverage 80.7%)TestExportRedactSecrets— extended keys, issuer strip, auth flags preservedTestExportWithoutRedactPreservesSecrets— opt-in default (no flag)TestVerifyNoCleartextSecretsFailsWithPath— gate fails with path-qualified errorAdditional information
extend-redact-secrets