Psql ошибка пользователь не прошел проверку подлинности

тоже была такая проблема, с паролем и не находил путь.

решение:

1. прописал путь в переменных средах.
2. Работает только через командную строку, через PowerShell не работает (у меня)

Steve BennettSteve Bennett

5,78012 gold badges47 silver badges59 bronze badges

It means that Postgres is trying to authenticate a user using the Ident protocol, and can’t. Ident auth automatically matches Unix usernames with Postgres usernames. It works like this:

• You have database role ‘foo’ on database ‘db’
• Your pg_hba.conf file (in /etc/postgres-something/main) defines ‘Ident’ as the protocol to connect to database db for users connecting from certain hosts
• The unix username making the connection is ‘foo’
• An Ident server running on the machine the user is connecting from confirms that their username really is ‘foo’

Possible causes and solutions:

1. There is no Ident server running on the machine you’re trying to connect from. Test this by trying to connect to it on port 113. If that fails, install an Ident server (eg, sudo apt-get install oidentd).

2. There’s an Ident server, but there’s no database role matching the name you’re trying to connect with (‘foo’ in the above example). So create it by connecting somehow to the database with superuser rights and do CREATE ROLE foo. Alternatively add an entry to /etc/postgresql/.../main/pg_ident.conf (or /var/lib/pgsql/12/data or wherever).

3. Maybe the shell username doesn’t match the database role. You may be able to test this by connecting to the Ident server while a connection is going on, and passing the right port numbers.

4. Maybe you actually want to connect with a password, not Ident. Edit the pg_hba.conf file appropriately. For example, change:

   host all all 127.0.0.1/32 ident
   

to

    host all all 127.0.0.1/32 md5

Be sure to restart Postgres after updating the pg_hba.conf file. You do that by issuing the following command:

    sudo service postgresql-12 restart
   

answered Jul 11, 2012 at 0:44

Not sure about the causes, but this fixed it for me:

in pg_hba.conf

change to this:

host all all 127.0.0.1/32 md5

Exact error: Caused by: org.postgresql.util.PSQLException: FATAL: Ident authentication failed for user "postgres"

answered Sep 10, 2012 at 15:21

For Centos 7, Change pg_hba.conf to below:

# TYPE  DATABASE        USER            ADDRESS                 METHOD

# "local" is for Unix domain socket connections only
local   all             all                                     peer
# IPv4 local connections:
#host    all             all             127.0.0.1/32            ident
host    all             all             127.0.0.1/32            md5
# IPv6 local connections:
#host    all             all             ::1/128                 ident
host    all             all             ::1/128                 md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
#local   replication     all                                     peer
#host    replication     all             127.0.0.1/32            ident
#host    replication     all             ::1/128                 ident

On CentOS, add the following line to /var/lib/pgsql/9.3/data/pg_hba.conf:

host all all 127.0.0.1/32 trust

And comment out the other entries.

Of course, this setting is not secure, but if you’re just messing about on a development VM like me then it’s probably fine…

answered Jul 14, 2014 at 11:11

If you have not tried this already, review your pg_hba.conf file. It will be named something like /var/lib/pgsql/9.3/data/pg_hba.conf (Fedora 20); you may have to use ‘find / -name pg_hba.conf’ to locate it.

At the bottom of the file, change the ‘METHOD’ values to ‘trust’ for local testing (see postgres docs for full information). Reboot the machine to ensure everything is started clean and the new params are read.

Hopefully this will cure your woes. It solved my problems on Fedora 20 with PostgreSQL 9.3.

answered Jul 26, 2014 at 0:59

Evan Carroll

61.4k45 gold badges229 silver badges462 bronze badges

In a fresh install from a few days ago, the second line of my pg_hba.conf is

local   all             all              peer

I believe this is the one that makes your connection attempt fail.

The order of rules matter here: the first one that matches the access method, username, database name and source IP range will be considered. If it fails, then there is no second try, so the connection attempt will likely fail. Or, as the documentation states:

There is no «fall-through» or «backup»: if one record is chosen and the authentication fails, subsequent records are not considered. If no record matches, access is denied.

The solution is easy: either remove the above line if you don’t plan to use peer authentication, or move your specific rule above this one.

First of all, check if you have the lines giving permission to the myuser user in pg_hba.conf. For example:

# IPv4 local connections:
host    all             all             127.0.0.1/32            md5
# IPv6 local connections:
host    all             all             ::1/128                 md5

Or any other lines of permission to IPV4 (and IPv6 if you use) with: TYPE DATABASE USER ADDRESS METHOD

After this check, run the psql as follows:

psql -h localhost -U myuser mydatabase

And then, the requested prompt, enter the user’s password myuser.