this has been discussed before. the problem is that we are not entering the password once for authentication, it is entered as part of the configuration. thus we would still want to review it later.

there could an option to "show/hide password" next to such fields (how about community in snmp v1&2c ?), but that's more like a feature development

zalex_ua I agree with Rich.
Also remember about user macros used often to store credentials. I have no idea how it could be nicely designed to store passwords.

This idea sounds reasonable to me.

Hiding such fields (incl. snmp community strings) with the option to show them would improve security a little bit without having to make disruptive changes.
However, in long term I think all sensitive data should be moved into a secure container like mentioned by ZBXNEXT-1660.

ZBX-6721 is related.
Not sure how far we will go

ZBXNEXT-2957 asks to hide [some] macros/variables that way

This seems to still be the case (Text box) in 3.4.7, why can't this be changed? I modified configuration.item.edit.php to use CPassBox vs. CTextBox and didn't see any problems creating the item. The password column in items is still clear text but at least the database is restricted more so than when you have multiple Zabbix Admins.

Any reason this can't be fixed? Every time I upgrade I have to go edit all the files with a password field.

(new CTextBox('password'
to
(new CPassBox('password'

please?

I am an enterprise monitoring engineer and I shouldn't know all passwords I need in environment. I need to make the responsible team enter the needed pw once, then I should use it whenever I need without seeing the password. (for example choose pw from safe in snmpv3 item) And also maybe a cyberark integration needed ahead! The world is going through self changing passwords. Also, I use version 4.0 now and there's still shown passwords everywhere.

CProxyPatch.txt

Including a patch of the API code to hide PSK information from non Super Admins in get requests.

DB monitors are also affected by this "feature".

We can't fully use DB monitor items without hiding passwords in web.

Just hiding password fields in web will help a lot: when you unsure about password you can retype it and that's all, BUT no user can see password by just clicking DB monitor item.

I would like to support this CR. When multiple teams use Zabbix for monitoring collective infrastrusture open passwords cause concern.

It has been already fixed in 5.2 by masking of user macros and ability to keep them in an external Vault