{"id":7,"date":"2008-05-16T09:11:00","date_gmt":"2008-05-16T03:41:00","guid":{"rendered":"http:\/\/guganeshan.com\/blog\/?p=7"},"modified":"2009-12-18T14:02:03","modified_gmt":"2009-12-18T08:32:03","slug":"resetting-asp-net-membership-password-when-the-user-has-forgotton-the-answer-for-the-security-question","status":"publish","type":"post","link":"https:\/\/guganeshan.com\/blog\/resetting-asp-net-membership-password-when-the-user-has-forgotton-the-answer-for-the-security-question.html","title":{"rendered":"Resetting asp.net membership password when the user has forgotton the answer for the security question!"},"content":{"rendered":"

Here is the scenario… a web application has been implemented with the standard user management features… can create new users, the admin approves the users, can recover passwords and change security question + answer bla bla bla<\/p>\n

What happens if a user forgets the password?… simple, just goto the password recovery page and answer the security question and get the new password in the email.<\/p>\n

But what if he\/she doesn’t remember the answer for the security question???<\/p>\n

Well, this is what happened exactly today. Although there were some solutions on the net, they required you to create a temporary Membership provider in the config etc.. which I didn’t like doing.<\/p>\n

But for my joy, I found this post<\/a> that gave me the idea. Although it is not a clean solution to the problem, it was what I wanted for the urgent need of resetting the password (since this won’t happen too often)<\/p>\n

The post<\/a> says that you have to replace the password hash and salt with the password hash and salt of a user whose password you know! What a simple idea. Well, whose password do I know?? mine of course!<\/p>\n

So this is what I did:<\/p>\n

    \n
  1. Changed my password to something like password_999<\/li>\n
  2. Replaced the user’s (who doesn’t remember the security answer) password hash and salt with my hash and salt<\/li>\n
  3. Changed my password back<\/li>\n
  4. Gave him ‘password_999’ as the password, which he obviously will have to change once he logged in<\/li>\n<\/ol>\n

    A more hassle-free solution would be to always have a dummy user account in the Membership database, which we can keep locked or as unapproved. And to make things even simpler, we can deploy an admin’s page that can accept the user name and replace the password hash and salt (copied from the dummy user account)… thanks to Tim Huffam<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

    Here is the scenario… a web application has been implemented with the standard user management features… can create new users, the admin approves the users, can recover passwords and change security question + answer bla bla bla What happens if a user forgets the password?… simple, just goto the password recovery page and answer the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7,9],"tags":[23,30,29,68],"class_list":["post-7","post","type-post","status-publish","format-standard","hentry","category-programming","category-troubleshooting","tag-net","tag-asp-net","tag-tips","tag-troubleshooting"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t