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

Ability to resend verification email #1492

Closed
tzarebczan opened this Issue May 18, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@tzarebczan
Member

tzarebczan commented May 18, 2018

The Issue

Possibly related to #997.

If a user begins the email verification process but never completes (doesn't go into email, get verification code), there is currently no way to re-send the email besides following the manual instructions to clear their login token. If they still have the old email, they can grab the verification code, but that will trigger a new email since it's expired, so they have to do it again.

Instead, we should add a link to resend verification email on the verification input screen.

System Configuration

  • LBRY Daemon version:
  • LBRY App version:
  • LBRY Installation ID:
  • Operating system:

Anything Else

Screenshots

@amitnndn

This comment has been minimized.

Show comment
Hide comment
@amitnndn

amitnndn Jun 6, 2018

Contributor

I am trying to take a dig at this one. @tzarebczan

I understand that when a user first registers their email, there is a call to LBRY API's user_email/new end point and since that one is for a new user, I am thinking that it should ideally create a conflict if I am trying to reuse the same funciton from the first step where the user enters their email for the first time.

Is there any documentation available on what kind of API calls that I can use to resend the user email. I am thinking maybe changing the end-point will work, but I am not sure what the end point is. It would be great if you could point me to any documentation that is available or provide me with the actual end point.

Thanks!

Contributor

amitnndn commented Jun 6, 2018

I am trying to take a dig at this one. @tzarebczan

I understand that when a user first registers their email, there is a call to LBRY API's user_email/new end point and since that one is for a new user, I am thinking that it should ideally create a conflict if I am trying to reuse the same funciton from the first step where the user enters their email for the first time.

Is there any documentation available on what kind of API calls that I can use to resend the user email. I am thinking maybe changing the end-point will work, but I am not sure what the end point is. It would be great if you could point me to any documentation that is available or provide me with the actual end point.

Thanks!

@kauffj

This comment has been minimized.

Show comment
Hide comment
@kauffj

kauffj Jun 6, 2018

Member

Hi @amitnndn! Thanks for taking this on.

You can call /user_email/resend_token?email=xxx@example.com.

This API is not publicly documented as it is primarily intended for our internal use.

Member

kauffj commented Jun 6, 2018

Hi @amitnndn! Thanks for taking this on.

You can call /user_email/resend_token?email=xxx@example.com.

This API is not publicly documented as it is primarily intended for our internal use.

@amitnndn

This comment has been minimized.

Show comment
Hide comment
@amitnndn

amitnndn Jun 6, 2018

Contributor

Perfect! Thank you @kauffj !

Contributor

amitnndn commented Jun 6, 2018

Perfect! Thank you @kauffj !

amitnndn added a commit to amitnndn/lbry-app that referenced this issue Jun 7, 2018

amitnndn added a commit to amitnndn/lbry-app that referenced this issue Jun 7, 2018

amitnndn added a commit to amitnndn/lbry-app that referenced this issue Jun 7, 2018

amitnndn added a commit to amitnndn/lbry-app that referenced this issue Jun 8, 2018

@tiger5226

This comment has been minimized.

Show comment
Hide comment
@tiger5226

tiger5226 Jun 11, 2018

Member

solved and merged

Member

tiger5226 commented Jun 11, 2018

solved and merged

@tiger5226 tiger5226 closed this Jun 11, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment