Bug 1319887

Summary: Password reset process does not send email, and directs email to contact address no longer in existence.
Product: OpenShift Container Platform Reporter: Stephen Gordon <sgordon>
Component: apiserver-authAssignee: Andy Grimm <agrimm>
Status: CLOSED CURRENTRELEASE QA Contact: weiwei jiang <wjiang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: agrimm, aos-bugs, jgoulding, sgordon, wsun
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-22 14:08:07 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:
Attachments:
Description Flags
post-password-reset-screen none

Description Stephen Gordon 2016-03-21 18:20:44 UTC 
Created attachment 1138700 [details]
post-password-reset-screen

Description of problem:

Password reset process does not send email, and directs email to contact address no longer in existence.

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


How reproducible:


Steps to Reproduce:

1) From openshift.redhat.com click My Account -> Web Console
2) Leads to https://openshift.redhat.com/app/login?then=%2Fapp%2Fconsole
3) Click "Forgot my password"
4) Fill in email, click "Reset Password"
5) Screen attached is displayed.

Actual results:

* Never receive reset email (not in spam, trash etc., have received it in the past.
* Screen displayed says to email openshift in this case, which is not a valid email address:

Google tried to deliver your message, but it was rejected by the server for the recipient domain redhat.com by mx1.redhat.com. [209.132.183.28].
The error that the other server returned was:
554 5.7.1 <openshift>: Recipient address rejected: Access denied

Expected results:

* Actually receive reset email.
* Receive valid instructions for follow up in the case where the reset process does not resolve issue.
Additional info:
Comment 1 Andy Grimm 2016-03-21 18:31:38 UTC 
I saw two attempts to reset the password for "stephen.a.gordon"  -- note the missing 'l' in the domain.  Perhaps that is the issue?
Comment 3 Stephen Gordon 2016-03-21 18:52:33 UTC 
(In reply to Andy Grimm from comment #1)
> I saw two attempts to reset the password for "stephen.a.gordon"  --
> note the missing 'l' in the domain.  Perhaps that is the issue?

This does indeed resolve the first issue, it does not however resolve the second issue (pointing of the user to a support email that does not exist).
Comment 4 Andy Grimm 2016-03-22 14:08:07 UTC 
Right, the second issue was addressed via a configuration change.