Description of problem:
Currently, if Zanata fails to verify the email of a fedora contributor, the contributor's account will be disabled, and he/she can no longer login.
However, it will be more convenient for contributors to login, change email, then re-verify the account.
Version-Release number of selected component (if applicable):
Zanata version 1.4-SNAPSHOT (20110901-1705)
Steps to Reproduce:
1. Assume a contributor has not register in Zanata.
2. The contributor follow the registration process, but enter an invalid email address.
3. The contributor relogin
User XXXX has been disabled. Please check your email for a validation code, or contact server admin.
User XXXX can still login to change his/her email, yet the account is still inactivate until the email can be verified.
Actually, this isn't specific to Fedora authentication. It applies to any new user who doesn't receive the account validation email. Internal or external authentication.
Assigning to Scrum product owner for prioritisation.
Added workaround for this bug: When no domain is configured on the server, new users will be forced to enter their email address. The server won't try to "guess" it.
Carlos's workaround looks okay to me. Dean, could you please check that and then remove this bug from the Zanata-1.4 blockers?
Mmm, admin deleting the user then user re-register with zanata (not for fedora authentication) seems does the trick, so I can remove this as blocker.
Then again, Carlos' workaround does not quite solve following scenario:
2. people might still filling in email@example.com
So this bug can't be closed yet.
*** This bug has been marked as a duplicate of bug 803923 ***