Обсуждение: pgadmin 1.4 not remembering password

I just installed pgadmin 1.4.  When I create a new connection and
supply the password, it only seems to remember it until I restart.
Then I get the message "Error connection to the server: fe_sendauth:
no password supplied"

When I look at %APPDATA%/postgresql/pgpass.conf it look normal with
the password and all.  Is there something I am missing?

Regards,
Collin

Mitch S McKenzie wrote:
> 
> I have the same problem on the latest snapshot 1.5 

I could not reproduce this. Please provide specific information about a 
user that has this problem, i.e. post me the exact role name and 
pgpass.conf line, and a description how you create/use the connection 
using that login role. The only way I could produce the fe_auth message 
was by deleting the password in pgpass.conf. If this is what you did, 
the advice is "don't use an empty password".

Regards,
Andreas

.
> 
> It would be nice if it work but it is not critical.
> 
> Mitch McKenzie
> Programmer/Analyst_
> __Learning Environment & Internet Services_ <http://app1.unmc.edu/leis>
> University of Nebraska Medical Center
> Phone: 402-559-9306
> Cell Phone: 402-708-1493
> *
> University of Nebraska Medical Center E-mail Confidentiality Disclaimer :*
> The information in this e-mail is privileged and confidential, intended 
> only for the use of the addressee(s) above.
> Any unauthorized use or disclosure of this information is prohibited.
> If you have received this e-mail by mistake please delete it and 
> immediately contact the sender.
> 
> 
> *Collin Peters <cadiolis@gmail.com>*
> Sent by: pgadmin-support-owner@postgresql.org
> 
> 12/01/2005 11:49 AM
> 
>     
> To
>     pgadmin-support@postgresql.org
> cc
>     
> Subject
>     [pgadmin-support] pgadmin 1.4 not remembering password
> 
> 
>     
> 
> 
> 
> 
> 
> I just installed pgadmin 1.4.  When I create a new connection and
> supply the password, it only seems to remember it until I restart.
> Then I get the message "Error connection to the server: fe_sendauth:
> no password supplied"
> 
> When I look at %APPDATA%/postgresql/pgpass.conf it look normal with
> the password and all.  Is there something I am missing?
> 
> Regards,
> Collin
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
> 

Mitch S McKenzie wrote:
> 
> To reproduce the problem:
> 
> 1. Open pgAdmin
> 2. Double click on server to connect to.  On the "Connect to Server" 
> dialogue box check "Store Password" and enter your password.
> 3. Close pgAdmin.
> 4. Reopen pgAdmin and try to connect to the same server.  You will be 
> the following error: "Error connecting to the server: fe_sendauth: no 
> password supplied"

That's how it is supposed to work (and how it does work for me) if you 
press OK (and thus actually connect) to the server as step 2.1. If you 
don't, and just abort the dialog, you can't expect pgAdmin to do anything...

Regards,
Andreas

Mitch S McKenzie wrote:
> 
> That's how it's suppose to work???  Throwing and error???
> 
> hrmmmm......
> 
> So it's only suppose to save your password for the duration you have the 
> application open?

No, it's supposed to save it if you press OK! In addition, it will 
remember it until you close pgAdmin. The next time, it relies on 
pgpass.conf to contain the correct password, and has no more knowledge 
of the pwd.

Regards,
Andreas

We, too, have found that the save-password does NOT work as described. Even
when OK is pressed fervently.

________________________________

David Fisher
Pres.
Fisher Aircraft Corporation
Two Cairn Street    Rochester, New York 14611-2416
info@ep4.org    585.889.4026

Omnia extares!



-------Original Message-----
--From: pgadmin-support-owner@postgresql.org 
--[mailto:pgadmin-support-owner@postgresql.org] On Behalf Of 
--Andreas Pflug
--Sent: Monday, December 05, 2005 1:11 PM
--To: Mitch S McKenzie
--Cc: cadiolis@gmail.com; pgadmin-support@postgresql.org
--Subject: Re: [pgadmin-support] pgadmin 1.4 not remembering password
--
--Mitch S McKenzie wrote:
--> 
--> That's how it's suppose to work???  Throwing and error???
--> 
--> hrmmmm......
--> 
--> So it's only suppose to save your password for the duration 
--you have 
--> the application open?
--
--No, it's supposed to save it if you press OK! In addition, it 
--will remember it until you close pgAdmin. The next time, it 
--relies on pgpass.conf to contain the correct password, and 
--has no more knowledge of the pwd.
--
--Regards,
--Andreas
--
-----------------------------(end of 
--broadcast)---------------------------
--TIP 1: if posting/reading through Usenet, please send an appropriate
--       subscribe-nomail command to majordomo@postgresql.org 
--so that your
--       message can get through to the mailing list cleanly
--

