February 12, 2009 at 9:27 am
We are redesigning our databases and are now going to be using all of the aspnet_XXX tables. We are running to the problem of how to insert the existing usernames and passwords from the old (unencrypted) login tables into the new aspnet_membership table. The password field is an encrypted nvarchar(128) field.
Anyone have this problem?
February 13, 2009 at 2:28 pm
Yin Halen (2/12/2009)
We are redesigning our databases and are now going to be using all of the aspnet_XXX tables. We are running to the problem of how to insert the existing usernames and passwords from the old (unencrypted) login tables into the new aspnet_membership table. The password field is an encrypted nvarchar(128) field.Anyone have this problem?
Does your application have an option to store as unencrypted? You may have to do that if you can't insert the data otherwise. I'll bet the encryption routine is in the .NET app.
On another topic, Yin Halen, have you ever worked with Sagar? Anyway, I dig the music..
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy