Closed Bug 483707 Opened 17 years ago Closed 17 years ago

Website: change copy for forgot password page

Categories

(Mozilla Labs Graveyard :: Personas Plus, defect, P1)

x86
All
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: drolnitzky, Assigned: rdoherty)

References

()

Details

Attachments

(1 file)

Copy wasn't changed in Bug 482627 (comment #5). It should be: "Oops! We are unable to locate the username you entered. Please try again, or create a new one."
Target Milestone: -- → 1.0
Priority: -- → P1
Note: for security, it's generally better not to let users know whether or not a given username exists on a site, since doing so makes it easier for account attackers to focus their attacks. So we probably shouldn't be revealing the nonexistence of the username here.
How about this approach: "Oops! The e-mail address and password you entered do not match any accounts on record. Are you trying to register for a new account?" Link "new account" to the signup page. Alternatively, flickr, as an example, uses simply: "This ID is not yet taken. Are you trying to register for a new account?" Which seems to be the original approach.
(In reply to comment #2) > How about this approach: > > "Oops! The e-mail address and password you entered do not match any accounts on > record. Are you trying to register for a new account?" Since this is from the Forgot Password page, they haven't entered a password at this point, so we can't say it doesn't match. > Link "new account" to the signup page. > > Alternatively, flickr, as an example, uses simply: > "This ID is not yet taken. > Are you trying to register for a new account?" Which seems to be the original > approach. That actually has the same security implications as the original text: it reveals whether or not the username is in use. But perhaps this is a security risk we're willing to take. I notice that addons.mozilla.org also reveals this information: when you enter an email address into its Password Reset form <https://addons.mozilla.org/en-US/firefox/users/pwreset> that doesn't correspond to an existing account, the site responds "User not found!". So perhaps it's ok to report an error when we can't find the username the user entered, and the text in comment 0 is fine.
Given the precedent here with other mozilla properties, let's stick with comment 0 for now. Thanks for the feedback Myk.
done.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Product: Mozilla Labs → Mozilla Labs Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: