Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Membership password troubles
Message
 
À
Tous
Information générale
Forum:
ASP.NET
Catégorie:
Autre
Titre:
Membership password troubles
Versions des environnements
Environment:
ASP.NET
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
MS SQL Server
Divers
Thread ID:
01227553
Message ID:
01227553
Vues:
60
Hi,

I had conversed with someone about this but have gotten no response in several days, so I am asking everyone again. I have been having trouble getting the membership feature working in ASP.NET 2. I am using Visual Studio 2005. I was referred to an article on the subject on the 4 Guys from Rolla website. It was very good, and I got some results, but all is not well. Here is the last reply I made to the person here:

I discovered that using the configuration tool kept referring to the local SQL Express database. So after putting in what seemed to be the required code (in the web.config file) I used ftp to upload the web.config, Login.aspx, Default.aspx and Memebers.aspx pages to try it out. On the login page I clicked on the create an account link and all seemed to go well. But when I tried to log in via the browser I got the error message that the user name or password was incorrect. Something is still wrong, and I can't figure it out with my limited experience in this technology. I used the SQL Query analyzer to look at the data that was created and the password is certainly encrypted. I am wondering if it is not being decrypted in the same way it was encrypted when created.

I was all happy when the create user form seemed to work. Then the brick wall hit me again. I followed their instructions concerning viewStateEncryptionMode (set to "Auto"), enableViewStateMac="true", setting the validationKey for the viewState and validation to "SHA1". That was all supposed to refer to viewState encryption. I set the key to the length they suggest and set the decryptionKey to the 64 character length. Decryption is set to "AES". I used the sample in the help on generating machine keys to create the encryption key generator console application and ran it and copied and pasted the results. Strangely, the results were one character longer than required, which caused an error. When I deleted one the error went away. I am wondering now if the validationKey should have been set to the same thing as the decryptionKey. Could this be the problem?

I will post the code if it will help. Just let me know.

I hope someone can help, I really want to use the membership and roles features now that I see how they can be used to make life easier.

Thanks,
Dana
Where's the damned Any Key?...too late
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform