I have an existing application in production that uses SqlMembershipProvider and has the specified machine key:
<machineKey validationKey="..." decryptionKey="..."
validation="SHA1" decryption="AES"/>
It currently runs under .Net 2.0 AppPool.
I am writing a new application that should use an existing database in which I have a backup. I am trying to get SqlMembershipProvider to work with it (what it does), but I cannot get a known username / password. This account works in prod, and the hash and password salt are the same for both databases (prod and my). However, at the moment when SqlMembershipProvider compares the password from the database with the hashed password entered, they do not match.
This article suggests changing the changes using the default hashing algorithm in ASP.Net in .NET 4.0:
http://www.asp.net/learn/whitepapers/aspnet4/breaking-changes
However, I already indicate the machine key, as suggested. In addition, I removed the .Net 4.0 components and dropped it to 3.5 (this is CLR 2), and the hash of the entered password is still the same.
In addition, I tried to redistribute this new temporary application on the same server as the server, and it still cannot log in (although I can’t check if it worked because of a password hash mismatch).
What else can I try here?
source
share