Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 560954 [details]
katello.conf

Take a SAM instance which is connected to three networks.

on enterprise vlan0, hostname is sam-lab1.example.com
on private vlan1, hostname is sam.vlan1-lab1
on private vlan2, hostname is sam-lab1.vlan2

SSL certificate is likely to be created to hostname sam-lab1.example.com during katello-configure.

Clients on vlan1 and vlan2 need to connect to SAM using corresponding vlans. They do not have connection to vlan0.

When a customer tries to initiate a connection from a client to a server, they get a message "Peer certificate commonName does not match host". 

Attaching /etc/httpd/conf.d/katello.conf as a reference -- it's created by katello-install.

moving to sam14

This bug was closed because of a lack of activity.  If you feel this bug should be reconsidered for attention please feel free to re-open the bug with a comment stating why it should be reconsidered.