Restrict and document access to BMC credentials
|Assigned To:||Dominic Cleal|
|Found in release:||Pull request:||https://github.com/theforeman/foreman/pull/3855|
|Velocity based estimate||-|
BMC interface credentials stored in Foreman are accessible through the ENC YAML output and through templates (#15046), however it isn't clear that they are so readily available when entering them and there is no option to restrict it.
It should be possible to disable access through the ENC YAML and templates to credentials if the administrator wishes, via a setting. This would use the credentials only for BMC smart proxies.
The BMC interface form should probably also state where the credentials are accessible from.
Reported by Alex Fisher to firstname.lastname@example.org, thanks. No CVE will be requested as it's by design, this is hardening.
fixes #16580 - redact BMC password in ENC/templates with setting
Passwords stored against BMC NICs are accessible by default via
nic.password in a template, even in safe mode (861a03b), and are also
exported in the ENC output. A new bmc_credentials_accessible setting
allows the admin to redact the values in both locations, only allowing
the password to be used internally for BMC smart proxies.
Disabling BMC credential access requires safemode_render for complete