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.
Bug 865523 - No error message displayed at failed login
Summary: No error message displayed at failed login
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Jordan OMara
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: 882288
TreeView+ depends on / blocked
 
Reported: 2012-10-11 16:39 UTC by Aaron Weitekamp
Modified: 2014-11-09 22:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 882288 (view as bug list)
Environment:
Last Closed: 2014-03-18 17:37:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
katello/production.log (264.20 KB, text/plain)
2012-10-11 16:39 UTC, Aaron Weitekamp 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 865528 0 high CLOSED Incorrect credentials shows strange bug "string indices must be integers" 2021-02-22 00:41:40 UTC

Internal Links: 865528

Description Aaron Weitekamp 2012-10-11 16:39:59 UTC 
Created attachment 625584 [details]
katello/production.log

Description of problem:
When switching between local database and ldap user modes the katello webUI sometimes does not return failed login error. The loading GIF spins and then stops. No new page is loaded.

Version-Release number of selected component (if applicable):
1.1
[root@localhost katello]# rpm -qa |grep katello
katello-glue-pulp-1.1.12-12.el6cf.noarch
katello-certs-tools-1.1.8-1.el6cf.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-cli-common-1.1.8-6.el6cf.noarch
katello-selinux-1.1.1-1.el6cf.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-common-1.1.12-12.el6cf.noarch
katello-1.1.12-12.el6cf.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-configure-1.1.9-6.el6cf.noarch
katello-all-1.1.12-12.el6cf.noarch
katello-cli-1.1.8-6.el6cf.noarch
katello-glue-candlepin-1.1.12-12.el6cf.noarch


How reproducible:
Several times

Steps to Reproduce:
1. run `katello-configure` with default settings (local database users)
2. update /etc/ldap_fluff.yml and /etc/katello/katello.yml for ldap server
3. `katello-service restart`
4. run `katello-configure` again with new username
5. login fails
  
Actual results:
no error message displayed

Expected results:
Display login failure

Additional info:
Comment 2 James Laska 2012-10-15 18:33:16 UTC 
Based on comment#0, my impression is that attempts to login with valid credentials are failing.  There appears to be a traceback in the attached production.log (not clear whether that's related).  I'm not aware of a reasonable workaround at the moment.  This leads me to think that being unable to login to is rather serious.

I've set severity=urgent.  Feel free comment if I've assessed the severity incorrectly.
Comment 4 Jordan OMara 2012-10-17 15:18:11 UTC 
This bug is specifically caused by creating a user (logging in for the first time) in LDAP mode, switching Katello to database mode and then trying to log in.

The server throws an error because the user actually doesn't HAVE a password, not just that it doesn't match. Users are created with no passwords in LDAP mode.

This is bad because we don't correctly catch / display that error and instead just spin infinitely

Despite how bad it is, it requires a very specific set of steps to reproduce and I don't think this will be along any normal use case. 

You can also work around it by manually setting a password for the users in question in the DB.
Comment 5 James Laska 2012-10-17 15:31:11 UTC 
(In reply to comment #4)
> Despite how bad it is, it requires a very specific set of steps to reproduce
> and I don't think this will be along any normal use case. 

Thanks for the feedback Jordan.  Are the steps to reproduce the normal recommended procedure for enabling LDAP in katello?

> 1. run `katello-configure` with default settings (local database users)
> 2. update /etc/ldap_fluff.yml and /etc/katello/katello.yml for ldap server
> 3. `katello-service restart`
> 4. run `katello-configure` again with new username
> 5. login fails

What I'm wondering is whether the steps to reproduce are the correct procedure for enabling LDAP support in katello.  If so, it seems the frequency of users hitting this problem would be high.
Comment 6 James Laska 2012-10-18 14:39:45 UTC 
I appear to be seeing this while debugging other LDAP related login issues.  No matter how many times I attempt to login with valid credentials, the result is the same.  The login spinner appears, then goes away.  No error (or success) notification is displayed.

After <shift> reloading the login page, I was immediately able to login.
Comment 8 Mike McCune 2013-08-16 18:02:27 UTC 
getting rid of 6.0.0 version since that doesn't exist
Comment 9 Mike McCune 2014-03-18 17:37:54 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.