Potential fix for code scanning alert no. 3: Clear-text logging of sensitive information #78
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/3
To fix the problem, we need to avoid logging the
client_secretin clear text. Instead, we can log a message indicating that the service token was created without including the sensitive information. This way, we maintain the functionality of informing the user that the token was created while ensuring that sensitive data is not exposed.We will modify the print statement on line 150 to exclude the
client_secret. We will also add a note to the user to save the secrets without logging them.Suggested fixes powered by Copilot Autofix. Review carefully before merging.