Description of problem: If a custom certificates archive (TAR) is created for an external Capsule Server, and the installer used to try and install the custom certificates on an external Capsule Server with a *different* host name, the attempted installation proceeds but fails.
Version-Release number of selected component (if applicable): Testing was done with Satellite 6.2.2.
How reproducible: Every time.
Steps to Reproduce:
1. Create a custom certificate for the Satellite Server.
2. Create a custom certificate for an external Capsule Server.
3. Create the Capsule Server's certificate's archive (for example, hostname test1-capsule.anzlab.bne.redhat.com).
4. Attempt installation of the external Capsule Server's certificates archive on a host which has a different name (for example, test-capsule.anzlab.com.au).
Actual results: Installer fails with several error messages. (Refer to the attached installation log file).
Expected results: Installer detects that the hostname contained in the certificate is different to that of the current host and stops before making any change, and outputs a suitable error message.
We should be careful to ensure we're checking the subject alternative names, not just the CN. Often times several capsules are installed with the same cert bundle containing a virtual hostname + the the host names of the actual capsules for load balancing purposes.
Created redmine issue http://projects.theforeman.org/issues/18225 from this bug
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.