Re: login issue..

From: Robert Treat <rtreat(at)webmd(dot)net>
To: Chris Bowlby <excalibur(at)hub(dot)org>
Cc: phppgadmin-users(at)lists(dot)sourceforge(dot)net, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: login issue..
Date: 2002-06-20 18:24:59
Message-ID: 1024597500.24064.108.camel@camel
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 2002-06-20 at 12:53, Chris Bowlby wrote:
>
> Hi All,
>
> Hmmm ok I'm running PostgreSQL 7.2.1 with phppgadmin 2.4.1. I'm
> attempting to configure pgadmin to allow a "user" to see all their
> databases, however we use a password configuration scheme.
>
> the pg_hba.conf file looks like:
>
> host testme_database 192.168.1.2 255.255.255.255 password password_file
>
> However, the test account that I have specified in the password file is
> not "acknowledged" by postgreSQL unless I also have the user as being
> create in the system tables.

AFAIK this is by design in postgreSQL; you are not a valid user unless
you have an entry in pg_shadow.

> I am cross posting this one to both lists
> because I know part of the problem is "pgsql" related and the other half
> (getting to it) is phppgadmin related (I think)..
>
> The other problem is, that when I can access the database from the
> console, I can not access it via the phppgadmin interface unless I put the
> username and password in the config file, regardless of if I'm using
> adv_auth or not...
>
> anyone run into something similar and figure out a solution for it?
>

I just set this up on one of our servers and it worked so it is doable.
9 times out of 10 this is an issue of tcp sockets vs. unix sockets. Your
config.inc should probably look like:

$cfgServers[2]['local'] = false;
$cfgServers[2]['host'] = '192.168.0.xxx'; // IP of DB server
$cfgServers[2]['port'] = '5432';
$cfgServers[2]['adv_auth'] = true;

$cfgServers[2]['user'] = ''; // if you are not using
$cfgServers[2]['password'] = ''; // if you are not using adv_auth
$cfgServers[2]['only_db'] = ''; // if set to a db-name, only

also try looking in your postgres logs, you should be generating "FATAL"
errors every time login fails, they should give you better insight as to
where things are going wrong.

Robert Treat
xzilla(at)users(dot)sourceforge(dot)net
member phpPgAdmin development team

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrew Sullivan 2002-06-20 18:44:09 Re: URGENT: Performance tuning
Previous Message Varun Kacholia 2002-06-20 18:21:54 versions ?