Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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 747765[details]
error messages
Description of problem:
If you misconfigure your katello to use LDAP auth, the login page shows a few "scary" looking errors, none of which are actually helpful to understand that there is something wrong with the ldap configuration
Version-Release number of selected component (if applicable):
* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.8.7-1.el6.noarch
* candlepin-selinux-0.8.7-1.el6.noarch
* candlepin-tomcat6-0.8.7-1.el6.noarch
* elasticsearch-0.19.9-7.el6.noarch
* katello-1.4.2-1.git.333.d2a35bc.el6.noarch
* katello-all-1.4.2-1.git.333.d2a35bc.el6.noarch
* katello-candlepin-cert-key-pair-1.0-1.noarch
* katello-certs-tools-1.4.2-1.el6.noarch
* katello-cli-1.4.2-1.git.48.441089b.el6.noarch
* katello-cli-common-1.4.2-1.git.48.441089b.el6.noarch
* katello-common-1.4.2-1.git.333.d2a35bc.el6.noarch
* katello-configure-1.4.3-1.git.12.bc3684c.el6.noarch
* katello-glue-candlepin-1.4.2-1.git.333.d2a35bc.el6.noarch
* katello-glue-elasticsearch-1.4.2-1.git.333.d2a35bc.el6.noarch
* katello-glue-pulp-1.4.2-1.git.333.d2a35bc.el6.noarch
* Katello-Katello-Installation-ConfigureRepos-1.7-3.noarch
* Katello-Katello-Installation-RegisterRHNClassic-1.1-3.noarch
* Katello-Katello-Sanity-ImportKeys-1.2-1.noarch
* katello-qpid-broker-key-pair-1.0-1.noarch
* katello-qpid-client-key-pair-1.0-1.noarch
* katello-repos-1.4.2-1.el6.noarch
* katello-selinux-1.4.3-1.git.3.ce8227b.el6.noarch
* openldap-2.4.23-26.el6.x86_64
* pulp-rpm-plugins-2.1.1-0.10.beta.el6.noarch
* pulp-selinux-2.1.1-0.10.beta.el6.noarch
* pulp-server-2.1.1-0.10.beta.el6.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-ldap_fluff-0.1.3-4.el6.noarch
* ruby193-rubygem-net-ldap-0.2.2-6.el6.noarch
How reproducible:
Steps to Reproduce:
1. Configure your katello to use LDAP auth by enter incorrect values for the arguments
2. Go to the web login page
3.
Actual results:
See attached screenshot
Expected results:
Additional info:
With the move of Katello to be an engine running within Foreman, any issues related to ldap configuration will be much different. As a result, going to close this out and we can create new ones for any issues found.
Created attachment 747765 [details] error messages Description of problem: If you misconfigure your katello to use LDAP auth, the login page shows a few "scary" looking errors, none of which are actually helpful to understand that there is something wrong with the ldap configuration Version-Release number of selected component (if applicable): * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.8.7-1.el6.noarch * candlepin-selinux-0.8.7-1.el6.noarch * candlepin-tomcat6-0.8.7-1.el6.noarch * elasticsearch-0.19.9-7.el6.noarch * katello-1.4.2-1.git.333.d2a35bc.el6.noarch * katello-all-1.4.2-1.git.333.d2a35bc.el6.noarch * katello-candlepin-cert-key-pair-1.0-1.noarch * katello-certs-tools-1.4.2-1.el6.noarch * katello-cli-1.4.2-1.git.48.441089b.el6.noarch * katello-cli-common-1.4.2-1.git.48.441089b.el6.noarch * katello-common-1.4.2-1.git.333.d2a35bc.el6.noarch * katello-configure-1.4.3-1.git.12.bc3684c.el6.noarch * katello-glue-candlepin-1.4.2-1.git.333.d2a35bc.el6.noarch * katello-glue-elasticsearch-1.4.2-1.git.333.d2a35bc.el6.noarch * katello-glue-pulp-1.4.2-1.git.333.d2a35bc.el6.noarch * Katello-Katello-Installation-ConfigureRepos-1.7-3.noarch * Katello-Katello-Installation-RegisterRHNClassic-1.1-3.noarch * Katello-Katello-Sanity-ImportKeys-1.2-1.noarch * katello-qpid-broker-key-pair-1.0-1.noarch * katello-qpid-client-key-pair-1.0-1.noarch * katello-repos-1.4.2-1.el6.noarch * katello-selinux-1.4.3-1.git.3.ce8227b.el6.noarch * openldap-2.4.23-26.el6.x86_64 * pulp-rpm-plugins-2.1.1-0.10.beta.el6.noarch * pulp-selinux-2.1.1-0.10.beta.el6.noarch * pulp-server-2.1.1-0.10.beta.el6.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-ldap_fluff-0.1.3-4.el6.noarch * ruby193-rubygem-net-ldap-0.2.2-6.el6.noarch How reproducible: Steps to Reproduce: 1. Configure your katello to use LDAP auth by enter incorrect values for the arguments 2. Go to the web login page 3. Actual results: See attached screenshot Expected results: Additional info: