|
That will depend on how you have user information stored in your ASP.NET 1.1 member database. You can programmatically access the membership providers that are used to support the ASP.NET 2.0 membership and authentication controls. Therefore, it should be possible to write a script that would access your ASP.NET 1.1 user data store, retrieve the users and migrate their information to the ASP.NET 2.0 data store using methods such as CreateUser(). You could probably reverse engineer the table structure of the ASP.NET 2.0 membership data store, but you are better off using the provider methods to help ensure that the new ASP.NET 2.0 users are properly set up.
If you have hashed the passwords in the ASP.NET 1.1. user data store such that they are unrecoverable, then you have a more challenging migration situation. In order to move the users into the new ASP.NET 2.0 data store you could assign all users a new password and email them their new login information. This is not a terribly attractive approach because emails are unencrypted and subject to interception and other eavesdropping. Also, given the rise of phishing attacks savvy users are likely to be spooked by these suspicious-looking emails.
If you have stored password recovery questions and answers for your ASP.NET 1.1 users, you could migrate the users as mentioned above, giving them random, unknown passwords. When the user tries to log in to your application again they could present the answer to the password recovery question and re-set their password for use on the new system. This is a somewhat awkward approach that could be improved with the appropriate warnings in the login page to help coach existing users through their first login to the new system.
More information:
|
