-
-
Notifications
You must be signed in to change notification settings - Fork 747
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
Add a Secret Masking to Rule Enfocement API View Output #6170
base: master
Are you sure you want to change the base?
Add a Secret Masking to Rule Enfocement API View Output #6170
Conversation
Add a Secret Masking to the API Output.
The idea seems good but the implementation needs a better architectural solution. Code already exists to handle masking secrets, would it be possible to call that?
I've not tested this, but perhaps it can be called like below so secrets are masked?
|
Thanks @nzlosh I will try it. :) |
@nzlosh I have tryed it:
Output: So Iooks like I can not 1:1 use that function. The Secret Masking it self working but the output for the none Secret Parameters get lost. |
I tried your Idea as well:
|
Philipp Homberger seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
Hi Community,
From My View of perspective Secrets should not show in cleartext in the Rule Enforcement View in the UI and the API. So I add a loop that auto mask the secret to *****.
I'am not 100% happy with the way I do it for get one function because of problem I had with access the keys of the object So I convert the Object to a str and than with eval to a dict.
Maybe someone here have a better Idea.
I wait for your feedback.
Thank you all.