Probably because the web.config now specifies to store password in "Hashed" format rather than "Clear". Check the membership provider and set it to the same value as your old website's web.config
I was using a ControlAdapter to re-format the Login control without a HTML table. As is it now ASP.NET 4, I can do it without the adapter using RenderOuterTable and using the Templates.
Just to double check: the problem was not in the hashes generated by the console app then? Because if that piece of code would be causing issues I'd have to add proper warnings/notifications to the original post. Although I thought I double checked the code repository for the algorithm that is currently used...
Updated v4 -> v4.5 but members cannot login
I cannot log into my website as a end user (a 'member') after upgrading Umbraco to v4.5.
I have tried resetting the passwords, but it still doesn't work.
Probably because the web.config now specifies to store password in "Hashed" format rather than "Clear". Check the membership provider and set it to the same value as your old website's web.config
If you need to hash password, there's someone who's written some code to change passwords using a batch console app (use with care!)
Cheers,
/Dirk
Hi Dirk - sorry, I should have said that I did try hashing the passwords using that console app, but that doesn't help.
Lee
Hmm, strange, but next step would be to either debug (if you can), or profile your sql to check what's going wrong. Frankly, currently out of ideas...
Cheers,
/Dirk
Any other changes except for umbraco version? .net version? Seems password hashing is quite different when changing from 3.5 to 4.0 (see this link)
I moved from .NET 3.5 to 4 at the same time (I've also moved to a new server).
I've resolved the problem.
I was using a ControlAdapter to re-format the Login control without a HTML table. As is it now ASP.NET 4, I can do it without the adapter using RenderOuterTable and using the Templates.
Thanks for your help.
Just to double check: the problem was not in the hashes generated by the console app then? Because if that piece of code would be causing issues I'd have to add proper warnings/notifications to the original post. Although I thought I double checked the code repository for the algorithm that is currently used...
Hi Kris
I can confirm that the console app was not the problem - it worked fine.
Thanks
Lee
is working on a reply...