Bug 860301

Summary: forgot username and reset password: no confirmation and user action not clear
Product: Red Hat Satellite Reporter: Aaron Weitekamp <aweiteka>
Component: WebUIAssignee: David Davis <daviddavis>
Status: CLOSED UPSTREAM QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.1CC: jomara, mmccune, tomckay
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 882247 (view as bug list) Environment:
Last Closed: 2013-09-19 18:11:51 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: 882247    
Attachments:
Description Flags
reset password
none
Forgot username none

Description Aaron Weitekamp 2012-09-25 13:59:12 UTC
Created attachment 617065 [details]
reset password

Description of problem:
When selecting "Forgot Username or Password?" user is not taken to a confirmation screen. An email is sent in the background but the UI does not change. It feels like nothing has happened.

Also it is not at all clear what the circle icon does.


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


How reproducible:
100%

Steps to Reproduce:
1. Go to login screen
2. select "Forgot Username or Password?"
3. complete form and submit

Actual results:


Expected results:
UI should confirm an email has been sent and provide basic instruction to user. Circle icon should be changed to text "Login" or equivalent.

Comment:
This may seem like an RFE but the behavior really feels broken to me, or at least half-baked.

Comment 1 Aaron Weitekamp 2012-09-25 13:59:35 UTC
Created attachment 617066 [details]
Forgot username

Comment 2 Aaron Weitekamp 2012-09-25 14:06:43 UTC
Also, when a user enters a new password there's no confirmation the password has been changed. Clicking the mysterious circle icon returns a page with text "Unknown action The action 'show' could not be found for UserSessionsController". The only way to login after resetting password is to change the URL in the browser location bar to [myHost]/katello

Comment 4 Mike McCune 2012-10-10 14:33:12 UTC
agreed, that page is a bit confusing now since there is zero feedback after a submit.

Comment 5 David Davis 2012-12-03 17:53:22 UTC
It looks like the code here is relying on our notices.js/notify stuff which requires that a user be logged in. Talking to some people, I found out that Lukas may have dealt with this problem before (notifying a user that's not logged in) so I am hoping he can maybe point me to some code that does this.

Comment 6 David Davis 2012-12-04 00:04:06 UTC
The back button/arrow should be fixed in the latest release of alchemy.

Comment 7 David Davis 2012-12-04 00:08:17 UTC
To be more specific, the back arrow was fixed in commit cd7d623c0fc25297944a636f70fc268ff4efc762 of alchemy.

Comment 8 David Davis 2012-12-11 16:04:10 UTC
Katello commits:

10754139fdd2c876232d28faeff93e76e3642f07

cd164b2ea06f15be4c93f89945d51ec1b595892d

Comment 9 David Davis 2012-12-11 16:05:50 UTC
I also noticed if you're using rails_warden >= 0.5.5, if you put in an incorrect username or password, it doesn't show you any message.

Comment 10 Mike McCune 2013-08-16 17:57:37 UTC
getting rid of 6.0.0 version since that doesn't exist

Comment 11 Mike McCune 2013-09-19 18:11:51 UTC
These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM.  If this is a mistake feel free to re-open.