Description of problem: When running the playbook "Configure Cloud Connector", when entering parameters, there is text input "satellite_password". It's not hidden in asterisks, it's plaintext. Users usually expect password fields to be of type password, not text. Version-Release number of selected component (if applicable): 6.7 snap 16, NOT regression How reproducible: Deterministic Steps to Reproduce: 1. Hosts -> Job Templates 2. Run template Configure Cloud Connector 3. Start typing in field satellite_password Actual results: The entered password is visible Expected results: The entered password is hidden as passwords usually are
Perhaps we should document that it's a good idea to use token instead of a password. It's additional manual step that must be done through CLI, but probably a good idea. Anyway, this is a generic RFE for template inputs in Foreman core, we should be able to mark inputs as hidden like we do with parameters.
No, it's not - this bug is about filling the invocation form and not having the password asterisked-out, the other one is about already invoked job having password in its name.
Created redmine issue https://projects.theforeman.org/issues/29464 from this bug
Upstream bug assigned to mhulan
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29464 has been resolved.
Verified with Sat 6.7 snap 20. Password is now correctly asterisked-out while being entered. Verified with WebUI and Hammer, job passed.
This was fixed in 6.7.