Description of problem:
When direct AD integration of the Satellite machine is used, the key for the HTTP/ service is the same as the host/ key. Or indeed, the same /etc/krb5.keytab can be used for HTTP/ as well if KrbServiceName Any is used. That means attack against the Apache service will be able to impersonate the whole host.
It is essential for this setup to separate access to the keytab. The GSS-Proxy project (available in RHEL 7.0) can achieve this -- the Apache HTTP server does not need to have access to the keytab at all. Even for non-AD scenarios, shielding the daemon from the key material has benefits. For generic Apache description, see https://fedorahosted.org/gss-proxy/wiki/Apache.
Satellite 6 installer should take advantage of this possibility and configure GSS-Proxy, either based on some explicit option, and for some scenarios like direct AD integration, by default.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure Satellite 6 with external authentication against IPA using --foreman-ipa-authentication=true, or when the RFE in bug 1198103 is addressed to make it easily possible to configure directly against AD, setup that.
2. Check the setup.
The file /etc/httpd/conf/http.keytab is readable by apache user.
The file /etc/httpd/conf/http.keytab is not readable by apache user, it probably does not exist at all, and Kerberos SSO still works.
This should likely go hand in hand with move to mod_auth_gssapi, see bug 1198106.
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
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.