Store hashed password using Digest authentication Digest Authentication is something like this:


Server sends client a nonce.
Client hashes username and password with nonce.
Client sends hashed value back to server.
Server validates hash.


However, it seems like this requires the server to have access to the password plaintext, otherwise it wouldn't be possible to verify each hash with unique nonce values.

Is there some way to follow this authentication protocol without requiring the server to have access to password plaintexts?
The server doesn't need the plaintext.  When the password was "saved" the server generated a nonce and concatenated that with the password and then hashed the combination.  The server saves the nonce and the hash, not the password.  Now, when client sends the hashed value to the server all the server does is compare that it against the saved value.