David Fisher wrote:
> We, too, have found that the save-password does NOT work as described. Even
> when OK is pressed fervently.

I can't reproduce this, that's why I asked for precise information about 
user/password etc...

To repeat:
After pgAdmin has stored the password, it should reuse pgpass.conf, just 
as psql should (omitting password on the cmd line). Please try that, and 
modify pgpass.conf until it works, and post what has to be done, 
together with server encoding informations.

Regards,
Andreas

Mitch S McKenzie wrote:
> 
> Andreas,
> 
> Where is the pgpass.conf file??? 

Please search the docs for the path, don't have it at hand right now.

Do I have to create it?

pgAdmin does it for you.


> "In addition, it will remember it until you close pgAdmin."

remember internally, i.e. in RAM. This can't survive a restart, of 
course. But that's not necessary anyway if libpq's pgpass.conf mechanism 
works.

Regards,
Andreas

PS
Please don't post to pgadmin-support-owner@postgresql.org, that address 
is for mailing list maintenance only and might corrupt something.

This pgpass.conf file is NOT created by pgAdmin. It is not there. This may
be relevant?

________________________________

David Fisher
Pres.
Fisher Aircraft Corporation
Two Cairn Street    Rochester, New York 14611-2416
info@ep4.org    585.889.4026

Omnia extares!



-------Original Message-----
--From: pgadmin-support-owner@postgresql.org 
--[mailto:pgadmin-support-owner@postgresql.org] On Behalf Of 
--Andreas Pflug
--Sent: Monday, December 05, 2005 1:25 PM
--To: Mitch S McKenzie
--Cc: cadiolis@gmail.com; pgadmin-support@postgresql.org
--Subject: Re: [pgadmin-support] pgadmin 1.4 not remembering password
--
--Mitch S McKenzie wrote:
--> 
--> Andreas,
--> 
--> Where is the pgpass.conf file??? 
--
--Please search the docs for the path, don't have it at hand right now.
--
--Do I have to create it?
--
--pgAdmin does it for you.
--
--
--> "In addition, it will remember it until you close pgAdmin."
--
--remember internally, i.e. in RAM. This can't survive a 
--restart, of course. But that's not necessary anyway if 
--libpq's pgpass.conf mechanism works.
--
--Regards,
--Andreas
--
--PS
--Please don't post to pgadmin-support-owner@postgresql.org, 
--that address is for mailing list maintenance only and might 
--corrupt something.
--
-----------------------------(end of 
--broadcast)---------------------------
--TIP 4: Have you searched our list archives?
--
--               http://archives.postgresql.org
--

David Fisher wrote:

>This pgpass.conf file is NOT created by pgAdmin. It is not there. This may be relevant?
>  
>

Very funny. Since the password is stored there, surely nonexistence *is* 
relevant...
Do you have correct write access to your home directory? On English win32

C:\Documents and Settings\<Username>\Application Data\postgresql\pgpass.conf
or more exactly %APPDATA%\postgresql\pgpass.conf if you reconfigured 
something


Maybe you can scan your harddisk where the file is written, if not there 
(would be a security problem we need to fix immediately, we won't like 
files with confidential contents written into the wild, no?)

Regards,
Andreas

Sorry, my error. I had not looked for the file in the right place. How
embarrassing.

It IS where you say, and it does contain the correct IP and password data.
However, we still get the same behaviour. Open pgAdmin and double-click on
the server, get a connection error message, close that dialogue box,
double-click the same server again, and it then connects.

If that connection is closed without stopping pgAdmin, subsequent
connections do not raise the error but do ask for the password again.
- David
________________________________

David Fisher
Pres.
Fisher Aircraft Corporation
Two Cairn Street    Rochester, New York 14611-2416

info@ep4.org    585.889.4026


Omnia extares!



-------Original Message-----
--From: pgadmin-support-owner@postgresql.org 
--[mailto:pgadmin-support-owner@postgresql.org] On Behalf Of 
--Andreas Pflug
--Sent: Monday, December 05, 2005 5:41 PM
--To: ep4@frontiernet.net
--Cc: pgadmin-support@postgresql.org
--Subject: Re: [pgadmin-support] pgadmin 1.4 not remembering password
--
--David Fisher wrote:
--
-->This pgpass.conf file is NOT created by pgAdmin. It is not 
--there. This may be relevant?
-->  
-->
--
--Very funny. Since the password is stored there, surely 
--nonexistence *is* relevant...
--Do you have correct write access to your home directory? On 
--English win32
--
--C:\Documents and Settings\<Username>\Application 
--Data\postgresql\pgpass.conf or more exactly 
--%APPDATA%\postgresql\pgpass.conf if you reconfigured something
--
--
--Maybe you can scan your harddisk where the file is written, 
--if not there 
--(would be a security problem we need to fix immediately, we 
--won't like 
--files with confidential contents written into the wild, no?)
--
--Regards,
--Andreas
--
--
-----------------------------(end of 
--broadcast)---------------------------
--TIP 6: explain analyze is your friend
--

Oh, bother. Got it wrong. Subsequent reconnections do NOT ask for the
password again.

It's been a long day.....

It appears that this aberrant behaviour occurs on connections to another
computer but not on connections to a server on localhost.
- David

________________________________

David Fisher
Pres.
Fisher Aircraft Corporation
Two Cairn Street    Rochester, New York 14611-2416

info@ep4.org    585.889.4026


Omnia extares!



-------Original Message-----
--From: pgadmin-support-owner@postgresql.org 
--[mailto:pgadmin-support-owner@postgresql.org] On Behalf Of 
--Andreas Pflug
--Sent: Monday, December 05, 2005 5:41 PM
--To: ep4@frontiernet.net
--Cc: pgadmin-support@postgresql.org
--Subject: Re: [pgadmin-support] pgadmin 1.4 not remembering password
--
--David Fisher wrote:
--
-->This pgpass.conf file is NOT created by pgAdmin. It is not 
--there. This may be relevant?
-->  
-->
--
--Very funny. Since the password is stored there, surely 
--nonexistence *is* relevant...
--Do you have correct write access to your home directory? On 
--English win32
--
--C:\Documents and Settings\<Username>\Application 
--Data\postgresql\pgpass.conf or more exactly 
--%APPDATA%\postgresql\pgpass.conf if you reconfigured something
--
--
--Maybe you can scan your harddisk where the file is written, 
--if not there 
--(would be a security problem we need to fix immediately, we 
--won't like 
--files with confidential contents written into the wild, no?)
--
--Regards,
--Andreas
--
--
-----------------------------(end of 
--broadcast)---------------------------
--TIP 6: explain analyze is your friend
--

David Fisher wrote:

>Sorry, my error. I had not looked for the file in the right place. How
>embarrassing.
>
>It IS where you say, and it does contain the correct IP and password data.
>However, we still get the same behaviour. Open pgAdmin and double-click on
>the server, get a connection error message, close that dialogue box,
>double-click the same server again, and it then connects.
>  
>

So modify the file with an editor (username/passwd), and check again 
(close pgadmin and reopen it; after the first login failure pgadmin 
won't try the stored password again until you restart it; alternatively, 
use psql). Don't forget to save the old version, to compare changes.

Regards,
Andreas

David Fisher wrote:

>Changed the password in pgpass.conf, opened pgAdmin, went past the error
>msg, logged in with the correct password, closed pgAdmin; the correct
>password had been written to pgpass.conf.
>  
>
If pgAdmin doesn't ask for the password, it won't write it to the file, 
so your manual change was it. But what's the difference? Server locale, 
workstation locale, database encoding?

Regards,
Andreas

Guys,

Quick note that came in on one of the postgres lists, about storing
pg passwords for Win32 users.

>Do you have correct write access to your home directory? On English win32

>C:\Documents and Settings\<Username>\Application Data\postgresql\pgpass.conf
>or more exactly %APPDATA%\postgresql\pgpass.conf if you reconfigured 
>something

-- 
David T. Bath
System Analyst, Challenge Logistics
75-85 Nantilla Road, Clayton North Vic 3168
Voice: 131323 Fax: +613 8562 0002
bathdt@challengelogistics.com.au

============================================================
IMPORTANT - This email and any attachments is confidential.
If received in error, please contact the sender and delete
all copies of this email. Please note that any use,
dissemination, further distribution or reproduction of this
message in any form is strictly prohibited. Before opening or
using attachments, check them for viruses and defects.
Regardless of any loss, damage or consequence, whether caused
by the negligence of the sender or not, resulting directly or
indirectly from the use of any attached files, our liability
is limited to resupplying any affected attachments.  
Any representations or opinions expressed in this email are
those of the individual sender, and not necessarily those
of the Capital Transport Services.
============================================================

Although previous posts explicitely stated that no non-ascii chars where 
involved, I'm quite sure that this is in fact the problem. I created a 
user with a non-ascii password, and immediately was able to reproduce 
the problem.

Passwords entered in pgAdmin are in Unicode, and are converted when sent 
to the backend. Unfortunately, at connect time some default conversion 
rules are applied, so pgAdmin can't be sure whether converted or 
non-converted passwords are needed; it will try both when connecting 
interactively.

When libpq evaluates pgpass.conf (or ~.pgpass on *ix), it will *not* try 
several conversions, instead it will use the string as-is.

I changed pgAdmin now to store the pgpass info in the format that it has 
found suitable from the last successful connect. Please check the latest 
snapshot (win32 available now, *ix tomorrow after nightly build), and 
give me feedback if it works for you. If it does not, I really need the 
pgpass.conf line to dig further.

Regards,
Andreas

Collin Peters wrote:
> On 12/7/05, Andreas Pflug <pgadmin@pse-consulting.de> wrote:
> 
>>See www.pgadmin.org
> 
> 
> 1.5 snapshot did not work
> 
> I un-installed 1.4 (and my old 1.2 which I thought may cause some
> problems) and ran 1.5.  Same problem.... I noticed it still remembered
> my server info so I found a registry key (HKCU\Software\pgAdmin III)
> deleted it and then pgadmin seemed to start up fresh (tips started
> showing up again, etc..)  I then added a new server, and it was
> exactly like the process before.  i.e. same error, etc...
> 
> 
>>>By db/user/passwd details do you mean the contents of pgpass.conf?  If
>>>so it is
>>>
>>>127.0.0.1:5432:*:dbuser:dbpassword
> 
> 
> Well... not sure what else to say :)  Must be something in the OS...
> some DLL or something.  Like I said... the same setup works ok on
> other computers.

The new snapshot will log the password filename if debugging log is 
enabled; this should be consistent with what SET APPDATA returns on a 
command line. If not, let me know.

In addition, you could check for other libpq.dll versions sneaking 
around on your computer; report the version you're actually using.

All I can advise further is to check with psql and manually editing 
pgpass.conf, and post the difference.

Regards,
Andreas

An update to this thread for this issue for any future people having
the same problem

Found a fix for this.  It seems that if you have the address set to
'127.0.0.1' it does not correctly use the stored password but if you
use 'localhost' it does.  Very strange indeed.

On 12/9/05, Andreas Pflug <pgadmin@pse-consulting.de> wrote:
> Collin Peters wrote:
> > On 12/7/05, Andreas Pflug <pgadmin@pse-consulting.de> wrote:
> >
> >>See www.pgadmin.org
> >
> >
> > 1.5 snapshot did not work
> >
> > I un-installed 1.4 (and my old 1.2 which I thought may cause some
> > problems) and ran 1.5.  Same problem.... I noticed it still remembered
> > my server info so I found a registry key (HKCU\Software\pgAdmin III)
> > deleted it and then pgadmin seemed to start up fresh (tips started
> > showing up again, etc..)  I then added a new server, and it was
> > exactly like the process before.  i.e. same error, etc...
> >
> >
> >>>By db/user/passwd details do you mean the contents of pgpass.conf?  If
> >>>so it is
> >>>
> >>>127.0.0.1:5432:*:dbuser:dbpassword
> >
> >
> > Well... not sure what else to say :)  Must be something in the OS...
> > some DLL or something.  Like I said... the same setup works ok on
> > other computers.
>
> The new snapshot will log the password filename if debugging log is
> enabled; this should be consistent with what SET APPDATA returns on a
> command line. If not, let me know.
>
> In addition, you could check for other libpq.dll versions sneaking
> around on your computer; report the version you're actually using.
>
> All I can advise further is to check with psql and manually editing
> pgpass.conf, and post the difference.
>
> Regards,
> Andreas
>

On 29/3/06 19:34, "Collin Peters" <cadiolis@gmail.com> wrote:

> An update to this thread for this issue for any future people having
> the same problem
> 
> Found a fix for this.  It seems that if you have the address set to
> '127.0.0.1' it does not correctly use the stored password but if you
> use 'localhost' it does.  Very strange indeed.

That's really bizzare. I'll look into it when I get a minute - thanks for
reporting back.

Regards, Dave.