How do you store passwords in ASP.NET Identity?
PICTURE THIS: HASH MAP
Simple meaning
Identity hashes with a strong algorithm and salt via PasswordHasher.
WHY — Security instead of guessing?
Why interviewers care about Security:
question about Security.
trade-offs, and what you would actually do on a .NET project - not buzzwords.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Identity hashes with a
strong algorithm and salt via PasswordHasher.
- 2Why it exists
I never store plain text.
- 3Lockout and complexity policies
sit on top.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Identity hashes with a strong algorithm and salt via PasswordHasher. I never store plain text.