fix(config): #715 run RequireSecureScheme in the env credential resolver #733
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!733
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-715-cred-resolver-scheme"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
GetCredentialsWithSource returned the env MADTEA_URL and token without the cleartext-http guard. Every current caller re-runs the guard, so the gap is latent, but a future caller could skip it. Add RequireSecureScheme in the env-var branch, like the sibling GetCredentials branch and ADR 0041: the check belongs at the point that carries the token. An https or loopback setup is unaffected. Only a non-loopback http env URL with a token is refused.
Closes #715