I am using Argon Hash for user passwords.
On my development instance all works 100%, but once web app is deployed to hosted Docker image, it does not work and returns unauthorised.
Anyone knows why this would be? I can change the password to the non hashed version in DB and then user can login, but that defeats the point of using the hash.
Sorry no solution, but we’re using argon without issues between dev and production.
Now I do remember having some issues when we just switched to argon (when it was released in Wappler) (node project). But can’t remember what it was 
Is it node?
yes it is node.js
Hmm sorry can’t find anything in my documentation about it. Just that users had to reset their pass to make the switch to the new encryption.
Only things I can think of is that it’s a db connection issue / some form of caching
Not sure if you’ve already tried. Could you try installing the node packages on live site. Don’t think this runs automatically on deploy now.
I tried the password reset already.
I installed node packages and ran update as well. No luck.
Not sure if it helps but we had an identical issue with Argon and NodeJS . Worked fine locally but not when deployed to the server.
It turns out the Argon module wasn’t present in the server. Once added to the server it was all fine.
Maybe check yours to make sure that module is present on the server side.
That basically means Argon changes have not been deployed to production server.
Try connecting production DB to your local instance, and see if the login works.
We are using Argon in a few projects, without any issues. We recently changed from SHA to Argon in a project, and things went smoothly.
Could the argon hash work partially due to packages not installed correctly? The hashing on password save works.
It is just the login that does not…
Haven’t seen that actually. If package is not installed all Argon steps give module not found error.
Check the secrets/salts that you might have configured in the env variables set in the config files
The security provider is configured per target. Have you checked the same settings as the dev environment are in there. If they have changed since you set up the target, they may not have pulled through