Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am planning to create a component that will be able to check user’s credentials (username and password) and, if they are valid, return associated profiles. I don’t want to use the providers that already exist in the .Net framework (I am trying to exercise my development skills ). Is there any pattern I can use? Or standards?
The membership providers are really nice, and you can definitely exercise your dev skills even if you use them. But you’d be developing something other than a user auth/profile service!.
If you truly want to roll it yourself, you need a store for the username and password hash. When users register, have them type in the password and then hash it. Store the username and password hash in whatever store you choose. Then, when a user logs in, you hash the pw they provide and check it against the stored hash.
For the simplest cases you could just use an XML file with a list of elements, one element per user, and you can use XmlSerialization to slurp it in and save it.
But you could also use a database, or AD/AM, some other store.