Bug 803923 - RFE: email should be able to corrected during register validation.
Summary: RFE: email should be able to corrected during register validation.
Alias: None
Product: Zanata
Classification: Retired
Component: Usability
Version: 1.6-SNAPSHOT
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 2.1
Assignee: Alex Eng
QA Contact: Ding-Yi Chen
: 735892 864088 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2012-03-16 01:52 UTC by Joyce Chang
Modified: 2013-03-04 03:19 UTC (History)
8 users (show)

Fixed In Version: 2.1-SNAPSHOT (20121220-0033)
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-26 04:06:13 UTC

Attachments (Terms of Use)
Server Log (39.03 KB, text/x-log)
2012-12-18 02:36 UTC, Ding-Yi Chen
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 750104 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 884386 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 750104 884386

Description Joyce Chang 2012-03-16 01:52:58 UTC
Description of problem:

a typo during the process of register(e.g. wrong email address)result in failure of account activation. 

users should be able to go back and fix incorrect info for successful account activation (e.g. correcting email address ) 

Version-Release number of selected component (if applicable):
Zanata version 1.6-SNAPSHOT (20120315-1806). 

How reproducible:

Steps to Reproduce:
2.fill in all correct info except for wrong email address
3.register sent 
4. sign in 

Actual results:

unable to sign in, and no way to change email address 

Expected results:

able to to sign in and email can be changed in the profile

Additional info:

Comment 1 Runa Bhattacharjee 2012-07-30 13:27:49 UTC
Generally, in these cases a failure notice is displayed on the sign up page if the email address is not valid. If the email address is valid, but not the one the user intended it to be then the confirmation period comes with a timeout (24 hours in most cases), after which the user can sign up again (provided the other unrelated account holder did not activate the account). 

Do we have a timeout?

Comment 2 David Mason 2012-07-31 00:39:42 UTC
There is currently no timeout for validation emails. There is no expiration of validation emails at all, even if they have been used previously (see https://bugzilla.redhat.com/show_bug.cgi?id=750104).

Comment 3 Sean Flanigan 2012-07-31 02:35:23 UTC
Note that approx 99.999% of systems which attempt to pre-validate email addresses (on the sign-up page) get it wrong, and disallow perfectly valid addresses, because the programmer didn't expect to see a full-stop in an address, for example.

We should implement a timeout for validation emails, and for deleting unactivated accounts.

Note that the fix for this issue may require somewhat different handling for external authentication systems.  With internal authentication, users can always pick another username and try again with a different email address, but with external authentication, the username is determined for them, so they don't even have that option.

Comment 4 Ding-Yi Chen 2012-11-06 01:18:30 UTC
*** Bug 735892 has been marked as a duplicate of this bug. ***

Comment 5 Patrick Huang 2012-11-20 05:38:37 UTC
*** Bug 864088 has been marked as a duplicate of this bug. ***

Comment 6 Alex Eng 2012-12-17 05:45:02 UTC
Implemented option to change email/resend activation email for unactivated account.


Comment 7 Ding-Yi Chen 2012-12-18 02:36:24 UTC
Created attachment 665242 [details]
Server Log

Comment 8 Ding-Yi Chen 2012-12-18 02:38:43 UTC
Tested with Zanata version 2.1-SNAPSHOT (20121217-1536)

Unexpected error. Please try again. [ Request: /error.seam?cid=18 ] 
appears after either Resend activation email or Update email address.

Note that server setting is done through the zanata.properties

Server log is attached in previous comment.

Comment 11 Ding-Yi Chen 2012-12-19 23:17:55 UTC
VERIFIED with Zanata version 2.1-SNAPSHOT (20121220-0033)

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