Hello guys,
I'm configuring a new server, and I would to authenticate the users via
LDAP. We already have systems doing this, like Intranet (Joomla! Framework)
and Imap Mail.
So, for tests, I added the following line in the pg_hba.conf (according the
Postgres Documentation):
hostall
re ignored.
Thank again for your helpTahir Tamba
De: Shoaib Mir <[EMAIL PROTECTED]>
Date: Mardi, Mai 23, 2006 1:33 pm
Objet: Re: [ADMIN] Authentication troubleshooting using psql
> Try using > > \c dbname > > and if you want to get rid of the asking password thing
Tahir Tamba wrote:
> Hi Guys,
>
> I install Postgres 8.1.3 on WinXP Pro OS using msi.exe. Using Postgres with
> PGAdmin III, everything works well. But when I'm trying to use the psql
> terminal interface to connect into my database psql ask me to enter my
> password and when trying to enter m
Try using\c dbnameand if you want to get rid of the
asking password thing you can change your authentication method from
'md5' to 'trust' in your pg_hba.conf file and then reload the settings
using "pg_ctl reload"
/ShoaibOn 5/23/06, Tahir Tamba <[EMAIL PROTECTED]> wrote:
Hi Guys,I install Postgres
Hi Guys,
I install Postgres 8.1.3 on WinXP Pro OS using msi.exe. Using Postgres with
PGAdmin III, everything works well. But when I'm trying to use the psql
terminal interface to connect into my database psql ask me to enter my
password and when trying to enter my password, nothing happens fro
Epps, Aaron M. writes:
> pg_hba.conf
> localallalltrust
> why when I run the following command does authentication fail (Yes, password is
> correct)?
You don't need a password in this setup.
> [EMAIL PROTECTED] aaron]$ psql test -U testing -W
> Password:
> psql: FATAL: IDENT authe
Here's my config file...
pg_hba.conf
local all all
trust
PostgreSQL Users...
test=#
\du
List of database users User name | User ID
|
Attributes---+-+ aaron
| 100 | superuser, create
database postgres |
uot;);
> break;
> default:
> $this->logger("Unknown database type in init()","DBI");
> break;
>
> -Original Message-
> From: scott.marlowe [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 28, 2003 2:58 PM
>
ername and password I get the following error...
>
> Warning: pg_connect(): Unable to connect to PostgreSQL server: FATAL: IDENT
> authentication failed for user "dbname=issue-tracker" . in
> /var/www/html/issue-tracker/includes/classes/dbi.class.php on line 98 "
>
tml/issue-tracker/includes/classes/dbi.class.php on line 98 "
>
> Thoughts?
>
> -Original Message-
> From: scott.marlowe [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 28, 2003 2:37 PM
> To: Tom Lane
> Cc: Epps, Aaron M.; '[EMAIL PROTECTED]'
>
g_connect(): Unable to connect to PostgreSQL server: FATAL: IDENT
authentication failed for user "dbname=issue-tracker" . in
/var/www/html/issue-tracker/includes/classes/dbi.class.php on line 98 "
Thoughts?
-----Original Message-----
From: scott.marlowe [mailto:[EMAIL PROTECTED
On Tue, 28 Oct 2003, Tom Lane wrote:
> "Epps, Aaron M." <[EMAIL PROTECTED]> writes:
> > I've got an authentication questions. I've just setup pg_hba.conf to use
> > "localallalltrust" for testing purposes, but when the application I'm
> > using tries to connect to the PostgreSQL
On Tue, 28 Oct 2003, Epps, Aaron M. wrote:
> I've got an authentication questions. I've just setup pg_hba.conf
> to use "localallalltrust" for testing purposes, but when the
> application I'm using tries to connect to the PostgreSQL Db (Using PHP)
> I get the following error.
>
On Tue, Oct 28, 2003 at 14:12:31 -0600,
"Epps, Aaron M." <[EMAIL PROTECTED]> wrote:
> I've got an authentication questions. I've just setup pg_hba.conf to use "local
>allalltrust" for testing purposes, but when the application I'm using
> tries to connect to the PostgreSQL Db (
"Epps, Aaron M." <[EMAIL PROTECTED]> writes:
> I've got an authentication questions. I've just setup pg_hba.conf to use "local
>allalltrust" for testing purposes, but when the application I'm using
> tries to connect to the PostgreSQL Db (Using PHP) I get the following error.
>
I've got an authentication
questions. I've just setup pg_hba.conf to use "local
all all trust" for testing purposes, but
when the application I'm using tries to connect to the PostgreSQL Db (Using PHP)
I get the following error.
" Warning: pg_connect(): Unable to connect to P
That is going to use the identd server on your machine, not NIS.
---
Yung-Min Chen wrote:
> Can anybody tell me how to set up pgsql authentication using NIS password database?
>
> I set my pg_hba.conf as following:
>
> hos
Can anybody tell me how to set up pgsql authentication using NIS password database?
I set my pg_hba.conf as following:
hostall10.0.1.0255.255.255.0identsameuser
But I'm still getting "user does not exist" error. Any suggestion will be very much
appreciated.
Thanks in advanc
Can anybody tell me how to set up pgsql (v7.1) authentication using NIS password
database?
I set my pg_hba.conf as following:
hostall10.0.1.0255.255.255.0identsameuser
But I'm still getting "user does not exist" error. Any suggestion will be very much
appreciated.
Thanks i
On Wednesday, July 10, 2002, at 08:54 AM, Kevin Brannen wrote:
Stuff deleted
> The order I would propose would be: env-var, command-line, STDIN,
> interactive prompt if we have a tty. Reorder as you see fit.
To the above list I would add a .psql (or something) file in
the home dir of the pe
Bruce Momjian wrote:
> Kevin Brannen wrote:
>
>>Bruce Momjian wrote:
>>...
>>
>>>7.3 may remove PGPASSWORD, I think, and instead allow you to specify a
>>>file that contains the password.
>>
>>But do you know how many hours it took me to find out about PGPASSWORD
>>in the docs and now you want t
> -Messaggio originale-
> Da: Bruce Momjian [mailto:[EMAIL PROTECTED]]
> Inviato: mercoledì 10 luglio 2002 4.11
> A: Kevin Brannen
> Cc: [EMAIL PROTECTED]
> Oggetto: Re: [ADMIN] Authentication in batch processing
>
>
> Kevin Brannen wro
Kevin Brannen wrote:
> Bruce Momjian wrote:
> ...
> >
> > 7.3 may remove PGPASSWORD, I think, and instead allow you to specify a
> > file that contains the password.
>
> But do you know how many hours it took me to find out about PGPASSWORD
> in the docs and now you want to change that? :-)
>
Bruce Momjian wrote:
...
>
> 7.3 may remove PGPASSWORD, I think, and instead allow you to specify a
> file that contains the password.
But do you know how many hours it took me to find out about PGPASSWORD
in the docs and now you want to change that? :-)
How about all 4 approaches: on the com
In my previous message I forgot to say that there is also another file
to patch to re-enable the old stdin input method for pg_dump:
In addition to: src/bin/psql/common.c
You have to patch also: src/bin/pg_dump/pg_backup_db.c
Changes to apply are the same.
--
t;http://www.xmedia.net>
via Francesco Benaglia, 13 - Tel. +39 06 588851
00153 Roma Italy fax +39 06 58885016
--
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]]
> Sent: tuesday 4 july 2002 18.16
> To: Alfred Anzlovar
> Cc: Alfred Anzlova
On Tue, 2 Jul 2002, Bruce Momjian wrote:
> Yes, we had complaints that people were running their script and they
> wouldn't be prompted for the password on their terminal. Researching,
> we found no applications that gets passwords from stdin _if_ a
> controlling terminal (/dev/tty) can be opene
At 12:16 PM 7/4/02 -0400, Bruce Momjian wrote:
> > Well, I must admit we had some rain today, but after your answer sun came
> > from behind the clouds :)
Rain? I've heard about that. Something about moisture falling from the
sky. Haven't seen any here in Phoenix for several months.
On Thu, 4 Jul 2002, Bruce Momjian wrote:
> How about PGUSER/PGPASSWORD? That will work. This is assuming you
> don't have an OS (BSD?) that displays environment variables for a
> process.
No BSD, Linux. And it works. Thanks.
Well, I must admit we had some rain today, but after your answer sun
Alfred Anzlovar wrote:
> On Thu, 4 Jul 2002, Bruce Momjian wrote:
>
> > How about PGUSER/PGPASSWORD? That will work. This is assuming you
> > don't have an OS (BSD?) that displays environment variables for a
> > process.
>
> No BSD, Linux. And it works. Thanks.
>
> Well, I must admit we had s
Alfred Anzlovar wrote:
> Maybe this could/can be done differently, but as it was, it was so easy
> and nice. And if there are more of us, poor souls, with comparable
> problems maybe an option called '--pwd-from-stdin-only' would be a
> solution. Another option (thanks God for Open Source proje
Alfred Anzlovar wrote:
> [EMAIL PROTECTED] (Bruce Momjian) wrote in message
>news:<[EMAIL PROTECTED]>...
> > Password prompting was changed in 7.2.X. You can now pass a script into
> > psql, and you will be prompted for the password on your terminal rather
> > than having the password coming fro
[EMAIL PROTECTED] (Bruce Momjian) wrote in message
news:<[EMAIL PROTECTED]>...
> Password prompting was changed in 7.2.X. You can now pass a script into
> psql, and you will be prompted for the password on your terminal rather
> than having the password coming from the script.
>
> The best way
I solved my problems. I was issuing the wrong command to create users
and alter the user's passwords.
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
I am having problems with authentication. Whatever I try I always get
this error.
psql: FATAL 1: Password authentication failed for user
I am trying to use MD5. I tried with system users and with postgres user
and with user added with ADD USER WITH ENCRYPTION PASSWORD
'thepassword'
I am on a Re
Password prompting was changed in 7.2.X. You can now pass a script into
psql, and you will be prompted for the password on your terminal rather
than having the password coming from the script.
The best way send the password in 7.2.X is to use 'expect', or use the
PGPASSWORD environment variable
I have postgres set up to require usernames and passwords for access.
The following script works just fine in 7.1.2 without manual
intervention. Using 7.2.1 psql issues a password prompt and
blocks until a password is manually entered.
###
#!/bin/sh
psql myd
> The "sameuser" part of this works now, since sameuser is a record
> matching constraint, not an authentication test.
>
> There has been some talk of adding a more flexible username-matching
> field to pg_hba (whereupon the file name would be inappropriate ;-))
> but no one's really done any wor
Dmitry Morozovsky <[EMAIL PROTECTED]> writes:
> There is no "fall-through" or "backup": if one record is chosen
> and the authentication fails, the following records are not
> considered.
> Are there any plans to loose this restriction?
No. I don't believe we could count on cl
Hi there colleagues,
>From the Docs (Admin 4.1):
There is no "fall-through" or "backup": if one record is chosen
and the authentication fails, the following records are not
considered.
Are there any plans to loose this restriction? It would be very useful
to use e.g.
lo
Hi all,
sometimes i have a curios problem with my Zope.
Without any errors in any logs Zope could not authenticate himself with
postgres.
The error message is that there is a wrong password.
After a restart of Zope everything works fine until the eror occurs
again.
My sysop has traced the protco
On Sat, Sep 29, 2001 at 07:34:43PM -0700, Russ McBride wrote:
> I'm going to restate the situation since there was some confusion,
> judging from a couple of responses.
>
> The goal-- The goal is to be able to connect to my database from the
> very machine where the database sits, without worry
Russ-
You've got a real poser there... our system works fine with the same lines
in pg_hba. I think that means you may find your answer in the operating
system environment instead of the postgres setup.
> local all trust
> host all 127.0.0.1255.25
Alright all you pg_hba.conf experts . . .
I can't for the life of me figure out why I'm getting connection
error messages which mention the pg_hba.conf file. I was trying to
use the default settings:
local all trust
host all 127.0.0.1255.255.2
Graham Vickrage writes:
> host all 127.0.0.1 255.255.255.0ident sameuser
> host all 0.0.0.0 0.0.0.0 password
>
> I assumed that the above would solve my problem, which it only half manages.
> The local client connections are worki
Hi all,
I have a problem that may not be directly to do with postgres but I can't
seem to figure it out. I have a linux redhat server with apache and postgres
7.0 runing on the same machine.
I am trying to sort out authentication so that local clients can connect to
the databases using 'ident sa
ALTER USER postgres WITH PASSWORD 'yourpassword';
On Mon, 12 Mar 2001, Peter Schuller wrote:
> Hello,
>
> I'm sure this has been covered before, but the ML archive search engine is
> down (?!).
>
> After telling postgresql not to trust anyone, but always use password/crypt
> as the authenticat
Hello,
I'm sure this has been covered before, but the ML archive search engine is
down (?!).
After telling postgresql not to trust anyone, but always use password/crypt
as the authenticaton method (pg_hdb.conf), I can't seem to get the
postmaster to authenticate against the right password.
What
Dear all
I've just started using postgreSQL (on a network of SUNs) and immediately
have run into the 'famous' (as it appears from this mail-list
archive) authentication problem. And the question is quite simple (I wish
the answer was...): Can one make postgreSQL work in the following way:
If som
Dear faisal,
Well, since the postgreSQL is already installed in my
server, I didn't install it by myself.
Is it the problem of installation???
I have the 'template1' database. Is is okay???
Thanks,
Ada
--- Faisal Haji Mustaffa <[EMAIL PROTECTED]> wrote:
> u have to compile your postgres pro
Dear all,
When I start to use PostgreSQL by creating user, the
following message appears.
Connection to database 'template1' failed.
fe_sendauth: no password supplied
createuser: database access failed.
Can anyone tell me what's going on???
Thank you!!!
Regards,
Ada
___
Hi.
Does anyone knows of an existing patch to authenticate users connecting to
the database via pam modules?
Thanks,
Jacopo
I have Postgres v. 6.3.2 installed and I need to set it for
user-password authentication.
I tried to change the file pg_hba.conf in the DATA directory with both
"password" and "crypt" options, but when I try to access the DB with the
"-u" option I get a "user authentication failed" error.
Can som
Does anyone know of any patches/utilities/magic to make PostgreSQL (6.5)
use either PAM for authentication, or, if that doesn't work, is somehow
NIS aware when the supplied password file ends with the usual +: ?
(Or, as a rather clumsy solution, can I pipe the output of ypcat as the
password "
I'm running PHP 3.05 on a remote machine trying to make a connection to our
Postgres 6.1 machine.
Here's the error that I'm getting:
-
Warning: Unable to connect to PostgresSQL server: Failed to authenticate client
as Postgres us
Hi,
i am trying to connect to postgres from a Perl script using DBI,
and using an encrypted password. (for right now i'm doing this on a
local machine, but the idea is obviously to go from a web server to
another machine with postgres on it.) Even though I have this in the
pg_hba.con
Please suggest me what are all the way i
can implement AUTHENTICATION on USER , DATABASE and TABLE.
As i have seen, to my knowledge i understood we can implement
Grant and Revoke on table
But how can we do the same on the DATABASE
There is a password attribute in pg_shadow
how can this be used t
57 matches
Mail list logo
