Just try the echo statement and check what it is printing in the
model.May be the sha1 will be using Time.now function also in addtion
to its own coding.The time that value is authenticated and the time
when u are checking the authentication will be different
The solution is if the sha1 is
Ouch - I simply used Digest::SHA256 instead of Digest::SHA2 and it
works now.
On Dec 27, 8:44 am, Sav savar...@gmail.com wrote:
I'm migrating a working app to a new server, but all my authentication
tests are failing on SHA2. The user.rb model has require 'digest/
sha2' at the top, yet I
2 matches
Mail list logo