fix(security): suppress false-positive Bandit B105 in residual authz test - #104
Open
github-actions[bot] wants to merge 1 commit into
Conversation
Bandit flags the hardcoded JWT_SECRET value in the test file as B105 (hardcoded_password_string). This is a test-only secret with no production exposure; add `# nosec B105` to silence the scanner so the security-scan CI job no longer fails with exit code 1. Fixes the failing security-scan job on PR #93. Co-Authored-By: Claude Sonnet 4.6 <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
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
services/orchestrator/tests/test_residual_authz.py(introduced on thechore/a2a-prod-rollout-prepbranch) assigns a hard-coded string toos.environ["JWT_SECRET"]at line 34. Bandit rule B105 (hardcoded_password_string) flags this, causing thesecurity-scanCI job (test.yml) to exit with code 1.# nosec B105inline suppression comment on that line. This is a test-only secret with no production exposure — the comment is the canonical Bandit way to acknowledge intentional test fixtures.security-scanjob on PR chore(a2a): FuzeAgent-first prod rollout (DRAFT — needs owner secrets/config) #93.Relates to: #93
Test plan
bandit -r services/orchestrator --skip B101 -f txtno longer exits non-zero due to this filesecurity-scanjob passes in CI on this PR🤖 Generated with Claude Code