Red Hat Bugzilla – Bug 860301
forgot username and reset password: no confirmation and user action not clear
Last modified: 2013-09-19 14:11:51 EDT
Created attachment 617065 [details]
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):
[root@qeblade40 Dev]# rpm -qa |grep katello
Steps to Reproduce:
1. Go to login screen
2. select "Forgot Username or Password?"
3. complete form and submit
UI should confirm an email has been sent and provide basic instruction to user. Circle icon should be changed to text "Login" or equivalent.
This may seem like an RFE but the behavior really feels broken to me, or at least half-baked.
Created attachment 617066 [details]
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
agreed, that page is a bit confusing now since there is zero feedback after a submit.
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.
The back button/arrow should be fixed in the latest release of alchemy.
To be more specific, the back arrow was fixed in commit cd7d623c0fc25297944a636f70fc268ff4efc762 of alchemy.
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.
getting rid of 6.0.0 version since that doesn't exist
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.