-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Data Sources | passwords in clear-text #14002
Comments
I don't think this is a bug. This is somewhat related to #13304, I suspect you are someone with edit access if you are able to view the sensitive parameters as plain text. Moreover, as per #12625 the functionality was requested only for detail object view. There are other issues I see with this report
|
I don't argue if it can be considered feature request. In the User form there is also a Password field and that one appears to deal with the password sensitivity correctly. Bullet 1. appears to be implemented already on the User form: Bullet 2. appears also to be implemented on the User form. No user can see my password. Not even my user. The User can only change it. Bullet 3. relates to #13729 |
I agree with @abhi1693 that none of the behavior mentioned here deviates from expected operation. While I appreciate the need to treat certain data as sensitive, there is a competing need to make it available to enable certain operations and troubleshooting. @teixemf if you would like to propose a mechanism for omitting potentially sensitive data from the changelog, please submit a feature request detailing both your proposed implementation as well as consideration of the constraints it would impose. Further, if you would like to propose changes to any of the form fields, please submit a separate FR for those. |
NetBox version
v3.6.3
Python version
3.11
Steps to Reproduce
Expected Behavior
Observed Behavior
While typing the password/AWS secret access key the characters appear in clear-text
After saving, one can see the password/AWS secret access key in clear-text on the Backend card
The text was updated successfully, but these errors were encountered: