Disable all previous generated passwordresettoken generated by application user manager ASP.NET identity

Question

0.00/5 (No votes)

See more:

Dears,

I am handling user reset password in my APP and i am using the following code:

if the user clicks forget password, system generates token by the following code:

C#

var token = manager.GeneratePasswordResetToken(userId);

Generated token sent to user email with a link to update his new password.

if the token is verified using the following code:

C#

UserManager.VerifyUserToken(UserId, "ResetPassword", token)

the user update his password.

C#

UserManager.ResetPassword(user.Id, model.token, model.Password)

Now what if the user generated more than one token?
The current behavior, Any token opened will disable the other tokens. this is handled by ASP.net Identity.

I want disable all previous generated tokens while generating a new token. IS THIS APPLICAPLE?

What I have tried:

Generate a table for and saved all tokens. it works fine but i am looking for a better solution auto generated by ASP.NET Identity.

Posted 19-Jan-19 20:19pm

_ProgProg_

Updated 30-Dec-20 22:58pm

v2

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2019-01-20T04:48:00

Solution 1

Ummm.... You just said that you want to "disable all previous generated tokens while generating a new token", but that's exactly what you said the "current behavior" already does, "Any token opened will disable the other tokens".

Posted 20-Jan-19 4:48am

Dave Kreskowiak

Comments

_ProgProg_ 21-Jan-19 0:47am

The current behavior is:
You can generate many tokens, but when you use one of them for resetting, the others are disabled. I want to disable all previous while generating new.

Dave Kreskowiak 21-Jan-19 16:51pm

Why would you want to?

_ProgProg_ 22-Jan-19 0:32am

Now i save all tokens in a DB Table then i am validating only the latest one. But if there is a way to get all tokens using identity with each token date that will be better.

Dave Kreskowiak 22-Jan-19 16:42pm

How is that "better" and for who?

majid1989 · Answer 2 · 2020-12-30T22:58:00

Solution 2

The default UserTokenProvider generates tokens based on the users's SecurityStamp, so until that changes(like when the user's password changes), the tokens will always be the same, and remain valid.

So if you want to simply invalidate old tokens, just call:

manager.UpdateSecurityStampAsync(user);

Posted 30-Dec-20 22:58pm

majid1989

Updated 31-Dec-20 9:21am

v2