Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If a Google button signup fallbacks because of username don't force to validate email #4187

Closed
juanignaciosl opened this issue Jun 24, 2015 · 0 comments · Fixed by #4825
Closed
Assignees

Comments

@juanignaciosl
Copy link
Contributor

See #3902. If you try to signup in a organization with google and username is taken you are forced to validate your email, but it shouldn't be needed.

Steps (change username with a username of a Google account you own):

  1. New incognito window. Create a "username", "username@non-google-domain.com" user.
  2. New incognito window. Try to do a sigup with "username@google-domain.com". Since username is taken you're prompted with the fallback screen asking you for a new username. Create the user. User is created but you must "check your email and activate your account". Since you can sign up with your google account that should not be necessary.
@juanignaciosl juanignaciosl self-assigned this Jun 24, 2015
@juanignaciosl juanignaciosl added this to the Calvos de Randín milestone Jun 24, 2015
@javisantana javisantana modified the milestone: Corcos Jul 9, 2015
@juanignaciosl juanignaciosl added this to the Villanueva del Pardillo milestone Jul 15, 2015
juanignaciosl added a commit that referenced this issue Aug 5, 2015
…fallbacks_because_of_username_dont_force_to_validate_email

google_access_token propagation and username setting fixes #4187
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants