Обсуждение: Logging on without prompt for password

Is there a way of enabling a user to logon without being prompted for password?  I know  there is the .pgpass file,  but this file requires the port#  and my server has several postgres clusters with different port#.    So,  am  not sure if I can use the .pgpass file.

 

And at the pg_hba.conf file,  the id already has ‘trust’ method, but it is still being prompted for password.

 

Have you tried PGPASSWORD env variable and unset it. I find it especially useful when scripting.

On Tue, Oct 20, 2015 at 10:38 AM, Rossi, Maria <maria.rossi@jackson.com> wrote:

Hi,

 

 

Is there a way of enabling a user to logon without being prompted for password?  I know  there is the .pgpass file,  but this file requires the port#  and my server has several postgres clusters with different port#.    So,  am  not sure if I can use the .pgpass file.

 

And at the pg_hba.conf file,  the id already has ‘trust’ method, but it is still being prompted for password.

 

This id will  be used for automated scanning and needs to run pg_dumpall.

 

Thanks.

 

Here’s what the automated discovery is using:

 

/usr/pgsql-9.3/bin/pg_dumpall" -U bmcap01 -s -x

 

And it got this error:

pg_dumpall: could not connect to database "template1": could not connect to server: No such file or directory 

Then, I retried the pg_dumpall with the –p (for port#) and it prompted for the password.

 

Thanks.

 

2015-10-20 14:15 GMT-02:00 Rossi, Maria <maria.rossi@jackson.com>:

Here’s what the automated discovery is using:

 

/usr/pgsql-9.3/bin/pg_dumpall" -U bmcap01 -s -x

 

And it got this error:

pg_dumpall: could not connect to database "template1": could not connect to server: No such file or directory 

Then, I retried the pg_dumpall with the –p (for port#) and it prompted for the password.

 

Thanks.

 

Hi,

 

 

Is there a way of enabling a user to logon without being prompted for password?  I know  there is the .pgpass file,  but this file requires the port#  and my server has several postgres clusters with different port#.    So,  am  not sure if I can use the .pgpass file.

 

And at the pg_hba.conf file,  the id already has ‘trust’ method, but it is still being prompted for password.

 

This id will  be used for automated scanning and needs to run pg_dumpall.

 

Thanks.

 

Maria A Rossi

Database Administration

PGDS (US)

email: maria.rossi@us.pgds.com
cell phone: 517.256.4392

work phone: 517.367.3099
work phone extension: 23099

 

Hi,

 

Back to  my original question, though.    Any ideas why it is still prompting for password even though it had ‘trust’ in the pg_hba.conf?    The .pgpass  or the PGPASSWORD is only  a work-around for that, I think.     ‘Trust’ is supposed to:

 

Allow the connection unconditionally. This method allows anyone that can connect to the PostgreSQL database server to login as any PostgreSQL user they wish, without the need for a password or any other authentication

 

So, I  shouldn’t need to set-up .pgpass or PGPASSWORD.

 

Any thoughts?

 

Thanks.

 

Maria A Rossi

Database Administration

PGDS (US)

email: maria.rossi@us.pgds.com
cell phone: 517.256.4392

work phone: 517.367.3099
work phone extension: 23099

 

From: Glauco Torres [mailto:torres.glauco@gmail.com]
Sent: Tuesday, October 20, 2015 1:54 PM
To: Rossi, Maria <maria.rossi@jackson.com>
Subject: Re: [ADMIN] Logging on without prompt for password

 

 

 

2015-10-20 15:50 GMT-02:00 Glauco Torres <torres.glauco@gmail.com>:

 

 

2015-10-20 15:44 GMT-02:00 Rossi, Maria <maria.rossi@jackson.com>:

Hi,

 

We will  try the .pgpass file at the user’s home directory, using *.* for port  as suggested by Scott Mead.    This way I don’t  have to worry about setting the  PGPASSWORD env var for the user.

 

I still need to create a role for the user, correct?  It needs admin to be able to rung pg_dumpall.

 

Thanks everyone.

 

 

 

The manual helps a lot in these types of doubts


"Also you will need superuser privileges to execute the saved script in order to be allowed to add users and groups, and to create databases."

http://www.postgresql.org/docs/current/static/app-pg-dumpall.html

 

 

Sorry,

O copied the wrong part "Since pg_dumpall reads tables from all databases you will most likely have to connect as a database superuser in order to produce a complete dump."