Error on 3.2.2 for hash password?

HI, is there a bug on hashing passwords for the login setup? I am windows 10, wappler 3.2.2.

I have been building a new login setup (following the video). it all works fine except when I add a hashed salt password.

I have created a new user page/server app etc, for new user and login, the query to do the new user insert has a hash 512 salt password set on the query, and the security login for the login server app has the salt with the same word on the $POST. If I remove the salt/hash from both I can sign in, create users. If I add the salt to both (using same word) I cannot sign in, I can see in my DB it inserts the new user and the password is hashed, but signing in just gives me a 401 so it’s failing on the hash I believe.

Had this working on an earlier project I played around with in wappler 3.0.0 no problems, but in 3.2.2 I cannot sign in, sat here for hours looking at it, changing salt words, saving, refreshing, checking the DB etc, I just cant phathom it :frowning:


Thanks
Darren

Are you sure your database field length is enough to store sha512 hash?

Yeah, as it’s storing it, it’s set to varchar 300 and think it needs 128
Thanks

believe I solved it, change varchar to char(128) and seems to now work, odd, its the only thing I changed, so must be something about a varchar

There is no reason for it to work with char and not with a car har field. Tested both and both work fine for me. Maybe something else was not properly setup for your field.

no idea, but all I changed was that one thing, var(300) to char(128) and boom it worked :slight_smile: