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 want to have (have already) all basic functionality which comes out of the box with standard asp.net membership like: ValidateUser, CreateUser, ChangePassword etc..
But I want to separate it out to a different layer, I don’t want the web application to have access directly to the database.
The question is should I try to use standard membership, or do I need implement everything from scratch?
Perhaps this may be something you are looking for?
http://www.codeproject.com/KB/aspnet/WSSecurityProvider.aspx
Hope it helps.