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 will be launching an mvc3 project soon. The project will be run on multiple servers which all point to the same database. The project uses ASP.Net’s membership provider. I need to ensure that a user created on Server 1 will be able to login to Server 2.
Question: Will there be any issues with automatically generated enryption/decryption keys that the membership provider uses?
We use the
MembershipProvider(we derive our own version of it) for a load-balanced application and I haven’t had an issue with it.As for the default
SqlMembershipProvider, if you’re either hashing your passwords or storing them in clear text, you should be fine. If you’re encrypting them, just make sure that your web servers all have the same key values in the machine.config’s<machineKey>configuration section. See this article for more information.