-
-
Notifications
You must be signed in to change notification settings - Fork 745
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Secret values on object in an array are not masked inside a pack config. #4139
Comments
Probably related to #4122 Wonder if the secret masking process for the CLI / API needs the same modifications? |
@NikosVlagoidis Thanks for reporting this. @nmaludy Yeah, it's most likely related to that change, but not to that code directly (that code is used in places where decrypted values are expected, API follows a different code path - just retrieves object from the database and masks secrets). We probably need to update Edit: That's also a good example which shows why it's important to think about all the various edge cases for tests when adding a new feature / similar and not just for simple "positive" test cases :) @nmaludy Will you have time to look into it? Or want me to do it? |
@Kami i'm checking it out now, looks like the affected functions are |
@armab Thanks for assigning the "bug" label - I was actually thinking of doing it myself, but IIRC, since nested objects were not supported in stable versions prior to v2.8dev, it's not a bug in a stable release, just a bug in current dev version so I decided to leave it out for now. Anyway, yeah, it's still a bug even though just in a dev release so it doesn't hurt to have that label. |
Fix for #4139 - Secrets not being masked in pack config
ISSUE TYPE
STACKSTORM VERSION
OS / ENVIRONMENT / INSTALL METHOD
docker instalation
SUMMARY
When I mark a secret value on a pack config inside an array I get the values in plain text even if Ii don't make the request with parameter show_secret=true.
STEPS TO REPRODUCE
Pack config
when I make a request on : https://{{host}}/api/v1/configs/<pack_name>
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: