when connect my user with the db at othermachin, how i can resolve it?

Question

Hi Guys
2021-05-06 10:51:47.399 UTC [35] FATAL: password authentication failed for user "chandu"
2021-05-06 10:51:47.399 UTC [35] DETAIL: User "chandu" does not have a valid SCRAM secret.
Connection matched pg_hba.conf line 99: "host all all all scram-sha-256"
I have this problem when connect my user with the db, how i can resolve it?

Rajanikant Hawaldar · Answer

There an underscore ALL_TABLES

Chandu K · Answer

psql --username "postgres" -c "CREATE USER chandu WITH PASSWORD 'Password01!';" psql --username "postgres" -c "CREATE DATABASE chandudb WITH OWNER = chandu ENCODING = 'UTF8' CONNECTION LIMIT = -1;" echo "Creato database chandudb" psql --username "postgres" -d "chandudb" < /docker-entrypoint-initdb.d/schema.sql

Chandu K · Answer

Thanks for help

Chandu K · Answer

GRANT SELECT,INSERT,UPDATE ON ALL_TABLES IN SCHEMA public TO chanduYou see some syntax error ,near IN?

Chandu K · Answer

OK, it's 12, problem is was docker volume

Rajanikant Hawaldar · Answer

what's your PG version? search "How to Upgrade Your PostgreSQL Passwords to SCRAM" The usual error with non-scram password is because the password_encryption setting is not set to scram-sha-256 when setting the user password.

Chandu K · Answer

# TYPE DATABASE USER ADDRESS METHOD # "local" is for Unix domain socket connections only local all all trust # IPv4 local connections: host all all 127.0.0.1/32 trust # IPv6 local connections: host all all ::1/128 scram-sha-256 host all chandu 0.0.0.0/32 scram-sha-256 # Allow replication connections from localhost, by a user with the # replication privilege. local replication all trust host replication all 127.0.0.1/32 trust host replication all ::1/128 trust host replication chandu 0.0.0.0/32 scram-sha-256

Chandu K · Answer

I will post the setup and instructions and tell me what configurations are missing . Thanks

Rajanikant Hawaldar · Answer

Seems you are storing passwords not with scram. You could either, change the users password, or changing/adding a line in pg_hba.conf with the correct password algorithm.