Potential fix for code scanning alert no. 26: Clear-text logging of sensitive information #84
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/krishnprakash/cloudflare-docs/security/code-scanning/26
To fix the problem, we need to ensure that sensitive information such as
client_secret
is not logged in clear text. Instead of logging theclient_secret
, we can log a message indicating that a service token has been created and instruct the user to save theclient_secret
securely without including the actual secret in the log.client_secret
in the message.client_secret
securely without displaying it.Suggested fixes powered by Copilot Autofix. Review carefully before merging.