Enhance mqsivault to provide an option to disable the display of passwords when creating the vault.

Idea review. Thank you very much for taking the time to raise this suggestion, but unfortunately on this occasion we would not be able to take forward the idea in its current form. Currently our vault model uses symmetric encryption. Using the vault key, you have the power to both create and read mqsicredentials entries from the vault. The intention of this idea appears to be to STOP the operator from being able to interact with other user's passwords, however it is not clear whether the need here is to entirely STOP or just to make it DIFFICULT (in the same way as the example mqsireportdbparms command which of course does not encrypt at all, and also has the option of confirming a password but only if the user has supplied it correctly). To resolve a need to entirely STOP, would require a change for the vault to use asymmetric encryption so that we could build in separate behaviours based on whether the operator presented the private key or the public key. Even if we were to re-write this component to use asymmetric encryption it is still not obvious how the feature should be designed as careful consideration would need to be applied to what level of authority the server itself should be granted. Clearly, it would need to be able to read credentials from the vault otherwise it could not do its job in communicating with third party systems. If this is actually just about making it DIFFICULT, then perhaps you would consider it sufficient to have some kind of configurable behaviour to turn off the --decode option of the mqsivault command and the --report option of the mqsicredentials command? If we were to offer this though, it would only be a "soft" way of constraining behaviour because a user could change the configurable behaviour back the other way. In other words, for determined users there will always be a way to circumvent these soft methods ... so if this is more about formally BLOCKING, then a major redesign would be required where we would need to rethink the ACE model for administration levels with separate classifications of users in this functional area.