chore: Potential fix for code scanning alert no. 12: Clear-text logging of sensitive information #1279
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.
Potential fix for https://github.com/open-component-model/ocm/security/code-scanning/12
To fix the problem, we should avoid logging sensitive information directly. Instead, we can log non-sensitive parts of the
sub
variable or provide a sanitized version of the information. This can be achieved by implementing a method that returns a sanitized string representation of theConsumerProvider
without including sensitive data.catchedMatch
function inapi/credentials/internal/consumers.go
to log a sanitized version of thesub
variable.ConsumerProvider
interface that returns a sanitized string representation.Suggested fixes powered by Copilot Autofix. Review carefully before merging.