Bug 865523
| Summary: | No error message displayed at failed login | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Aaron Weitekamp <aweiteka> | ||||
| Component: | Content Management | Assignee: | Jordan OMara <jomara> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Katello QA List <katello-qa-list> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.0.1 | CC: | athomas, jturner, mmccune, tomckay | ||||
| Target Milestone: | Unspecified | Keywords: | Triaged | ||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 882288 (view as bug list) | Environment: | |||||
| Last Closed: | 2014-03-18 17:37:54 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 882288 | ||||||
| Attachments: |
|
||||||
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. 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. (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. 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. getting rid of 6.0.0 version since that doesn't exist 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. |
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: