0

For email verification during user registration which method would be better if we are taking following (or more - which I am missing) points:

From user point of view

  • Authenticity - Fear of clicking to scary looking URLs
  • Ease of use - as in case of URL based method user just needs to click the URL and token based method will require user to copy and then paste to the particular verify field

From user + developer point of view

  • Reliability - Maintaining each method like expiration of each.
  • Any other point that I am missing

Note: For link expiration I have already read this post but that doesn't cover expiration of token based method.

marked as duplicate by msp, Matt Obee, JonW Apr 28 '15 at 12:33

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • Can you explain more what you mean by token based vs url based? token-based email verification still uses URL's as far as I know, so i'm not sure i understand what you mean, thanks – tohster Apr 28 '15 at 8:37
1

Your con for email authentication by URL is that the URL is longer and scarier looking than the shorter URL to the location where people can enter a code.

But you can simply hide the long and scary URL behind a bright and inviting button. True, you would have to display the entire URL for people to copy and paste in their browser, because some email clients don't support links, but you can style these links to be less scary. Just put them in a box (border or background color) and decrease contrast between font color and background color.

Not the answer you're looking for? Browse other questions tagged or ask your own question.