Bug 2528 – Second login attempt ALWAYS email's password

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 2528 - Second login attempt ALWAYS email's password

Summary:	Second login attempt ALWAYS email's password

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Bugzilla
Classification:	Community
Component:	Bugzilla General (Show other bugs)
Sub Component:
Version:	2.1rC
Hardware:	All Linux

Priority	medium Severity medium (vote)
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-05-03 19:47 EDT by caperry
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-09-19 15:34:58 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description caperry 1999-05-03 19:47:20 EDT

I goofed at login, and hit the "eMail password" button with
all the fields blank.  I then enterd my eMail and his "email
password" again.  Worked fine.  Then hit back, entered
password, and pressed login.  "Password emailed".  Maybe I
hit the wrong button, so I hit back again and then hit
login.  Same effect.  Hit back, re-entered password (in case
I mistyped), hit login.  Same effect.  Hit back TWICE and
then entered email and password.  Login worked.

Comment 1 David Lawrence 2001-03-18 18:26:54 EST

When I click on the Email Password with the login name field blank I get an
error message the the email address (same as login name) did not pass minimal
syntaxt checking so therefore I am not able to replicate the mentioned problem
with the latest Bugzilla code. Closing.

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