Account Number isn't Configured as Sensitive #38
Conversation
This file contains 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
Development and production account number configuration keys are stored in an encrypted format, but are not configured as sensitive
|
Hello @swiftelan , We have created a ticket based on your report. Thank you. |
|
I'd love to see them encrypted instead: #18 |
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.
Development and production account number configuration keys are stored in an encrypted format, but are not configured as sensitive.
The Magento command magento config:sensitive:set will not set the account number values because they are not configured as sensitive. They are also not read from environment variables.
The regular
magento config:setcommand will set the values in plain text. This results in errors authenticating since the module expects encrypted values.