This issue still exists for Katello 3.1. Without the workaround mentioned by Claran, it's not possible to use custom SSL certificates for katello.
On Wed, Aug 17, 2016 at 10:40 AM, Ciarán Taog <portic...@gmail.com> wrote: > I was finally able to resolve this issue by performing the following. > > The default katello certificate remains in the ssl-build directory created > by the initial install. I added it to the CA trust bundle on CentOS with: > > cp /root/ssl-build/katello-default-ca.crt /etc/pki/ca-trust/source/ > anchors/ > update-ca-trust enable > update-ca-trust > > There is probably a better and more restrictive way to accomplish this but > this seems to have resolved the issue for me. Thank you for pointing me in > the right direction with the port 8443 tip. > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-users+unsubscr...@googlegroups.com. > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
