How do I modify the .NET Identity Template, so that my ASP.NET Web Forms Application could use a new field

Question

0.00/5 (No votes)

See more:

Hello good day everyone,
I need help on modifying the .NET Identity Template, so that my ASP.NET Web Forms Application could use a new field I will include as a unique identifier, when registering new users on the site?

Since the Register Template only has three (3) fields viz; USERNAME, PASSWORD, CONFIRM PASSWORD. I would like to include another field, REGISTRATION NUMBER which should be the unique constraint [Request 1]

I have been able to Create the REGISRATION NUMBER field on the Register Page of the Application, however, its values are not even stored in the ASPNETUSERS Table. Any suggestions on how to go about it, please? [Request 2]

Posted 9-Sep-14 6:56am

Arthur Ezenwanne

Add a Solution

Comments

j snooze 9-Sep-14 17:09pm

Add the field to the users table and modify the applicationuser class to have a registration number property.

Arthur Ezenwanne 10-Sep-14 9:21am

Thank you J Snooze for the insight.

However, concerning my REQUEST 1, could you instruct me on how to change the USERNAME PROPERTY FIELD from being unique on the site and instead make the REGISTRATION NUMBER PROPERTY FIELD to be unique.

j snooze 10-Sep-14 9:23am

http://www.asp.net/identity/overview/extensibility/change-primary-key-for-users-in-aspnet-identity

Christian Amado 10-Sep-14 10:59am

There are some articles about this scenario in Google!

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)