Thread: login issue..
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. 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? Chris Bowlby, ----------------------------------------------------- Manager of Information and Technology. excalibur@hub.org www.hub.org 1-902-542-3657 -----------------------------------------------------
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@users.sourceforge.net member phpPgAdmin development team
On 20 Jun 2002, Robert Treat wrote: Hi Robert, Ok, that worked for getting me into it. However phppgadmin is now giving me two login screens after I manage to log in, as it it's not seeing the connection... the frame's are loaded, but it does not give me the familiar listing of databases's in the left frame and links on the right... only two login screens... anyone run into this as well? > 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@users.sourceforge.net > member phpPgAdmin development team > > > > Chris Bowlby, ----------------------------------------------------- Manager of Information and Technology. excalibur@hub.org www.hub.org 1-902-542-3657 -----------------------------------------------------
On 24 Jun 2002, Robert Treat wrote: Hi Robert, Just did a quick check to make sure the register globals is enabled, and she is... > Hey Chris, > > I left early friday and missed this one but I was just wondering if you > got this resolved. The problem your describing sounds like register > globals issue, where register globals needs to be turned on. Usually > this problem crops up in newer version of PHP, I think the 4.2 release > and maybe some of the later 4.1 series as well. HTH > > Robert > > On Fri, 2002-06-21 at 10:47, Chris Bowlby wrote: > > On 20 Jun 2002, Robert Treat wrote: > > > > Hi Robert, > > > > Ok, that worked for getting me into it. However phppgadmin is now > > giving me two login screens after I manage to log in, as it it's not > > seeing the connection... the frame's are loaded, but it does not give me > > the familiar listing of databases's in the left frame and links on the > > right... only two login screens... anyone run into this as well? > > > > > > > > > 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@users.sourceforge.net > > > member phpPgAdmin development team > > > > > > > > > > > > > > > > Chris Bowlby, > > ----------------------------------------------------- > > Manager of Information and Technology. > > excalibur@hub.org > > www.hub.org > > 1-902-542-3657 > > ----------------------------------------------------- > > > Chris Bowlby, ----------------------------------------------------- Manager of Information and Technology. excalibur@hub.org www.hub.org 1-902-542-3657 -----------------------------------------------------
Assuming you are running a newer version of php, there is a new beta (2.4.2-beta) available of phpPgAdmin which is supposed to address the issue your talking about. You can get it at http://sourceforge.net/project/shownotes.php?release_id=93000 Robert Treat xzilla@users.sourceforge.net phpPgAdmin Development Team On Mon, 2002-06-24 at 12:21, Chris Bowlby wrote: > On 24 Jun 2002, Robert Treat wrote: > > Hi Robert, > <snip> > > > > On Fri, 2002-06-21 at 10:47, Chris Bowlby wrote: > > > On 20 Jun 2002, Robert Treat wrote: > > > > > > Hi Robert, > > > > > > Ok, that worked for getting me into it. However phppgadmin is now > > > giving me two login screens after I manage to log in, as it it's not > > > seeing the connection... the frame's are loaded, but it does not give me > > > the familiar listing of databases's in the left frame and links on the > > > right... only two login screens... anyone run into this as well? > > > > > > > > > > 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: > > > > <snip> > > > > > > > > > > > > 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@users.sourceforge.net > > > > member phpPgAdmin development team > > > > > > > > Chris Bowlby, > ----------------------------------------------------- > Manager of Information and Technology. > excalibur@hub.org > www.hub.org > 1-902-542-3657 > -----------------------------------------------------
On 25 Jun 2002, Robert Treat wrote: Hi Robert, Just tried 2.4.2-beta and still get the same results....:(... I am able to log in but I still only get two frames that contain login screens again. are there issues with Apache 2? I know there are issues with PHP 4.2.x and storing multiple cookie's.... > Assuming you are running a newer version of php, there is a new beta > (2.4.2-beta) available of phpPgAdmin which is supposed to address the > issue your talking about. You can get it at > http://sourceforge.net/project/shownotes.php?release_id=93000 > > Robert Treat > xzilla@users.sourceforge.net > phpPgAdmin Development Team > > On Mon, 2002-06-24 at 12:21, Chris Bowlby wrote: > > On 24 Jun 2002, Robert Treat wrote: > > > > Hi Robert, > > > <snip> > > > > > > On Fri, 2002-06-21 at 10:47, Chris Bowlby wrote: > > > > On 20 Jun 2002, Robert Treat wrote: > > > > > > > > Hi Robert, > > > > > > > > Ok, that worked for getting me into it. However phppgadmin is now > > > > giving me two login screens after I manage to log in, as it it's not > > > > seeing the connection... the frame's are loaded, but it does not give me > > > > the familiar listing of databases's in the left frame and links on the > > > > right... only two login screens... anyone run into this as well? > > > > > > > > > > > > > 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: > > > > > > <snip> > > > > > > > > > > > > > > > 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@users.sourceforge.net > > > > > member phpPgAdmin development team > > > > > > > > > > > > Chris Bowlby, > > ----------------------------------------------------- > > Manager of Information and Technology. > > excalibur@hub.org > > www.hub.org > > 1-902-542-3657 > > ----------------------------------------------------- > > > Chris Bowlby, ----------------------------------------------------- Manager of Information and Technology. excalibur@hub.org www.hub.org 1-902-542-3657 -----------------------------------------------------