Bug 772883 - There is no expected confirmation email after submiting a password reset request.
Summary: There is no expected confirmation email after submiting a password reset requ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Fotios Lindiakos
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-10 08:33 UTC by Yujie Zhang
Modified: 2015-05-15 01:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-18 18:04:17 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Yujie Zhang 2012-01-10 08:33:01 UTC
Description of problem:

There is no confirmation email after submiting a password reset request.

Version-Release number of selected component (if applicable):

rhc-site-0.84.13-1.el6_2.noarch

How reproducible:always


Steps to Reproduce:
1.Change /var/www/libra/site/config/environments/production.rb as following:
config.streamline = {
                     :host => 'https://streamline.devlab.phx1.redhat.com/'
2.Go to openshift,and click the "Sign in" button on the nav bar.
3.Click the "Click here to reset your password" button.
4.Input valid email and click the "Reset passwrd" button.
5.Check the email
  
Actual results:
The email received after reseting password has the following content:

Hello yujzhang+b2,

At your request, your password has been reset to JK6gEkgj3c

Sincerely,

The RedHat.com Team

Expected results:

The expected email in US1062 is like this:

http://etherpad.corp.redhat.com/IP8YVWboho

Additional info:

Comment 1 Fotios Lindiakos 2012-01-10 14:52:02 UTC
If that is the email being received, then the changes to the streamline server did not take effect. After changing the streamline server, you need to restart the Rails server.

Comment 2 Yujie Zhang 2012-01-12 02:36:50 UTC
(In reply to comment #1)
Test this bug on rhc-site-0.84.14-1.el6_2.noarch,it's fixed now.


Note You need to log in before you can comment on or make changes to this bug.